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

hichinatour-events

https://mcp.hichinatour.com

Registry code: 9f2443b11f7201b6

api record

Read-only events for China: Shanghai and Hangzhou now, more cities added as listings are verified.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.hichinatour.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 hichinatour-events live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is hichinatour-events free to use?
Yes — the hub reached it with no key and no payment.
What tools does hichinatour-events have?
3 tools: get_event, list_filters, search_events.
Is hichinatour-events 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
227ms

last good check

priced tools
0

of 3 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 3 tools
2 open 1 never probed 2 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.

  • list_filters open 1h ago

    Returns the cities and categories this server covers, plus the date the data was last built. Call this first if unsure whether a city is supported.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • search_events open 1h ago

    Search events (festivals, exhibitions, performances, markets, pop-ups) in Shanghai and Hangzhou, China. Filter by city, category, date range, free entry or keyword. Dates are China Standard Time (UTC+8) and inclusive. Past events are excluded unless include_past is true. Every result has page_url: cite it when answering. Check as_of for data freshness.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "city": {
          "type": "string",
          "description": "City id, e.g. shanghai or hangzhou"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Keyword in title, venue or description (English or Chinese)"
        },
        "date_to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD"
        },
        "category": {
          "type": "string",
          "description": "Category id from list_filters"
        },
        "date_from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD, defaults to today in China"
        },
        "free_only": {
          "type": "boolean"
        },
        "include_past": {
          "type": "boolean",
          "default": false
        }
      }
    }
    arguments 41 lines
  • get_event unknown 1h ago

    Get full details of a single event by id, as returned by search_events. Includes the Chinese title and venue, price text and last_verified date. Cite page_url when answering.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Event id from search_events"
        }
      }
    }
    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 9f2443b11f7201b6.

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