Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Shanghai Streets Travel Guide

REMOTE · WWW.SHANGHAISTREETS.CO.IL

Curated travel places, walking routes and areas for Shanghai, Jiangsu and Zhejiang, China.

71 Trust /100

Last scanned (21 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2182 tokens (~242/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://www.shanghaistreets.co.il/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.shanghaistreets.co.il CN=WE1,O=Google Trust Services,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 fbd2887dacc27e1134a1b7f9ea7b14a
SANs: www.shanghaistreets.co.il
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.shanghaistreets.co.il. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
il. DS published 35088 13 Verified
co.il. DS published 7144 13 Verified
shanghaistreets.co.il. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.shanghaistreets.co.il/mcp Verified 200
http (plaintext) http://www.shanghaistreets.co.il/mcp HTTPS enforced 301 https://www.shanghaistreets.co.il/mcp
MCP tools · 9 exposed · ~1,296 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_nearby ~170

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.

NameTypeReqDescription
categorystring–Optional specific category key filter.
familystring–Optional broad family filter (e.g. food, sights, drinks).
latnumber–Center latitude (required unless place_id is provided).
limitinteger–Maximum results to return (default 20, max 100).
lonnumber–Center longitude (required unless place_id is provided).
place_id––Existing place ID or slug to search around instead of lat/lon.
radius_kmnumber–Search radius in kilometers (default 2, max 50).

No output schema declared.

No examples provided.

get_area ~66

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).

NameTypeReqDescription
id–yesArea ID or slug (e.g. 3 or '3-old-town').

No output schema declared.

No examples provided.

get_place ~113

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.

NameTypeReqDescription
id–yesPlace ID (e.g. 42) or slug (e.g. '42-yu-garden').

No output schema declared.

No examples provided.

get_route ~85

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.

NameTypeReqDescription
id–yesRoute ID or slug (e.g. 7 or '7-wukang-road').

No output schema declared.

No examples provided.

list_areas ~100

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.

NameTypeReqDescription
categorystring–Area category filter.
limitinteger–Max results (default 20).
provincestring–Province filter.
querystring–Search query in English, Hebrew or Chinese.

No output schema declared.

No examples provided.

list_categories ~32

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_routes ~120

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.

NameTypeReqDescription
categorystring–Route category: 'alley' (city walk) or 'trail' (outdoor trail).
limitinteger–Max results (default 20).
provincestring–Province filter.
querystring–Search query in English, Hebrew or Chinese.

No output schema declared.

No examples provided.

plan_itinerary ~341

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).

NameTypeReqDescription
familiesarray–Optional place family filters to focus on (e.g. ['sights', 'food', 'drinks']).
include_geometryboolean–Include GeoJSON LineString/Polygon geometry on routes and areas (default true).
latnumber–Optional center latitude to focus around (requires lon).
limitinteger–Max places to return alongside the routes and areas (default 30, max 100).
lonnumber–Optional center longitude to focus around (requires lat).
provincestring–Province filter when the target region is known.
querystring–Destination, city, neighborhood or theme in English, Hebrew or Chinese (e.g. 'Shanghai', 'Suzhou', 'Hangzhou', 'שנגחאי', 'water town', 'Old City').
radius_kmnumber–Radius in km when lat/lon are provided (default 5, max 50).

No output schema declared.

No examples provided.

search_places ~269

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.

NameTypeReqDescription
categorystring–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).
familystring–Broad category family filter.
latnumber–Latitude for proximity filter (requires lon).
limitinteger–Max results to return (default 20, max 100).
lonnumber–Longitude for proximity filter (requires lat).
offsetinteger–Pagination offset.
provincestring–Province filter.
querystring–Search text in English, Hebrew or Chinese (e.g. 'Yu Garden', '豫园', 'xiaolongbao', 'גן יו').
radius_kmnumber–Search radius in kilometers when lat/lon are provided (default 2, max 50).

No output schema declared.

No examples provided.

Install

How do I install the Shanghai Streets Travel Guide MCP server?

Shanghai Streets Travel Guide is a hosted endpoint at https://www.shanghaistreets.co.il/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.shanghaistreets.co.il

# add to Claude Code
claude mcp add --transport http 9symphony-shanghai-streets 'https://www.shanghaistreets.co.il/mcp'
Common questions

What is the Shanghai Streets Travel Guide MCP server?

Shanghai Streets Travel Guide is an MCP server listed in the public MCP registry as io.github.9symphony/shanghai-streets. Curated travel places, walking routes and areas for Shanghai, Jiangsu and Zhejiang, China. This page covers its hosted endpoint (https://www.shanghaistreets.co.il/mcp).

Is the Shanghai Streets Travel Guide MCP server safe to use?

Shanghai Streets Travel Guide scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Shanghai Streets Travel Guide MCP server expose?

Shanghai Streets Travel Guide exposes 9 tools: plan_itinerary, search_places, get_place, find_nearby, list_routes, and 4 more. Their descriptions and schemas cost roughly 1,296 tokens of context every time the server is loaded.

Does the Shanghai Streets Travel Guide MCP server require authentication?

No. We connected to Shanghai Streets Travel Guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Shanghai Streets Travel Guide MCP server still maintained?

Shanghai Streets Travel Guide is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Shanghai Streets Travel Guide MCP server?

VerifyMCP ran 13 checks on Shanghai Streets Travel Guide, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.