mcp-registry/io.github.pipeworx-io/openrouteservice · v0.1.0
Also listed as glama/pipeworx-io/mcp-openrouteservice
As of 2026-10-25 03:03 UTC, the Pipeworx Io Openrouteservice MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
Openrouteservice MCP.
Point your MCP client at this streamable-http endpoint: https://gateway.pipeworx.io/openrouteservice/mcp
49 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
15 parameter(s) across 5 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 →
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~18,727 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
In the last 30 days: 0 tool(s) removed and 10 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.pipeworx-io%2Fopenrouteservice/fixes
{
"name": "elevation_line",
"description": "\"Elevation profile along a route\" / \"hiking trail elevation gain\" / \"topographic profile of [path]\" / \"how hilly is this route\" — elevation samples along a geometry (linestring). Pass geojson / polyline / encodedpolyline5 / encodedpolyline6. Use for hiking elevation gain, cycling grade analysis, trail planning, terrain profiles.",
"inputSchema": {
"type": "object",
"examples": [
{
"geometry": {
"type": "LineString",
"coordinates": [
[
8.681495,
49.41461
],
[
8.687872,
49.420318
]
]
},
"format_in": "geojson"
},
{
"geometry": "u{~vFvyys@fS",
"format_in": "polyline"
}
],
"required": [
"format_in",
"geometry"
],
"properties": {
"geometry": {
"description": "Per format_in",
"type": "string"
},
"format_in": {
"type": "string",
"description": "geojson | polyline | encodedpolyline5 | encodedpolyline6"
}
}
},
"annotations": {
"cost": {
"all": 1
},
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Elevation Line"
}{
"name": "elevation_point",
"description": "\"Elevation / altitude at [coordinates]\" / \"how high is [location]\" / \"height above sea level for [lat,lng]\" — elevation (meters above sea level) at a single point. Use for \"what's the elevation of Denver\", terrain queries, or attaching altitude to GPS records.",
"inputSchema": {
"type": "object",
"examples": [
{
"geometry": [
8.681495,
49.41461
],
"format_in": "point"
},
{
"geometry": {
"type": "Point",
"coordinates": [
2.352222,
48.856613
]
},
"format_in": "geojson"
}
],
"required": [
"format_in",
"geometry"
],
"properties": {
"geometry": {
"description": "Per format_in (point: [lon, lat])",
"type": "string"
},
"format_in": {
"type": "string",
"description": "point | geojson"
}
}
},
"annotations": {
"cost": {
"all": 1
},
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Elevation Point"
}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.pipeworx-io/openrouteservice"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.pipeworx-io/openrouteservice"}) over MCP.
company_facts ~1,192 tokenssubscribe ~963 tokenspolymarket_edges ~904 tokensresearch_row ~575 tokensprediction_calibration ~539 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.pipeworx-io%2Fopenrouteservice?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fopenrouteservice?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fopenrouteservice.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fopenrouteservice.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fopenrouteservice?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:a7e57d8ab84bea3c…, first seen 2026-10-25, included at leaf 62939 of 80,233. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable web servers · most reliable data servers · most reliable other servers · most reliable knowledge 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-25 03:03 UTC, the Pipeworx Io Openrouteservice MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
Pipeworx Io Openrouteservice MCP server advertises 49 tools, including ai_visibility_check, archive_compare, archive_evidence, ask_pipeworx, ask_pipeworx_beta.
Point your MCP client at this streamable-http endpoint: https://gateway.pipeworx.io/openrouteservice/mcp
Glimind scanned all 49 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.