mcp-registry/io.github.carlos-vlab/routing-services-courier
As of 2026-10-19 22:03 UTC, the Carlos Vlab Routing Services Courier MCP server is unknown with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.
Pay-per-call ($0.01 USDC) model-routing for AI coding agents: which LLM to call, cost vs. quality.
Point your MCP client at this streamable-http endpoint: https://routing-courier-mcp-production.up.railway.app/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
3 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,993 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.carlos-vlab/routing-services-courier"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.carlos-vlab/routing-services-courier"}) over MCP.
recommend_model_for_task ~167 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.carlos-vlab%2Frouting-services-courier?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.carlos-vlab%2Frouting-services-courier?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.carlos-vlab%2Frouting-services-courier.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.carlos-vlab%2Frouting-services-courier.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.carlos-vlab%2Frouting-services-courier?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ec9f809ce5004e35…, first seen 2026-10-17, included at leaf 160 of 34,189. Version history · verify what your client received.
Compare: most reliable ml servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 22:03 UTC, the Carlos Vlab Routing Services Courier MCP server is unknown with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.
Carlos Vlab Routing Services Courier MCP server advertises 1 tool, including recommend_model_for_task.
Point your MCP client at this streamable-http endpoint: https://routing-courier-mcp-production.up.railway.app/mcp
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.