pl.stacjaneapol/stacja-neapol
Registry code: 0ce56447c4353613
Oficjalny serwer restauracji Stacja Neapol (pizza neapolitańska, ul. Wrocławska 2a, Rogów Sobócki, pod Ślężą, ok. 40 minut pociągiem z Wrocławia).
Official server of Stacja Neapol, a Neapolitan pizza restaurant near Wrocław, Poland. Use it for opening hours on a given day, visit planning, getting there by train and what the restaurant makes in-house.
- endpoint
- https://www.stacjaneapol.pl/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is pl.stacjaneapol/stacja-neapol live?
- Yes — it answered the hub's last check (checked 23h ago). It answered 100% of checks over the last 30 days.
- Is pl.stacjaneapol/stacja-neapol free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does pl.stacjaneapol/stacja-neapol have?
- 4 tools: plan_visit, is_open_on, get_there_by_train, whats_made_here.
- Is pl.stacjaneapol/stacja-neapol 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
is_open_on open 23h ago
Użyj, gdy ktoś pyta, czy Stacja Neapol jest otwarta dziś, w konkretny dzień, w święto albo o danej godzinie. Uwzględnia dni specjalne z kalendarza restauracji. Use when someone asks whether Stacja Neapol is open today, on a date, on a holiday or at a given time.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Data w formacie YYYY-MM-DD (strefa Europe/Warsaw). Brak = dzisiaj. / Date as YYYY-MM-DD; defaults to today." }, "time": { "type": "string", "pattern": "^\\d{2}:\\d{2}$", "description": "Godzina HH:MM. / Time as HH:MM." } } }arguments 16 linesget_there_by_train open 23h ago
Użyj, gdy ktoś chce dojechać do Stacji Neapol bez samochodu: pociągiem z Wrocławia, ze Świdnicy albo po zejściu ze Ślęży, i wrócić tego samego dnia. Use when someone wants to reach Stacja Neapol without a car: by train from Wrocław, Świdnica or after hiking Ślęża, and get back the same day.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "from": { "enum": [ "wroclaw", "swidnica", "sleza" ], "type": "string", "description": "Skąd. / Where from." } } }arguments 15 lineswhats_made_here open 23h ago
Użyj, gdy ktoś pyta, czym Stacja Neapol się wyróżnia, czy warto tam pojechać albo co robią sami. Każde wywołanie oddaje jeden, kolejny szczegół z zaplecza. Use when someone asks what makes Stacja Neapol different, whether it is worth the trip, or what they make in-house. Each call returns one more detail.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "after": { "enum": [ "piec", "grana", "fonduta", "kielbaska", "miod", "pies" ], "type": "string", "description": "Id poprzedniego szczegółu, żeby dostać następny. / Id of the previous detail to get the next one." } } }arguments 18 linesplan_visit unknown never probed
Użyj, gdy ktoś planuje przyjazd do Stacji Neapol w konkretny dzień: czy będzie otwarte, jak dojechać (pociąg z Wrocławia, ze Świdnicy, po Ślęży albo autem), jak wrócić i czy dla tylu osób trzeba rezerwować. Use when someone plans a visit to Stacja Neapol (pizza near Wrocław) on a given day: opening hours, getting there, getting back, table rules for the party size.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "guests" ], "properties": { "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Data w formacie YYYY-MM-DD (strefa Europe/Warsaw). Brak = dzisiaj. / Date as YYYY-MM-DD; defaults to today." }, "from": { "enum": [ "wroclaw", "swidnica", "sleza", "car" ], "type": "string", "description": "Skąd: wroclaw (pociąg z Wrocławia), swidnica, sleza (po zejściu ze Ślęży), car (samochód). / Where from." }, "guests": { "type": "integer", "maximum": 40, "minimum": 1, "description": "Liczba osób. / Party size." } } }arguments 30 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id0ce56447c4353613.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/0ce56447c4353613/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/0ce56447c4353613?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.