io.github.rymi-live/rymi-mcp
Rymi
Is the Rymi MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Build, call and manage AI voice agents on real phone calls.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
The server needs auth, so these tool definitions were read from the publisher's open-source package npm:@rymi/mcp, started in a container with placeholder values and the network off, on 2026-11-14. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing bearer token"}- Endpoint
- https://mcp.rymi.live/mcp (streamable-http)
- Host
- mcp.rymi.live
- Of a 1M window
- 1.3 % of a 1M context window
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.rymi.live/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server oplhypjwdjnpxsjfaukm.supabase.co, PKCE S256, grants authorization_code, refresh_token.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/rymi-live/rymi-mcp
- Website
- https://docs.rymi.live/api/mcp
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention rymi or manage or build.
- Mimetic — Website Growth and Analytics com.trymimetic/mimetic · needs auth
- Mint io.github.verymint/mint · needs auth
- Propick Integration MCP ae.propick/propick · needs auth
- ai.actwise/ideation · needs auth
- ai.adramp/google-ads · needs auth
- ai.adside/adside · needs auth
- Adsap ai.adsap/adsap · needs auth
- Aevia ai.aeviamodeler/aevia · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.