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

china-footnotes

https://chinafootnotes.com

Registry code: 0d4884c2f2859dac

api record

China Footnotes is a sourced guide for first-time foreign visitors to China. It covers Shanghai (50 places), Beijing (20 places), Xi’an (10 places), Chengdu (12 places), Chongqing (10 places), Hangzhou (10 places), plus pre-trip topics such as visas, payments and internet. Each practical field has a status: source_checked means a source was read on the stated date, not confirmed today; unknown means not found yet; conflicting means sources disagree; not_applicable means the place has no single rule (never read it as free or always open). Keep conditions, holiday rules and dates when you…

endpoint
https://chinafootnotes.com/mcp
protocol
streamable-http ·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 it live, free and safe measured by this hub
Is china-footnotes live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is china-footnotes free to use?
Yes — the hub reached it with no key and no payment.
What tools does china-footnotes have?
5 tools: get_pretrip_topic, get_place, get_current_notices, list_pretrip_topics, search_places.
Is china-footnotes 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
100%

90 days 100%· all time 100%

latency
428ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

_ what it can do 5 tools
3 open 2 never probed 3 of 5 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_current_notices open 1h ago

    List dated notices in effect today (Asia/Shanghai) for places in the China Footnotes guide, such as holiday traffic controls, temporary closures and special opening hours. Only notices the editors have entered are included; this is not a live news feed, and an empty list does not mean nothing has changed.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string",
          "description": "City id. Covered: shanghai, beijing, xian, chengdu, chongqing, hangzhou."
        },
        "placeId": {
          "type": "string",
          "description": "Only notices for this place id."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • list_pretrip_topics open 1h ago

    List the China Footnotes "Before you go" topics for foreign visitors preparing a trip to China: when to go, visa and entry, paying, internet and SIM, apps, booking ahead, getting around, safety. Covers how to prepare for a trip to China. Returns topic ids and one key fact each; details come from get_pretrip_topic.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_places open 1h ago

    Search the China Footnotes guide for sights and neighbourhoods a first-time foreign visitor might go to. Matches English or Chinese names, aliases, district, type and tags. Suited to questions about what to see or do in a covered city, and to finding a place's id from its name. Coverage today: Shanghai (50 places), Beijing (20 places), Xi’an (10 places), Chengdu (12 places), Chongqing (10 places), Hangzhou (10 places). Returns short summaries with ids and page links, best match first; matchedAll is false when no place matched the whole query and the results only share some words with it. Opening hours, tickets, booking and traveler tips come from get_place.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "tag": {
          "type": "string",
          "description": "Tag, e.g. free, paid, rainy-day, indoor, night-view, family, history, art, booking-required, closed-mon, day-trip."
        },
        "city": {
          "type": "string",
          "description": "City id. Covered: shanghai, beijing, xian, chengdu, chongqing, hangzhou."
        },
        "type": {
          "enum": [
            "museum",
            "open_district",
            "park",
            "water_town",
            "temple",
            "observation_deck",
            "classical_garden",
            "ticketed_attraction"
          ],
          "type": "string",
          "description": "Place type."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum places to return (default 10)."
        },
        "query": {
          "type": "string",
          "description": "Words to match, e.g. \"Yu Garden\", \"豫园\", \"art museum\", \"night view\". Leave empty to list places."
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • get_pretrip_topic unknown never probed

    Get one China Footnotes "Before you go" topic by id: the essentials, a checklist, dated items such as holiday crowd calendars or rule changes, traveler tips and sources. Topic ids: when-to-go, visa, arrival-card, payments, internet, apps, book-ahead, getting-around, safety. Rules such as visa policy change, so each item carries the date it was checked.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Topic id, e.g. \"visa\" or \"payments\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_place unknown never probed

    Get the full China Footnotes entry for one place by id (from search_places): why go, what to do, opening hours with weekday and seasonal rules, ticket prices, booking channels and whether passports work, last entry, metro and taxi directions, notices in effect, current and upcoming events (temporary festivals, exhibitions and shows), what was searched but not found, traveler tips, and every source with its link. Each practical field carries a status and the date its source was read; it is not a live confirmation for today.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Place id, e.g. \"yuyuan-garden\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 0d4884c2f2859dac.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0d4884c2f2859dac/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/0d4884c2f2859dac/badge.svg)](https://brick.blue/agent/0d4884c2f2859dac?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
90%

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.