Paxa Labs
NPM · @PAXALABS/MCP · SCANNED SEP 25
Thai, English, Mandarin speech AI: TTS with playback, transcription, translation, OCR, extraction
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2662 tokens (~221/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Paxa Labs MCP server?
Paxa Labs runs locally as an npm package, launched with npx -y @paxalabs/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @paxalabs/mcp
claude mcp add com-paxalabs-mcp -- npx -y @paxalabs/mcp
{
"mcpServers": {
"com-paxalabs-mcp": {
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
]
}
}
} {
"servers": {
"com-paxalabs-mcp": {
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
]
}
}
} codex mcp add com-paxalabs-mcp -- npx -y @paxalabs/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-paxalabs-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@paxalabs/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-paxalabs-mcp --command npx --arg -y --arg @paxalabs/mcp
mcp_servers:
com-paxalabs-mcp:
command: "npx"
args: ["-y", "@paxalabs/mcp"] {
"McpServers": {
"com-paxalabs-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@paxalabs/mcp"
]
}
}
} assistant mcp add com-paxalabs-mcp -t stdio -c npx -a -y @paxalabs/mcp
{
"mcpServers": {
"com-paxalabs-mcp": {
"command": "npx",
"args": [
"-y",
"@paxalabs/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 −1
- Stability: 0.50 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 158 → 221 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.0-beta.9 → 0.1.0-beta.10 functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@paxalabs/mcp@0.1.0-beta.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
control_playback Playback control ~67
Inspect and control the shared audio queue. status reports what is playing, what is queued, and any synthesis failures. pause and resume halt and continue playback (not supported on Windows). skip drops the current segment. clear stops playback and empties the queue.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
No output schema declared.
No examples provided.
extract_fields Extract fields from a document ~781
Extract typed fields from a local PDF, PNG, JPEG, or WebP document (up to 20 pages and 10 MiB) with Paxa Document Extraction. You write a schema of fields; every value returned is text printed in the document, read as the field's type, or null with the reason. Nothing is inferred or looked up. Built for Thai documents (receipts, tax invoices, forms, IDs) and fine on English ones. Costs 13 credits per page for a schema of up to 50 leaf fields and 19.5 per page for 51 to 100; the page reading and the evidence spans cost nothing extra. A schema the API refuses costs nothing and names the field and reason. The schema parameter summarizes the dialect; https://paxalabs.com/docs/extraction has every type and key.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to a local PDF, PNG, JPEG, or WebP file |
| include_evidence | boolean | – | Also return, per field path, the printed span the value was read from. Free. |
| include_pages | boolean | – | Also return each page's text as Markdown, the reading the fields came from. Free. |
| output_path | string | – | Save the full JSON response here. Relative paths resolve against PAXA_OUTPUT_DIR (or the working directory). An existing file is never overwritten. |
| schema | object | yes | Prefer the most specific type for each field: a specific type verifies the printed value (a date must parse, a thai_id must pass its check digit, a bank must be a real bank) and returns a normalized… |
No output schema declared.
No examples provided.
get_account Account and credits ~26
Show the API key's account: credit balance, plan, and rate limits. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_models List models ~22
List available Paxa models with their limits and credit pricing. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_voices List voices ~32
List the Paxa TTS voice roster: ids, names, gender, language, and character notes. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ocr_document OCR a document ~109
Run Paxa OCR on a local PDF, PNG, JPEG, or WebP file and return its content as GitHub-flavored Markdown (or structured blocks). Up to 50 pages and 10 MiB per file. Costs 6.5 credits per page.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to a local PDF, PNG, JPEG, or WebP file |
| output | string | – | "markdown" (default) returns prose; "structured" returns typed blocks as JSON |
No output schema declared.
No examples provided.
play_audio Play an audio file ~76
Play a local audio file through this machine's speakers, for example a file produced earlier by text_to_speech. Blocks until playback finishes. Free (no API call).
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to a local audio file (mp3, wav, opus, ogg, flac, m4a, aac) |
No output schema declared.
No examples provided.
queue_speech Queue long-form speech ~179
Read long content aloud (stories, articles, books). Splits the text into segments, synthesizes ahead while playing, and returns immediately; segments play in order after anything already queued. Monitor and control with the control_playback tool. Costs 15 credits per 1000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to read aloud, Thai or English |
| voice | string | – | Voice id from list_voices (default "nomyen", a Thai voice). Every voice is designed around one language (Thai, English, or Mandarin Chinese) and reads the others with an accent. English text usually… |
No output schema declared.
No examples provided.
speak Speak out loud ~184
Synthesize a short line with Paxa TTS and play it through this machine's speakers. Blocks until playback finishes. Waits for the currently playing audio but jumps ahead of queued long-form segments. For long content use queue_speech. Costs 15 credits per 1000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to speak, Thai or English, up to 2000 characters |
| voice | string | – | Voice id from list_voices (default "nomyen", a Thai voice). Every voice is designed around one language (Thai, English, or Mandarin Chinese) and reads the others with an accent. English text usually… |
No output schema declared.
No examples provided.
text_to_speech Text to speech (file only) ~197
Synthesize speech with Paxa TTS and save it as an audio file without playing it. Costs 15 credits per 1000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Audio format (default "mp3") |
| output_path | string | – | Where to save the file. Relative paths resolve against PAXA_OUTPUT_DIR (or the working directory). |
| text | string | yes | Text to synthesize, up to 5000 characters |
| voice | string | – | Voice id from list_voices (default "nomyen", a Thai voice). Every voice is designed around one language (Thai, English, or Mandarin Chinese) and reads the others with an accent. English text usually… |
No output schema declared.
No examples provided.
transcribe_audio Transcribe a recording ~575
Transcribe a local recording of speech, Thai or any other language, code-switching included (mp3, wav, flac, ogg, m4a, aac, or webm; up to 60 minutes and 25 MiB) with Paxa STT. The transcript comes back inline, so nothing needs to be read from disk afterwards; optionally it is also saved as txt, json (with word timings and segments), srt, or vtt, named after the recording. Existing files are never overwritten. Detects the language, handles code-switching, and can label speakers. Terms configured in PAXA_VOCABULARY or PAXA_VOCABULARY_FILE are pinned on every call. Costs 8.33 credits per minute of audio (0.1 minimum); subtitles and word timings cost nothing extra. Long recordings take minutes to process.
| Name | Type | Req | Description |
|---|---|---|---|
| convention | string | – | "spoken" (default) writes numbers and dates as they were said; "written" uses numerals |
| diarization | boolean | – | Label speakers, for recordings under 9 minutes. The transcript is then returned as one line per turn, and subtitle cues never cross a speaker change. |
| file_path | string | yes | Path to a local mp3, wav, flac, ogg, m4a, aac, or webm recording |
| language | string | – | Language hint as a BCP 47 tag such as "th" or "en". Omit to auto-detect. |
| output_dir | string | – | Where to write the files. Defaults to the recording's own folder. A relative path resolves against PAXA_OUTPUT_DIR (or the working directory). |
| save | array | – | Files to write, named after the recording: txt (the transcript), json (text, words with timings, segments, usage), srt or vtt (subtitles rendered by the API). Omit to write nothing. |
| style | string | – | "verbatim" (default) keeps fillers and false starts; "clean" drops them |
| subtitle_line_chars | integer | – | Characters per subtitle line, 10 to 120 (default 60). Thai marks above and below consonants are not counted. |
| timestamps | boolean | – | Also return word-level timings inline as JSON (can be long). The json file always has them. |
| vocabulary | array | – | Keyword pinning: terms the recording likely contains, spelled the way they should appear in the transcript (product names, people, places, jargon; Thai or English). Up to 50 terms of 50 characters. T… |
No output schema declared.
No examples provided.
translate_to_thai Translate to Thai ~192
Translate text from any language into Thai with Paxa Translate. Accepts a single string or up to 200 segments that share context. Costs 25 credits per 1000 text characters (minimum 2 credits); context and glossary characters bill at 8 per 1000.
| Name | Type | Req | Description |
|---|---|---|---|
| borrowed_words | string | – | How to render foreign loanwords: transliterate into Thai script, or preserve as-is |
| context | string | – | Background material that improves accuracy, billed at the lower reference rate |
| do_not_translate | array | – | Strings preserved verbatim |
| formality | string | – | – |
| format | string | – | Treat input as plain text, Markdown, or HTML |
| glossary | array | – | Term pairs applied contextually |
| instructions | string | – | Free-form guidance for the translator |
| text | – | yes | Text to translate: one string, or an array of segments translated together |
No output schema declared.
No examples provided.
What is the Paxa Labs MCP server?
Paxa Labs is an MCP server listed in the public MCP registry as com.paxalabs/mcp. Thai, English, Mandarin speech AI: TTS with playback, transcription, translation, OCR, extraction. This page covers its npm package (@paxalabs/mcp).
Is the Paxa Labs MCP server safe to use?
Paxa Labs scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Paxa Labs MCP server expose?
Paxa Labs exposes 12 tools: speak, queue_speech, control_playback, play_audio, text_to_speech, and 7 more. Their descriptions and schemas cost roughly 2,440 tokens of context every time the server is loaded.
Is the Paxa Labs MCP server still maintained?
Paxa Labs is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Paxa Labs MCP server under?
Paxa Labs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.