POS.DO MCP Server
REMOTE · POS.DO · SCANNED SEP 27
Discover 356K+ restaurants in 20 countries: search, reviews, cultural context, time-based offers.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 828 tokens (~118/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the POS.DO MCP Server server?
POS.DO MCP Server is a hosted endpoint at https://pos.do/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pos.do
claude mcp add --transport http posdo-io-mcp-server 'https://pos.do/mcp'
{
"mcpServers": {
"posdo-io-mcp-server": {
"url": "https://pos.do/mcp"
}
}
} {
"servers": {
"posdo-io-mcp-server": {
"type": "http",
"url": "https://pos.do/mcp"
}
}
} [mcp_servers.posdo-io-mcp-server] url = "https://pos.do/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"posdo-io-mcp-server": {
"type": "remote",
"url": "https://pos.do/mcp",
"enabled": true
}
}
} openclaw mcp add posdo-io-mcp-server --url 'https://pos.do/mcp' --transport streamable-http
mcp_servers:
posdo-io-mcp-server:
url: "https://pos.do/mcp" {
"McpServers": {
"posdo-io-mcp-server": {
"Transport": "http",
"Url": "https://pos.do/mcp"
}
}
} assistant mcp add posdo-io-mcp-server -t streamable-http -u 'https://pos.do/mcp'
{
"mcpServers": {
"posdo-io-mcp-server": {
"type": "http",
"url": "https://pos.do/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Sept 26 −1
- Stability: pass → 0.93 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 21 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 15 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://pos.do/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pos.do | CN=WE1,O=Google Trust Services,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | aa8bfa534e1ef620ecd6cfe04799d47 |
| SANs: pos.do, *.pos.do | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pos.do. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| do. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://pagead2.googlesyndication.com https://adservice.google.com https://adservice.google.es https://tpc.googlesyndication.com https://www.googleadservices.com https://ep1.adtrafficquality.google https://ep2.adtrafficquality.google https://fundingchoicesmessages.google.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://unpkg.com https://js.stripe.com https://cdn.tailwindcss.com https://static.cloudflareinsights.com https://*.koah.ai https://challenges.cloudflare.com https://js.pusher.com https://checkout.razorpay.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://unpkg.com; font-src 'self' https://fonts.gstatic.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com data:; img-src 'self' data: blob: https: http:; media-src 'self' blob: https://*.amazonaws.com https://*.digitaloceans |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(self), gyroscope=(), magnetometer=(), microphone=(), payment=(self), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pos.do/mcp | Verified | 200 | |
| http (plaintext) | http://pos.do/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
book_flow_reservation ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_email | string | yes | – |
| guest_name | string | yes | – |
| guest_phone | string | yes | E.164 format, e.g. +34911234567. |
| notes | string | – | – |
| party_size | integer | – | – |
| slug | string | yes | Restaurant URL slug. |
| yield_offer_id | integer | yes | Offer ID returned by get_flow_offers. |
No output schema declared.
No examples provided.
find_restaurants_near_landmark ~102
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City hint for landmark disambiguation. |
| landmark | string | yes | Landmark name. |
| limit | integer | – | – |
| radius | integer | – | Search radius in meters. |
No output schema declared.
No examples provided.
get_cultural_context_around_restaurant ~51
Get cultural context around a restaurant: nearby monuments, museums, parks, historical sites with distance and heritage status. Powered by Wikidata.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Restaurant URL slug. |
No output schema declared.
No examples provided.
get_flow_offers ~73
POS.DO Flow time-based offers for a restaurant. Off-peak hours have bigger discounts. Returns time slots with discount percentages and remaining covers. Tagline: 'Tu hora, tu precio'.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date YYYY-MM-DD (default: today). |
| slug | string | yes | Restaurant URL slug. |
No output schema declared.
No examples provided.
get_restaurant_details ~81
Get the full profile of a restaurant by URL slug. Returns name, address, coordinates, rating, reviews count, phone, opening hours, photos, services, cuisine type, price level, current Flow offers, and cultural context.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Restaurant URL slug. Example: 'anima-e-cuore-osteria-bilbao'. |
No output schema declared.
No examples provided.
get_restaurant_reviews ~93
Get paginated reviews for a restaurant. Filter by star rating, sort by date or rating. Returns review text, author, rating, date, photos, language, owner response, and rating distribution.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| rating | integer | – | Filter by exact star rating. |
| slug | string | yes | Restaurant URL slug. |
| sort | string | – | – |
No output schema declared.
No examples provided.
search_restaurants ~195
Search restaurants in a specific city. Filter by cuisine type, price range, and features like outdoor seating, WiFi, delivery. Returns up to 20 results with name, rating, cuisine, price range, address, coordinates, photo, amenities, and current Flow offers.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name. Examples: 'Madrid', 'New York', 'Milano', 'Barcelona'. |
| cuisine | string | – | Cuisine filter. Examples: 'italian', 'mexican', 'sushi', 'spanish', 'indian'. |
| features | string | – | Comma-separated feature filters: terrace, wifi, parking, delivery, accessible. |
| limit | integer | – | – |
| price_max | integer | – | Max price level 1=budget, 4=fine dining. |
| query | string | – | Free-text search: cuisine, occasion, features (e.g. 'romantic italian terrace'). |
No output schema declared.
No examples provided.
What is the POS.DO MCP Server server?
POS.DO MCP Server is listed in the public MCP registry as io.github.posdo-io/mcp-server. Discover 356K+ restaurants in 20 countries: search, reviews, cultural context, time-based offers. This page covers its hosted endpoint (https://pos.do/mcp).
Is the POS.DO MCP Server server safe to use?
POS.DO MCP Server scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the POS.DO MCP Server server expose?
POS.DO MCP Server exposes 7 tools: search_restaurants, get_restaurant_details, get_restaurant_reviews, get_flow_offers, book_flow_reservation, and 2 more. Their descriptions and schemas cost roughly 762 tokens of context every time the server is loaded.
Does the POS.DO MCP Server server require authentication?
No. We connected to POS.DO MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the POS.DO MCP Server server still maintained?
POS.DO MCP Server is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.