mcp-registry/io.github.posdo-io/mcp-server · v1.0.0
Also listed as glama/posdo-io/posdo-mcp-server
As of 2026-10-21 17:11 UTC, the Posdo Io MCP server is up with a Glimind reliability score of 70/100 (grade C). Over the last 30 days it answered 98.5% of Glimind's liveness checks. It had 411 outages in 90 days, with a median recovery of 5 minutes.
Discover 356K+ restaurants in 20 countries: search, reviews, cultural context, time-based offers.
Claude Code
claude mcp add --transport http posdo-io-mcp-server https://pos.do/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"posdo-io-mcp-server": {
"type": "http",
"url": "https://pos.do/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 of 7 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 →
9 parameter(s) across 4 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 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
Reachable 98.5% of the time over the last 30 days; median recovery 5 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~1,889 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.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.posdo-io%2Fmcp-server/fixes
{
"name": "book_flow_reservation",
"description": "Make a reservation at a Flow-discounted time slot. Phone must be E.164 (e.g. +34911234567). To make retries safe, send the same Idempotency-Key HTTP header on retries (any UUID); replays within 24h return the original reservation. Rate limited to 5 reservations per email per day and 10 attempts per IP per minute.",
"inputSchema": {
"type": "object",
"required": [
"slug",
"yield_offer_id",
"guest_name",
"guest_email",
"guest_phone"
],
"properties": {
"slug": {
"type": "string",
"description": "Restaurant URL slug."
},
"notes": {
"type": "string"
},
"guest_name": {
"type": "string"
},
"party_size": {
"type": "integer",
"default": 2,
"maximum": 20,
"minimum": 1
},
"guest_email": {
"type": "string",
"format": "email"
},
"guest_phone": {
"type": "string",
"pattern": "^\\+[1-9]\\d{7,14}$",
"description": "E.164 format, e.g. +34911234567."
},
"yield_offer_id": {
"type": "integer",
"description": "Offer ID returned by get_flow_offers."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "find_restaurants_near_landmark",
"description": "Find restaurants near a famous landmark (monument, museum, park). Returns landmark info from Wikidata + nearby restaurants sorted by walking distance. Examples: 'Sagrada Familia', 'Colosseum', 'Central Park', 'Tour Eiffel'.",
"inputSchema": {
"type": "object",
"required": [
"landmark"
],
"properties": {
"city": {
"type": "string",
"description": "City hint for landmark disambiguation."
},
"limit": {
"type": "integer",
"default": 10,
"maximum": 15,
"minimum": 1
},
"radius": {
"type": "integer",
"default": 1000,
"maximum": 5000,
"minimum": 200,
"description": "Search radius in meters."
},
"landmark": {
"type": "string",
"description": "Landmark name."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_cultural_context_around_restaurant",
"description": "Get cultural context around a restaurant: nearby monuments, museums, parks, historical sites with distance and heritage status. Powered by Wikidata.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Restaurant URL slug."
}
}
},
"annotations": {
"readOnlyHint": true
}
}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.posdo-io/mcp-server"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.posdo-io/mcp-server"}) over MCP.
search_restaurants ~285 tokensbook_flow_reservation ~258 tokensfind_restaurants_near_landmark ~187 tokensget_restaurant_reviews ~187 tokensget_flow_offers ~130 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.posdo-io%2Fmcp-server?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.posdo-io%2Fmcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.posdo-io%2Fmcp-server.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.posdo-io%2Fmcp-server.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.posdo-io%2Fmcp-server?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:490ef7ec31f4d49a…, first seen 2026-10-17, included at leaf 10473 of 40,660. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable search servers · most reliable knowledge servers · most reliable data 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-21 17:11 UTC, the Posdo Io MCP server is up with a Glimind reliability score of 70/100 (grade C). Over the last 30 days it answered 98.5% of Glimind's liveness checks. It had 411 outages in 90 days, with a median recovery of 5 minutes.
Posdo Io MCP server advertises 7 tools, including book_flow_reservation, find_restaurants_near_landmark, get_cultural_context_around_restaurant, get_flow_offers, get_restaurant_details.
Point your MCP client at this streamable-http endpoint: https://pos.do/mcp
Glimind scanned all 7 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.