io.github.toruproject/mapnetwork-mcp
REMOTE · MAPNETWORK.APP · 2 COMPONENTS · SCANNED SEP 20
Generate styled PNG/SVG map images of any location with 11 customizable color themes.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 692 tokens (~230/item across 3 items; 3 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 Management19
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.toruproject/mapnetwork-mcp server?
io.github.toruproject/mapnetwork-mcp is a hosted endpoint at https://mapnetwork.app/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 · mapnetwork.app
claude mcp add --transport http toruproject-mapnetwork-mcp 'https://mapnetwork.app/mcp'
{
"mcpServers": {
"toruproject-mapnetwork-mcp": {
"url": "https://mapnetwork.app/mcp"
}
}
} {
"servers": {
"toruproject-mapnetwork-mcp": {
"type": "http",
"url": "https://mapnetwork.app/mcp"
}
}
} [mcp_servers.toruproject-mapnetwork-mcp] url = "https://mapnetwork.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"toruproject-mapnetwork-mcp": {
"type": "remote",
"url": "https://mapnetwork.app/mcp",
"enabled": true
}
}
} openclaw mcp add toruproject-mapnetwork-mcp --url 'https://mapnetwork.app/mcp' --transport streamable-http
mcp_servers:
toruproject-mapnetwork-mcp:
url: "https://mapnetwork.app/mcp" {
"McpServers": {
"toruproject-mapnetwork-mcp": {
"Transport": "http",
"Url": "https://mapnetwork.app/mcp"
}
}
} assistant mcp add toruproject-mapnetwork-mcp -t streamable-http -u 'https://mapnetwork.app/mcp'
{
"mcpServers": {
"toruproject-mapnetwork-mcp": {
"type": "http",
"url": "https://mapnetwork.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Aug 26 0
- Schema quality: 204 → 230 ▼ functional
- “generate_route_map” added an optional parameter “name” cosmetic
- “generate_map” added an optional parameter “name” cosmetic
- “generate_markers_map” added an optional parameter “name” cosmetic
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 19.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “generate_hyperlink_map” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “generate_route_map” rewrote its description, which is the text the model reads security
- Tool “generate_markers_map” rewrote its description, which is the text the model reads security
- Schema quality: 835 → 613 ▲ functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 6.
- 23 Aug 26 −7
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “compute_route” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “generate_map” rewrote its description, which is the text the model reads security
- Schema quality: 463 → 835 ▼ functional
- “generate_map” made “place” required, so existing callers break ▼ functional
- New tool “generate_route_map” functional
- New tool “generate_markers_map” functional
- New tool “generate_hyperlink_map” functional
- “generate_map” reworded the description of “place” cosmetic
- “generate_map” dropped the optional parameter “color_set” cosmetic
- “generate_map” dropped the optional parameter “canvas_width” cosmetic
- “generate_map” dropped the optional parameter “canvas_height” cosmetic
- “generate_map” dropped the optional parameter “route” cosmetic
- “generate_map” dropped the optional parameter “name” cosmetic
- “generate_map” dropped the optional parameter “markers” cosmetic
- “generate_map” dropped the optional parameter “location” cosmetic
- “generate_map” dropped the optional parameter “format” cosmetic
- 21 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “generate_map” rewrote its description, which is the text the model reads security
- Schema quality: 295 → 231 ▲ functional
- “generate_map” added an optional parameter “location” cosmetic
- “generate_map” reworded the description of “place” cosmetic
- “generate_map” dropped the optional parameter “size_ns” cosmetic
- “generate_map” dropped the optional parameter “size_ew” cosmetic
- “generate_map” dropped the optional parameter “radius” cosmetic
- “generate_map” dropped the optional parameter “lng” cosmetic
- “generate_map” dropped the optional parameter “layers” cosmetic
- “generate_map” dropped the optional parameter “lat” cosmetic
- 13 Aug 26 0
- HSTS header: fail → pass ▲ security
- DNSSEC: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “generate_map” rewrote its description, which is the text the model reads security
- Tool “compute_route” rewrote its description, which is the text the model reads security
- Tool “compute_route” now declares an output schema ▲ functional
- First check of Tool coverage: 50 functional
- Schema quality: good → excellent functional
- “compute_route” reworded the description of “from_location” cosmetic
- “generate_map” reworded the description of “size_ns” cosmetic
- “generate_map” reworded the description of “size_ew” cosmetic
- “generate_map” reworded the description of “route” cosmetic
- “generate_map” reworded the description of “radius” cosmetic
- “generate_map” reworded the description of “layers” cosmetic
- “generate_map” reworded the description of “color_set” cosmetic
- “generate_map” dropped the optional parameter “config” cosmetic
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 20 Sept 2026 · Probed https://mapnetwork.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mapnetwork.app | CN=YE1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6d1f18369a3372187a9f78470fff43a4957 |
| SANs: mapnetwork.app, www.mapnetwork.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mapnetwork.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| mapnetwork.app. | present | 2371 | 13 | Verified |
| mapnetwork.app. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=86400; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mapnetwork.app/mcp | Verified | 200 | |
| http (plaintext) | http://mapnetwork.app/mcp | HTTPS enforced | 301 | https://mapnetwork.app/mcp |
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 →
generate_map ~83
Generate a styled map image centered on a single place. Returns a download+link as text, not image bytes. Example: place='Tokyo Station'.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional: display name for the map. If omitted, the server derives one automatically from place. |
| place | string | yes | Place name to center the map on (geocoded server-side). |
No output schema declared.
No examples provided.
generate_markers_map ~127
Generate a map with multiple pinned locations. Example: markers=[{"label": "Tokyo Tower", "link": "https://www.tokyotower.co.jp/"}, {"label": "Zojoji Temple"}].
| Name | Type | Req | Description |
|---|---|---|---|
| markers | array | yes | Locations to pin on the map. At least one required. |
| name | string | – | Optional: display name for the map. If omitted, the server derives one automatically from place/markers. |
| place | string | – | Optional: place to center the map on. If omitted, the center is computed automatically from the markers. |
No output schema declared.
No examples provided.
generate_route_map ~161
Compute a walking/driving route between two places and generate a map with it overlaid. Both endpoints are pinned automatically — do not also call generate_markers_map for them. Example: from='Tokyo Station', to='Tokyo Tower', mode='walking'.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Route start. Place name to geocode. |
| mode | string | – | 'walking' (default) or 'driving'. |
| name | string | – | Optional: display name for the map. If omitted, the server derives one automatically from place/route. |
| place | string | – | Optional: place to center the map on. If omitted, the center is computed automatically from the route. |
| to | string | yes | Route end. Place name to geocode. |
No output schema declared.
No examples provided.
What is the io.github.toruproject/mapnetwork-mcp server?
io.github.toruproject/mapnetwork-mcp is listed in the public MCP registry as io.github.toruproject/mapnetwork-mcp. Generate styled PNG/SVG map images of any location with 11 customizable color themes. This page covers its hosted endpoint (https://mapnetwork.app/mcp).
Is the io.github.toruproject/mapnetwork-mcp server safe to use?
io.github.toruproject/mapnetwork-mcp scores 69 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 io.github.toruproject/mapnetwork-mcp server expose?
io.github.toruproject/mapnetwork-mcp exposes 3 tools: generate_map, generate_markers_map, generate_route_map. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.
Does the io.github.toruproject/mapnetwork-mcp server require authentication?
No. We connected to io.github.toruproject/mapnetwork-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.toruproject/mapnetwork-mcp server still maintained?
io.github.toruproject/mapnetwork-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.