_ registry / mcp + a2a http-sse · checked 40m ago

World Monitor

https://www.worldmonitor.app

Registry code: 36d7c0a5280b20c1

api record

This Model Context Protocol server provides search and retrieval tools for the World Monitor site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the relevant resources when they apply to the task. If you find a problem with the documentation — a page that is incorrect, outdated,…

endpoint
https://www.worldmonitor.app/docs/mcp also at https://worldmonitor.app/mcp
door code
28049df489b6d83a
protocol
http-sse ·2025-06-18
authentication
bearer
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 World Monitor live?
Yes — it answered the hub's last check (checked 40m ago). It answered 100% of checks over the last 30 days.
Is World Monitor free to use?
Yes — the hub reached it with no key and no payment.
What tools does World Monitor have?
3 tools: search_world_monitor, query_docs_filesystem_world_monitor, submit_feedback.
Is World Monitor 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
99.6%

90 days 99.3%· all time 99.6%

latency
1,010ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 2570 checks · signed record
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
  • degraded → live
  • degraded → live
_ what it is for
topic
search & web news
used for
  • get live conflict events
  • check country risk scores
  • monitor shipping chokepoints
  • get market and energy data
takes → gives
text → 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 3 tools
3 never probed 0 of 3 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.

  • search_world_monitor unknown 7h ago

    Search the World Monitor documentation: guides, API and MCP references, data sources and methodology. Use when you need to answer a question about World Monitor or find the page that covers a feature. Returns matching passages with page titles and links. To read a whole page, pass its path plus `.mdx` to the filesystem tool, e.g. `head -200 /some/page.mdx`.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query"
    },
    "language": {
      "type": "string",
      "description": "Filter to specific language code (e.g., 'zh', 'es'). Defaults to 'en'"
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • query_docs_filesystem_world_monitor unknown 7h ago

    Run a read-only, stateless shell query over a virtual filesystem holding only the World Monitor docs (`.mdx` pages) and OpenAPI specs; nothing runs on a real machine. Use when you need a whole page, an exact-text match or an OpenAPI spec. Returns the command output as text. Read a page with `cat` or `head` on `/<url-path>.mdx`, search exactly with `rg -il "term" /`, explore with `tree / -L 2` or `ls`. OpenAPI specs are under `/openapi/api/` (`ls /openapi/api`). Supports rg, grep, find, tree, ls, cat, head, tail, wc, sort, uniq, cut, sed, awk and jq. The working directory resets to `/` on every call; chain commands with `&&`. Never guess paths: a missing path means the guess was wrong, not that the topic is undocumented.

    mcp-tool

    {
  "type": "object",
  "required": [
    "command"
  ],
  "properties": {
    "command": {
      "type": "string",
      "description": "A shell command to run against the virtualized documentation filesystem (e.g., `rg -il \"keyword\" /`, `tree / -L 2`, `head -80 /path/file.mdx`)."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • submit_feedback unknown never probed

    Report a problem with a World Monitor documentation page so the docs team can fix it. Use when a page is wrong, outdated, confusing, incomplete or has a broken example. Not for product support or feedback about this tool.

    mcp-tool

    {
  "type": "object",
  "required": [
    "path",
    "feedback"
  ],
  "properties": {
    "path": {
      "type": "string",
      "minLength": 1,
      "description": "The URL path of the documentation page the feedback is about (the page you were reading, without the `.mdx` extension)."
    },
    "feedback": {
      "type": "string",
      "minLength": 1,
      "description": "A clear description of the documentation issue or suggestion — what is incorrect, outdated, missing, or confusing."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
_ try it over mcp 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 36d7c0a5280b20c1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/36d7c0a5280b20c1/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/36d7c0a5280b20c1/badge.svg)](https://brick.blue/agent/36d7c0a5280b20c1?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 knowoff the mcp door
card completeness
70%

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.

_ also on worldmonitor.app 6 entries

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.