_ registry / mcp streamable-http · checked 1h ago

POS.DO MCP Server

listed under this name in a public catalogue; the server gives only its address, pos.do

https://pos.do

Registry code: 0dd85113090a37b0

api record

POS.DO discovery server. Search 356K+ restaurants across 50+ countries with reviews, photos, cultural context, and Flow time-based offers. All data is read-only except book_flow_reservation. Phone numbers in book_flow_reservation must be E.164 (e.g. +34911234567).

endpoint
https://pos.do/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is POS.DO MCP Server live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is POS.DO MCP Server free to use?
Yes — the hub reached it with no key and no payment.
What tools does POS.DO MCP Server have?
7 tools: get_cultural_context_around_restaurant, search_restaurants, get_restaurant_reviews, find_restaurants_near_landmark, get_flow_offers, book_flow_reservation, get_restaurant_details.
Is POS.DO MCP Server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.4%

90 days 97.7%· all time 97.7%

latency
406ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 311 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search restaurants in a city
  • find restaurants near a landmark
  • get restaurant reviews
  • get discounted time slot offers
  • book a restaurant reservation
takes → gives
text → data
tools
6 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_cultural_context_around_restaurant reads unknown 12h ago

    Get cultural context around a restaurant: nearby monuments, museums, parks, historical sites with distance and heritage status. Powered by Wikidata.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Restaurant URL slug."
        }
      }
    }
    arguments 12 lines
  • search_restaurants reads unknown 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City name. Examples: 'Madrid', 'New York', 'Milano', 'Barcelona'."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Free-text search: cuisine, occasion, features (e.g. 'romantic italian terrace')."
        },
        "cuisine": {
          "type": "string",
          "description": "Cuisine filter. Examples: 'italian', 'mexican', 'sushi', 'spanish', 'indian'."
        },
        "features": {
          "type": "string",
          "description": "Comma-separated feature filters: terrace, wifi, parking, delivery, accessible."
        },
        "price_max": {
          "type": "integer",
          "maximum": 4,
          "minimum": 1,
          "description": "Max price level 1=budget, 4=fine dining."
        }
      }
    }
    arguments 36 lines
  • get_restaurant_reviews reads unknown 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Restaurant URL slug."
        },
        "sort": {
          "enum": [
            "recent",
            "rating_high",
            "rating_low"
          ],
          "type": "string",
          "default": "recent"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 30,
          "minimum": 1
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0
        },
        "rating": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Filter by exact star rating."
        }
      }
    }
    arguments 38 lines
  • find_restaurants_near_landmark reads unknown 12h ago

    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'.

    mcp-tool

    {
      "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."
        }
      }
    }
    arguments 29 lines
  • get_flow_offers reads unknown 12h ago

    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'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date YYYY-MM-DD (default: today)."
        },
        "slug": {
          "type": "string",
          "description": "Restaurant URL slug."
        }
      }
    }
    arguments 17 lines
  • book_flow_reservation changes data unknown never probed

    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.

    mcp-tool

    {
      "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."
        }
      }
    }
    arguments 41 lines
  • get_restaurant_details reads unknown 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Restaurant URL slug. Example: 'anima-e-cuore-osteria-bilbao'."
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0dd85113090a37b0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0dd85113090a37b0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0dd85113090a37b0/badge.svg)](https://brick.blue/agent/0dd85113090a37b0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.