world-capitals-explorer
https://capitals.skybridge.tech
Registry code: bb2529ceeceda1ae
World capitals explorer showcasing the Skybridge framework for building interactive apps.
from a public catalogue that lists it, not from the operator
- endpoint
- https://capitals.skybridge.tech
- 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 world-capitals-explorer live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is world-capitals-explorer free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does world-capitals-explorer have?
- 1 tool: explore-capitals.
- Is world-capitals-explorer 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.5%· all time 99.5%
last good check
of 1 tools
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- explore world capital cities on a map
- get information about a capital city
- takes → gives
- text → data
- tools
- 1 reads
- note
- demo or test
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
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
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.
explore-capitals reads unknown 19h ago
Use this tool to explore world capitals. Displays an interactive map with detailed information about capital cities including population, currencies, and beautiful photos. Always use it when users ask about capitals, countries, or want to explore geography.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "Capital city name in English (e.g., 'Paris', 'Tokyo', 'Washington, D.C.', 'London', 'New Delhi')" }, "user_intent": { "type": "string", "description": "A concise summary of the user's goal, based only on what they asked. The server uses this to decide whether to route the request to its internal agent or handle it with a deterministic workflow. Include only details needed for that decision. Before sending, strip all personally identifiable information (names, emails, phone numbers, addresses, dates of birth, ID numbers, payment details, credentials, IP addresses, and device identifiers) and sensitive personal data (such as health information, religion, or precise location). Do not ask follow-up questions solely to fill in this summary." } } }arguments 17 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 idbb2529ceeceda1ae.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/bb2529ceeceda1ae/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/bb2529ceeceda1ae?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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- everything.skybridge.tech alpic-openai-app
- ecommerce.skybridge.tech skybridge-shop
- times-up.skybridge.tech times-up
- investigation-game.skybridge.tech murder-in-the-valley
- productivity.skybridge.tech productivity-charts-example-server