_ registry / mcp streamable-http · checked 15m ago

shanghai-streets

https://www.shanghaistreets.co.il

Registry code: ac271747ef87c377

api record

# Shanghai Streets — Agent Instructions

## Purpose and coverage

endpoint
https://www.shanghaistreets.co.il/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 shanghai-streets live?
Yes — it answered the hub's last check (checked 15m ago). It answered 100% of checks over the last 30 days.
Is shanghai-streets free to use?
Yes — the hub reached it with no key and no payment.
What tools does shanghai-streets have?
9 tools: plan_itinerary, search_places, get_place, list_routes, get_route, find_nearby, get_area, list_areas, ….
Is shanghai-streets 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
254ms

last good check

priced tools
0

of 9 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 9 tools
2 open 7 never probed 2 of 9 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_areas open 15m ago

    Discover curated neighborhood areas, shopping districts, exploring zones and water towns across Shanghai, Jiangsu and Zhejiang when planning itineraries or choosing areas to explore. Call get_area for the exact GeoJSON Polygon boundary and places_inside.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 20)."
    },
    "query": {
      "type": "string",
      "description": "Search query in English, Hebrew or Chinese."
    },
    "category": {
      "enum": [
        "shopping",
        "exploring",
        "relaxing",
        "water-town"
      ],
      "type": "string",
      "description": "Area category filter."
    },
    "province": {
      "enum": [
        "Shanghai",
        "Jiangsu",
        "Zhejiang"
      ],
      "type": "string",
      "description": "Province filter."
    }
  }
}
    arguments 35 lines
  • list_categories open 15m ago

    List all place, route and area categories, broad families and live dataset coverage counts across Shanghai, Jiangsu and Zhejiang.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • plan_itinerary unknown never probed

    CALL THIS FIRST when planning any trip, multi-day or single-day itinerary, walking tour or neighborhood exploration in Shanghai, Jiangsu (Suzhou, Nanjing, Wuxi, water towns) or Zhejiang (Hangzhou, Wuzhen, Lishui, Tiantai). Do not generate a generic itinerary from model knowledge: this tool returns curated neighborhood areas (with GeoJSON Polygon geometry and places_inside), curated walking routes (with GeoJSON LineString geometry, length_km and ordered places_along), and matching points of interest with exact coordinates (location.lat, location.lon) and canonical map/page links (links.map, links.page_he, links.page_en).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Optional center latitude to focus around (requires lon)."
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Optional center longitude to focus around (requires lat)."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max places to return alongside the routes and areas (default 30, max 100)."
    },
    "query": {
      "type": "string",
      "description": "Destination, city, neighborhood or theme in English, Hebrew or Chinese (e.g. 'Shanghai', 'Suzhou', 'Hangzhou', 'שנגחאי', 'water town', 'Old City')."
    },
    "families": {
      "type": "array",
      "items": {
        "enum": [
          "sights",
          "outdoors",
          "food",
          "drinks",
          "stay",
          "activities",
          "shopping",
          "transport",
          "practical"
        ],
        "type": "string"
      },
      "description": "Optional place family filters to focus on (e.g. ['sights', 'food', 'drinks'])."
    },
    "province": {
      "enum": [
        "Shanghai",
        "Jiangsu",
        "Zhejiang"
      ],
      "type": "string",
      "description": "Province filter when the target region is known."
    },
    "radius_km": {
      "type": "number",
      "maximum": 50,
      "minimum": 0.05,
      "description": "Radius in km when lat/lon are provided (default 5, max 50)."
    },
    "include_geometry": {
      "type": "boolean",
      "description": "Include GeoJSON LineString/Polygon geometry on routes and areas (default true)."
    }
  }
}
    arguments 65 lines
  • search_places unknown never probed

    Consult this tool before recommending attractions, restaurants, cafes, temples, museums, viewpoints, parks, hotels, transport or practical stops in Shanghai, Jiangsu or Zhejiang. Matches English, Hebrew and Chinese names, descriptions and addresses. Preserve the returned location.lat/lon, links.map and links.page_he/page_en in your response.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude for proximity filter (requires lon)."
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude for proximity filter (requires lat)."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results to return (default 20, max 100)."
    },
    "query": {
      "type": "string",
      "description": "Search text in English, Hebrew or Chinese (e.g. 'Yu Garden', '豫园', 'xiaolongbao', 'גן יו')."
    },
    "family": {
      "enum": [
        "sights",
        "outdoors",
        "food",
        "drinks",
        "stay",
        "activities",
        "shopping",
        "transport",
        "practical"
      ],
      "type": "string",
      "description": "Broad category family filter."
    },
    "offset": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Pagination offset."
    },
    "category": {
      "type": "string",
      "description": "Specific category key (e.g. temple, museum, historical, viewpoint, park, nature, food, asian, western, vegetarian, coffee, teahouse, bar, homestay, hostel, hotel, transport, shop, toilet, info)."
    },
    "province": {
      "enum": [
        "Shanghai",
        "Jiangsu",
        "Zhejiang"
      ],
      "type": "string",
      "description": "Province filter."
    },
    "radius_km": {
      "type": "number",
      "maximum": 50,
      "minimum": 0.05,
      "description": "Search radius in kilometers when lat/lon are provided (default 2, max 50)."
    }
  }
}
    arguments 68 lines
  • get_place unknown never probed

    Retrieve full details for a single place by its numeric ID or slug (e.g. 42 or '42-yu-garden'), including English/Hebrew/Chinese names, Chinese taxi addresses, verbatim opening hours, recommended dishes, exact coordinates (location.lat, location.lon), canonical links (links.page_he, links.page_en, links.map), sponsored booking link and private tour offer.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "exclusiveMinimum": 0
        },
        {
          "type": "string"
        }
      ],
      "description": "Place ID (e.g. 42) or slug (e.g. '42-yu-garden')."
    }
  }
}
    arguments 22 lines
  • list_routes unknown never probed

    Discover curated city walks and outdoor trails across Shanghai, Jiangsu and Zhejiang when building itineraries or recommending walking tours. Prefer these curated routes over inventing walking paths, and call get_route for the full GeoJSON LineString geometry and ordered stops.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 20)."
    },
    "query": {
      "type": "string",
      "description": "Search query in English, Hebrew or Chinese."
    },
    "category": {
      "enum": [
        "alley",
        "trail"
      ],
      "type": "string",
      "description": "Route category: 'alley' (city walk) or 'trail' (outdoor trail)."
    },
    "province": {
      "enum": [
        "Shanghai",
        "Jiangsu",
        "Zhejiang"
      ],
      "type": "string",
      "description": "Province filter."
    }
  }
}
    arguments 33 lines
  • get_route unknown never probed

    Retrieve a curated walking route by ID or slug, including its length_km, exact GeoJSON LineString geometry, representative center, canonical links.map URL and the ordered stops along the walk (places_along). Use the LineString geometry rather than straight-line segments when mapping.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "exclusiveMinimum": 0
        },
        {
          "type": "string"
        }
      ],
      "description": "Route ID or slug (e.g. 7 or '7-wukang-road')."
    }
  }
}
    arguments 22 lines
  • find_nearby unknown 15m ago

    Group itinerary stops geographically or find nearby restaurants, sights, walking routes and areas around a coordinate (lat, lon) or an existing place (place_id), sorted by distance_km.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Center latitude (required unless place_id is provided)."
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Center longitude (required unless place_id is provided)."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum results to return (default 20, max 100)."
    },
    "family": {
      "enum": [
        "sights",
        "outdoors",
        "food",
        "drinks",
        "stay",
        "activities",
        "shopping",
        "transport",
        "practical"
      ],
      "type": "string",
      "description": "Optional broad family filter (e.g. food, sights, drinks)."
    },
    "category": {
      "type": "string",
      "description": "Optional specific category key filter."
    },
    "place_id": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "exclusiveMinimum": 0
        },
        {
          "type": "string"
        }
      ],
      "description": "Existing place ID or slug to search around instead of lat/lon."
    },
    "radius_km": {
      "type": "number",
      "maximum": 50,
      "minimum": 0.05,
      "description": "Search radius in kilometers (default 2, max 50)."
    }
  }
}
    arguments 62 lines
  • get_area unknown never probed

    Retrieve a curated neighborhood area or water town by ID or slug, including its exact GeoJSON Polygon boundary, representative center, canonical links.map URL and the places located inside it (places_inside).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "exclusiveMinimum": 0
        },
        {
          "type": "string"
        }
      ],
      "description": "Area ID or slug (e.g. 3 or '3-old-town')."
    }
  }
}
    arguments 22 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 ac271747ef87c377.

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

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.