Spoken
REMOTE · SPOKEN.MD · 2 COMPONENTS
Podcast transcripts as clean Markdown with real speaker names — via the Spoken API.
Available components
Last scanned (21 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Entertainment and Games
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 Security95
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 718 tokens (~89/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (88% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 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 current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 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.
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 4 Nov 2026 · Probed https://spoken.md/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=spoken.md | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 19 Aug 2026 | 4 Mar 2027 | RSA 2048 | SHA256-RSA | b17865edf1ec477fc6dcea96b170d75 |
| SANs: spoken.md | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of spoken.md. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| md. | present | 127 | 14 | Verified |
| spoken.md. | present | 2371 | 13 | Verified |
| spoken.md. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://spoken.md/.well-known/oauth-protected-resource/mcp", scope="mcp"
Bearer resource_metadata="https://spoken.md/.well-known/oauth-protected-resource/mcp", scope="mcp" | Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://spoken.md/.well-known/oauth-protected-resource/mcp", scope="mcp" |
Protected resource metadata
| Document | https://spoken.md/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://spoken.md/mcp |
| Authorisation server | https://spoken.md |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spoken.md/mcp | Verified | 200 | |
| http (plaintext) | http://spoken.md/mcp | HTTPS enforced | 301 | https://spoken.md/mcp |
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 →
follow_podcast Follow a show ~101
Declare a follow for a show, or clear a mute. Pass a podcast_id from search_podcasts. A declared follow stays until unfollow_podcast, regardless of fetch activity, and does not use one of the five automatic slots. For a show never fetched, what counts as new starts from its newest episode now. Does not consume credits.
| Name | Type | Req | Description |
|---|---|---|---|
| podcast_id | string | yes | Show id (the podcast_id field from a search_podcasts result). |
| Name | Type | Req | Description |
|---|---|---|---|
| podcast | string | yes | Show name. |
| podcast_id | string | yes | Show id; pass it to list_episodes or follow_podcast. |
| state | string | yes | – |
No examples provided.
get_balance Get credit balance ~32
Check the current Spoken credit balance, account email, and recent usage for the configured API key. Does not consume credits.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| credits | number | yes | Credits remaining; one is spent per first fetch of an episode. |
| string | – | Account email, when one is attached to the key. | |
| usage | object | yes | – |
No examples provided.
get_transcript Get transcript ~74
Fetch a podcast episode's transcript as clean Markdown with real speaker names and timestamps. Pass an episode id from search_podcasts. Costs 1 credit on the first fetch of an episode; repeat fetches are free and errors are never charged.
| Name | Type | Req | Description |
|---|---|---|---|
| episode_id | string | yes | Episode id returned by search_podcasts. |
No output schema declared.
No examples provided.
list_episodes List a show's episodes ~119
List a podcast's entire back-catalog (every episode, newest first). Pass a podcast_id from a search_podcasts result. Returns each episode's id, title, and date — fetch any with get_transcript. Use this to transcribe a whole show. Does not consume credits itself; transcribing the returned episodes costs 1 credit each (repeat fetches are free), so make sure the key has enough credits before looping.
| Name | Type | Req | Description |
|---|---|---|---|
| podcast_id | string | yes | Show id (the podcast_id field from a search_podcasts result). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | Episodes listed; fetching all of them costs up to this many credits. |
| episodes | array | yes | – |
| podcast | string | yes | Show name. |
| podcast_id | string | yes | Show id; pass it to list_episodes or follow_podcast. |
No examples provided.
list_following List followed shows ~99
The shows this key is kept current on. Every charged fetch makes its show a follow: the five most-fetched shows from the last 180 days are followed automatically (source 'fetch'), and up to 25 more can be declared with follow_podcast (source 'explicit'). Muted shows are listed separately. Use list_new_episodes to see what is new on them. Does not consume credits; the demo key has nothing to follow with.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| following | array | yes | – |
| limits | object | yes | – |
| muted | array | yes | – |
No examples provided.
list_new_episodes List new episodes on followed shows ~121
What is new on the shows this key follows: for each show, the episodes released in the last 90 days that are newer than the newest one already fetched from it (up to 10 per show), each with a transcript_url. Episodes with no transcript are left out. Fetch any with get_transcript (1 credit each on first fetch); a fetch raises that show's floor, so the next call lists only what came after. Refreshed hourly, so a show followed moments ago may be empty until its first poll. Does not consume credits.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | When the list was read, ISO 8601. |
| count | number | yes | New episodes across all followed shows. |
| shows | array | yes | – |
No examples provided.
search_podcasts Search podcasts ~101
Search published podcast episodes by text query, or paste an episode URL (Spotify, YouTube, etc.). Returns matching episodes with their id, title, podcast, podcast_id, and date. Use the id with get_transcript, or the podcast_id with list_episodes to get the show's whole back-catalog. Does not consume credits.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free text (e.g. 'huberman sleep') or a pasted episode URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
unfollow_podcast Stop following a show ~71
Mute a show: it leaves the followed list and later fetches do not re-add it. follow_podcast reverses it. Pass a podcast_id from list_following. Does not consume credits.
| Name | Type | Req | Description |
|---|---|---|---|
| podcast_id | string | yes | Show id, from list_following or search_podcasts. |
| Name | Type | Req | Description |
|---|---|---|---|
| podcast | string | yes | Show name. |
| podcast_id | string | yes | Show id; pass it to list_episodes or follow_podcast. |
| state | string | yes | – |
No examples provided.
How do I install the Spoken MCP server?
Spoken is a hosted endpoint at https://spoken.md/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 · spoken.md
claude mcp add --transport http spokenmd-spoken 'https://spoken.md/mcp'
What is the Spoken MCP server?
Spoken is an MCP server listed in the public MCP registry as io.github.spokenmd/spoken. Podcast transcripts as clean Markdown with real speaker names, via the Spoken API. This page covers its hosted endpoint (https://spoken.md/mcp).
Is the Spoken MCP server safe to use?
Spoken scores 95 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 Spoken MCP server expose?
Spoken exposes 8 tools: search_podcasts, get_transcript, list_episodes, get_balance, list_following, and 3 more. Their descriptions and schemas cost roughly 718 tokens of context every time the server is loaded.
Does the Spoken MCP server require authentication?
Yes. Spoken asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Spoken MCP server still maintained?
Spoken is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.