@paxalabs/mcp

MCPcommunity

v0.1.0-beta.10com.paxalabsUnknownUpdated 1d agonpm GitHub

Thai, English, Mandarin speech AI: TTS with playback, transcription, translation, OCR, extraction

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

10GitHub stars

1d agoLast update

Needs 1 credential before it runs

PAXA_API_KEYAPI keyrequired
Paxa Labs API key, created at https://paxalabs.com/app/keys

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorcom.paxalabs

LicenseUnknown

Version0.1.0-beta.10

Sourcenpm+mcp-registry

npm@paxalabs/mcp

GitHubpaxalabs/mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface11 tools · none privileged

Security scan✓ Cleanv0.1.0-beta.8 · 15d agoHow well does this scan work?

EvalsNone

IndexedSep 8, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · none privileged

Statically extracted from the published packagev0.1.0-beta.8 · 15d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

paxalabsNo description published

This tool published no description. Forge does not invent one.

speakSynthesize a short line with Paxa TTS and play it through this machine's speakers.

Synthesize a short line with Paxa TTS and play it through this machine's speakers.

No input schema was published for this tool.

queue_speechRead long content aloud (stories, articles, books). Splits the text into segments,

Read long content aloud (stories, articles, books). Splits the text into segments,

No input schema was published for this tool.

control_playbackInspect and control the shared audio queue. status reports what is playing, what is

Inspect and control the shared audio queue. status reports what is playing, what is

No input schema was published for this tool.

play_audioPlay a local audio file through this machine's speakers, for example a file produced

Play a local audio file through this machine's speakers, for example a file produced

No input schema was published for this tool.

text_to_speechSynthesize speech with Paxa TTS and save it as an audio file without playing it.

Synthesize speech with Paxa TTS and save it as an audio file without playing it.

No input schema was published for this tool.

translate_to_thaiTranslate text from any language into Thai with Paxa Translate. Accepts a single

Translate text from any language into Thai with Paxa Translate. Accepts a single

No input schema was published for this tool.

ocr_documentRun Paxa OCR on a local PDF, PNG, JPEG, or WebP file and return its content as

Run Paxa OCR on a local PDF, PNG, JPEG, or WebP file and return its content as

No input schema was published for this tool.

list_voicesList the Paxa TTS voice roster: ids, names, gender, language, and character notes. Free.

List the Paxa TTS voice roster: ids, names, gender, language, and character notes. Free.

No input schema was published for this tool.

list_modelsList available Paxa models with their limits and credit pricing. Free.

List available Paxa models with their limits and credit pricing. Free.

No input schema was published for this tool.

get_accountShow the API key's account: credit balance, plan, and rate limits. Free.

Show the API key's account: credit balance, plan, and rate limits. Free.

No input schema was published for this tool.

10 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Thai, English, Mandarin speech AI: TTS with playback, transcription, translation, OCR, extraction

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

11 tools · none privileged · observed 2026-09-08 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

paxalabs
speak
queue_speech
control_playback
play_audio
text_to_speech
translate_to_thai
ocr_document
list_voices
list_models
get_account

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-08 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.5.4
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.7
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.7
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.