RiverScript MCP Server Public MCP server for RiverScript, an AI transcription platform. RiverScript lets you transcribe everything you can hear on your computer. Literally. Record and transcribe system audio on Windows and macOS from virtually any app — meetings, calls, lectures, webinars, videos, live streams, podcasts, and other media — without bots or platform-specific integrations. RiverScript also transcribes audio and video files up to 50 GB and up to 8 hours long, without the usual browser limitations. This MCP server lets AI apps fetch RiverScript transcripts and AI translations of transcripts that users have shared with a link. Endpoint: https://riverscript.com/mcp Transport: Streamable HTTP Authentication: none — the MCP server can access content that users have explicitly shared with a RiverScript share link Documentation: https://riverscript.com/docs/platform-details/mcp Website: https://riverscript.com This repository documents the public MCP endpoint; it does not contain the server's implementation, which is part of RiverScript's main application. Tool get_shared_transcript Fetches the full text of a RiverScript transcript from a share link. The tool accepts a RiverScript share URL or share token and returns the shared transcript together with its available metadata. Share links can also point to AI translations of transcripts. The tool fetches them the same way and returns the translated text. Expired or deleted links return no transcript. What you can bring to AI apps Choose transcripts or translations in RiverScript and create share links for them. Once shared, transcripts can be fetched by compatible AI apps through the RiverScript MCP server. About RiverScript Beyond transcription, RiverScript includes transcript editing, speaker detection, clickable timestamps, timed subtitles, AI summaries, AI chat, translation into 100 languages, export, and sharing. Learn more at riverscript.com

MCP readiness

B · 79/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (2602 ms); slow response -1.
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	27/27 probes succeeded over 30 days (100%).
Tool declaration	5/10	Lists 1 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (2602 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 40% of peers; This listing 79 · peer median 81
Latency: Faster than 5% of peers; This listing 1,217 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Tool declaration −5 — Declare every tool with a description and input schema.
Now: Lists 1 tool(s) with descriptions.
Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-17 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/valosanteri/RiverScript-shared/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/valosanteri/RiverScript-shared/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://riverscript.com/

Listed at (smithery)

https://riverscript.com/