squidmaps
REMOTE · SQUIDMAPS.IO
Make a web map of places, routes and areas, and get a link to share it.
Available components
Last scanned (2 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_map). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 842 tokens (~168/item across 5 items; 4 tools + 1 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 Management23
- Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 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.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_map” rewrote its description, which is the text the model reads security
- Tool “get_map_spec” rewrote its description, which is the text the model reads security
- Tool “preview_map” rewrote its description, which is the text the model reads security
- Tool “update_map” rewrote its description, which is the text the model reads security
- Schema quality: 137 → 168 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “create_map” changed its title: Make a map → Make a shareable map cosmetic
- Tool “get_map_spec” changed its title: Read the squidmaps map spec → Read how to write a map cosmetic
- Tool “preview_map” changed its title: See a map → Look at a map cosmetic
- 29 Oct 26 67
First indexed and scored.
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 5 Nov 2026 · Probed https://squidmaps.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=squidmaps.io | CN=YE1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5febf02a255072ebc804e13cd69a389fc14 |
| SANs: *.squidmaps.io, squidmaps.io | ||||||
| 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 insecure
Validation of squidmaps.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| squidmaps.io. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://squidmaps.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://squidmaps.io/api/mcp | HTTPS enforced | 301 | https://squidmaps.io/api/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 →
create_map Make a shareable map ~161
Make a web map of places, routes or areas, and get a link anyone can open to see it, with no code and no account. Write it as the map document get_map_spec describes. The link works for an hour after the map last changed; opening it, the person can add the map to their squidmaps account to keep it, publish it and share it for good. Returns an id and editToken: keep them, to change this map with update_map rather than making another.
| Name | Type | Req | Description |
|---|---|---|---|
| map | object | yes | A squidmaps map document (see get_map_spec): "features" (GeoJSON features, styled with "@" properties), and optionally "name", "description", "basemap", "extent", "view" and "legend". |
No output schema declared.
No examples provided.
get_map_spec Read how to write a map ~81
Read this first when someone wants a map: of places, a route or an area, or of data like a CSV or GeoJSON, to look at or to share with a link. It's how squidmaps maps are written: GeoJSON features, how they're styled, and their popups, title panel and legend. Then make the map with create_map.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_map Look at a map ~190
A picture of a map made with create_map, as people who open its link see it, to check it before you share the link: where things are, their styles, its title panel and legend. 1200×630 by default, the shape most people see it in. Ask for another size to fit the map's shape: taller (like 800×1000) for a map that runs north to south, wider (like 1000×600) for one that runs east to west. The picture shows what fits on a screen that size, so a larger one shows more of a large map. At most 1,000,000 pixels (width × height).
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | – | The picture's height, in pixels |
| id | string | yes | The map's id, from create_map |
| width | integer | – | The picture's width, in pixels |
No output schema declared.
No examples provided.
update_map Change a map ~153
Change a map made with create_map when the person asks for changes, keeping its link: anyone who has the link sees the change, and it keeps working another hour. Send the whole changed map document, not just what changed: it replaces the map. Fails once someone has added the map to their account.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | yes | The editToken from create_map |
| id | string | yes | The map's id, from create_map |
| map | object | yes | A squidmaps map document (see get_map_spec): "features" (GeoJSON features, styled with "@" properties), and optionally "name", "description", "basemap", "extent", "view" and "legend". |
No output schema declared.
No examples provided.
How do I install the squidmaps MCP server?
squidmaps is a hosted endpoint at https://squidmaps.io/api/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 · squidmaps.io
claude mcp add --transport http io-squidmaps-squidmaps 'https://squidmaps.io/api/mcp'
What is the squidmaps MCP server?
squidmaps is an MCP server listed in the public MCP registry as io.squidmaps/squidmaps. Make a web map of places, routes and areas, and get a link to share it. This page covers its hosted endpoint (https://squidmaps.io/api/mcp).
Is the squidmaps MCP server safe to use?
squidmaps scores 70 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 squidmaps MCP server expose?
squidmaps exposes 4 tools: get_map_spec, create_map, update_map, preview_map. Their descriptions and schemas cost roughly 585 tokens of context every time the server is loaded.
Does the squidmaps MCP server require authentication?
No. We connected to squidmaps without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the squidmaps MCP server still maintained?
squidmaps is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.