com.terudo/partner
Terudo partner
Is the Terudo partner MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
Travel eSIMs for travel businesses: quotes, phone and plan checks, orders, top-ups, webhooks.
needs auth probed 2026-11-14 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"unauthorized","message":"Clé API absente, révoquée ou inconnue, ou API non ouverte pour ce c- Endpoint
- https://terudo.com/api/partner/v1/mcp/ (streamable-http)
- Host
- terudo.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://terudo.com/api/partner/v1/mcp/ registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server terudo.com, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://terudo.com/developers/api/#mcp
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Other registry entries on terudo.com.
- Terudo developer docs com.terudo/docs · alive
Servers that mention partner.
- ai.askmiles/catalog · alive
- ai.creationloop/creationloop · alive
- MLP Tax Computation Engine ai.lucasandersen/mlp-tax · alive
- Eous ai.partnerwith/eous · alive
- WEM Price Compare ai.wem3/wem-price-compare · alive
- Noemic app.noemic/noemic · needs auth
- Partli app.partli/partli · needs auth
- IT Security — Access Change Request Recertify — Alder Court Partners (b578285f) com.a2awire/benchmark-access-change-request-recertify-2026-09-15-b578285f · alive
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.