metto-tehran-metro
Registry code: c39cf0060421d5e4
Metto — Tehran Metro MCP Server. Plan routes, find stations, and navigate 7 lines with 130+ stations. Bilingual English/Farsi, GPS nearby search, station amenities, and real-time route planning.
from a public catalogue that lists it, not from the operator
- endpoint
- https://metto.ir/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 metto-tehran-metro live?
- Yes — it answered the hub's last check (checked 41m ago). It answered 99% of checks over the last 30 days.
- Is metto-tehran-metro free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does metto-tehran-metro have?
- 4 tools: get_route, get_station, find_nearby, list_stations.
- Is metto-tehran-metro 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 99.6%· all time 99.6%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- used for
- plan a tehran metro route
- find nearest metro stations
- get metro station details
- takes → gives
- text, data → data
- tools
- 4 reads
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.
list_stations reads open 16h ago
List all metro stations. Optionally filter by line number or search query.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "line": { "type": "number", "description": "Filter by line number (1-7)" }, "search": { "type": "string", "description": "Search by name (English or Farsi)" } }, "additionalProperties": false }arguments 15 linesget_route reads unknown 16h ago
Plan a metro route between two stations. Returns stops, transfers, travel time, and path. Departure is an absolute instant: metto automatically derives the correct Iran (Asia/Tehran) weekday, Thursday, or Friday/official-holiday timetable from it — never pass a day type. Pass arrive_by instead of depart_at to get the latest feasible journey arriving at or before a deadline. Each leg also reports per-stop arrival times (Tehran HH:MM) from the timetable when available.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "from", "to" ], "properties": { "to": { "type": "string", "description": "Destination station ID (stable slug, e.g. 'tehran-sadeghiyeh'; legacy English names accepted)" }, "from": { "type": "string", "description": "Origin station ID (stable slug, e.g. 'tajrish'; legacy English names accepted)" }, "arrive_by": { "type": "string", "description": "ISO-8601 arrival deadline with explicit timezone offset or Z (e.g. '2026-09-07T14:00:00+03:30'). metto returns the latest feasible journey reaching the destination at or before this instant, derived from the real timetable (never duration subtraction). Mutually exclusive with depart_at." }, "depart_at": { "type": "string", "description": "ISO-8601 departure datetime with explicit timezone offset or Z (e.g. '2026-09-07T14:00:00+03:30'). Defaults to now. metto derives the Iran (Asia/Tehran) weekday/Thursday/Friday-or-official-holiday timetable automatically from this instant." } }, "additionalProperties": false }arguments 27 linesget_station reads unknown 41m ago
Get full details for a single station.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Station ID (stable slug, e.g. 'tajrish'; legacy English names accepted)" } }, "additionalProperties": false }arguments 14 linesfind_nearby reads unknown 16h ago
Find the closest metro stations to a GPS coordinate.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "lat", "lng" ], "properties": { "lat": { "type": "number", "description": "Latitude" }, "lng": { "type": "number", "description": "Longitude" }, "limit": { "type": "number", "description": "Max results (default 5, max 20)" } }, "additionalProperties": false }arguments 23 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 idc39cf0060421d5e4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c39cf0060421d5e4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c39cf0060421d5e4?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.