Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MoneyTools Transcripts

REMOTE · SPEECH.MONEYTOOLS.DEV

STT + SRT/VTT; 3-hour async jobs; dTelecom-compatible file API; x402 $0.005/min, no prepaid credits

+3 this week 70 Trust /100

Last scanned (14 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1358 tokens (~194/item across 7 items; 7 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 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.

  • 18 Nov 26 +1
    • Server version: 1.3.2 → 1.3.3 functional
  • 16 Nov 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.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “speech_job_submit” rewrote its description, which is the text the model reads security
    • Tool “speech_report” rewrote its description, which is the text the model reads security
    • Tool “speech_transcribe” rewrote its description, which is the text the model reads security
    • Server version: 1.3.1 → 1.3.2 functional
  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 65

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://speech.moneytools.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=moneytools.dev CN=WE1,O=Google Trust Services,C=US 9 Nov 2026 7 Feb 2027 ECDSA 256 ECDSA-SHA256 bab55dfb456dac2d0ef477e48cd87999
SANs: moneytools.dev, speech.moneytools.dev, *.speech.moneytools.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of speech.moneytools.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
moneytools.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://speech.moneytools.dev/mcp Verified 200
http (plaintext) http://speech.moneytools.dev/mcp Served over HTTP 200
MCP tools · 7 exposed · ~1,059 tokens

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 →

Tool Tokens
speech_job_status ~105

Free: status, progress and (when done) transcript, segments, SRT/VTT of an async job. Needs jobId + jobToken (shown once at submit). format=srt|vtt|txt returns that text only.

NameTypeReqDescription
formatstring–json (default) or a subtitle/text format.
jobIdstringyesjob_… id from speech_job_submit.
jobTokenstring–jt_… token returned once at submit.

No output schema declared.

No examples provided.

speech_job_submit ~194

Submit a long audio file (url or uploadId) as an async job: 0.005 USDC per started minute (exact, x402 Base USDC), up to 180 min. Without payment returns PaymentRequired with the exact price; pay via _meta["x402/payment"]. First segment is transcribed before settlement; then poll speech_job_status or get a signed webhook.

NameTypeReqDescription
durationSecondsnumber–Declared duration hint (can only raise the price).
languagestring–Optional language hint (e.g. en, zh).
summaryboolean–Include a short summary when done.
uploadIdstring–job_… id from speech_job_upload_url after the PUT.
urlstring–HTTPS direct media URL you have the right to process (not a platform page).
webhookstring–Optional public https URL for a signed job.done callback.

No output schema declared.

No examples provided.

speech_job_upload_url ~160

Free: mint a signed single-use PUT URL for a long file (up to 100 MB / 180 min; MP3/WAV are segmented). PUT via plain HTTP; the PUT response carries the exact price. Then speech_job_submit with uploadId.

NameTypeReqDescription
bytesnumber–Optional file size hint in bytes.
contentTypestring–Content-Type to use on PUT (audio/* or video/*).
durationSecondsnumber–Declared duration hint (can only raise the price).
languagestring–Optional language hint (e.g. en, zh).
summaryboolean–Include a short summary when done.
webhookstring–Optional public https URL for a signed job.done callback.

No output schema declared.

No examples provided.

speech_quote ~120

Free: estimate the exact x402 price from minutes, seconds, bytes, or an audio URL (HEAD). Billing uses max(declared, parsed duration, 16 kbps size floor).

NameTypeReqDescription
bytesnumber–Audio file size in bytes (16 kbps floor used for pricing).
minutesnumber–Audio duration in minutes (hint only; never underprices alone).
secondsnumber–Audio duration in seconds (hint only).
urlstring–HTTPS audio URL; we HEAD for Content-Length (SSRF-protected).

No output schema declared.

No examples provided.

speech_report ~59

Paid live status snapshot: capacity remaining today, price table, billing rule, capabilities. 0.005 USDC via x402 over MCP (unpaid → PaymentRequired). Free quote remains at speech_quote / GET /v1/speech/quote.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

speech_transcribe ~298

Generate a value-added transcript with timestamped segments, SRT/VTT, language detection, word count and duration (optional summary). 0.005 USDC/started minute (min 0.005); 3 free/day. Pass url, upload_id (from speech_upload_url), or audioBase64 — WAV/MP3/M4A/MP4/WebM/OGG/FLAC you have the right to process. Platform pages refused. Max 10 min / 25 MB. Price = max(declared, parsed, 16 kbps floor).

NameTypeReqDescription
audioBase64string–Base64-encoded audio bytes (alternative to url/uploadId).
durationSecondsnumber–Declared duration hint in seconds (cannot underprice; we parse the file).
languagestring–Optional language hint (e.g. en, zh). If omitted we detect language.
minutesnumber–Declared duration hint in minutes.
summaryboolean–If true, include a short 1–3 sentence summary.
uploadIdstring–upload_id from speech_upload_url after a successful PUT (single-use).
urlstring–HTTPS direct media file URL you have the right to process (audio/* or video/*; MP3/M4A/MP4/WebM/WAV/…). Not a YouTube/Instagram/TikTok/Facebook/X/Vimeo page.

No output schema declared.

No examples provided.

speech_upload_url ~123

Free: mint a short-lived (15 min), single-use PUT URL for local media. PUT the file via plain HTTP (not MCP), then pass upload_id to speech_transcribe. Size cap matches MaxBytes; rate-limited per client. Not a public file host — bytes are deleted after transcription or expiry.

NameTypeReqDescription
bytesnumber–Optional declared size hint; must not exceed MaxBytes.
contentTypestring–Optional Content-Type to recommend on PUT (audio/* or video/*).
filenamestring–Optional original filename (metadata only).

No output schema declared.

No examples provided.

Install

How do I install the MoneyTools Transcripts MCP server?

MoneyTools Transcripts is a hosted endpoint at https://speech.moneytools.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · speech.moneytools.dev

# add to Claude Code
claude mcp add --transport http dev-moneytools-transcripts 'https://speech.moneytools.dev/mcp'
Common questions

What is the MoneyTools Transcripts MCP server?

MoneyTools Transcripts is an MCP server listed in the public MCP registry as dev.moneytools/transcripts. STT + SRT/VTT; 3-hour async jobs; dTelecom-compatible file API; x402 $0.005/min, no prepaid credits. This page covers its hosted endpoint (https://speech.moneytools.dev/mcp).

Is the MoneyTools Transcripts MCP server safe to use?

MoneyTools Transcripts scores 70 out of 100 on VerifyMCP. 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 MoneyTools Transcripts MCP server expose?

MoneyTools Transcripts exposes 7 tools: speech_report, speech_quote, speech_upload_url, speech_transcribe, speech_job_upload_url, and 2 more. Their descriptions and schemas cost roughly 1,059 tokens of context every time the server is loaded.

Does the MoneyTools Transcripts MCP server require authentication?

No. We connected to MoneyTools Transcripts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MoneyTools Transcripts MCP server still maintained?

MoneyTools Transcripts is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the MoneyTools Transcripts MCP server?

VerifyMCP ran 13 checks on MoneyTools Transcripts, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.