7Maps MCP server
io.github.XLSV777/7mapsXLSV777streamable-httpv1.0.3Scanned
7Maps, the live directory of MCP servers, run by 7IT Solutions: which work today, what changed.
16 tools: 13 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
13 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the 7Maps MCP server can do
The 7Maps MCP server is published by the GitHub account XLSV777. It has 16 tools. It can create or change data (13 tools: report_road, submit_mcp_server, claim_mcp_server, my_server_report and 9 more), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (submit_mcp_server and claim_mcp_server); 1 tool can send data out of your system (submit_mcp_server).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 1.0.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Changes things 13Claude Code: ask
about_7mapsUse this when deciding whether to use 7Maps, or when asked what it is: what the map covers right now, what each 7Maps tool answers, what a call costs, and how it saves an agent tok…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when deciding whether to use 7Maps, or when asked what it is: what the map covers right now, what each 7Maps tool answers, what a call costs, and how it saves an agent tokens, time and failed calls compared with connecting to MCP servers blind. Includes a live worked example on a real server from the map (changes daily), and, if you name a server, a quote of what 7Maps would save you on it (tokens and time) before you pay. No charge.
Annotations the server declares
- title: What 7Maps is (no charge)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
changes_sinceUse this to check all the MCP servers you depend on in one call instead of one by one: give up to 50 servers and the date of your last check, and get only what changed since then (…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this to check all the MCP servers you depend on in one call instead of one by one: give up to 50 servers and the date of your last check, and get only what changed since then (outages, recoveries, tools added, removed or changed, risk increases, silent changes). Most answers are "nothing changed". Paid per call (see list_paid_tools). Reads the map only.
Annotations the server declares
- title: What changed on my MCP servers (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
claim_mcp_serverUse this when the person you work for owns or runs an MCP server that is on the 7Maps map and wants its page to show it is owner verified, add a short note for agents (rate limits,…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this when the person you work for owns or runs an MCP server that is on the 7Maps map and wants its page to show it is owner verified, add a short note for agents (rate limits, sign-up, what the tools are for), or get a live status badge for their README. Verified owners' servers are checked every 5 minutes (uptime on the page and badge), and with alert_url the owner gets a message when the server stops answering and when it is back. First call returns the proof options (a line in /.well-known/7maps-verify.txt on the server's host, a DNS TXT record, or for io.github registry names a file in the GitHub repo) and, for a server with no owner yet, claim_check; once the proof is in place, call again with it. The first verification returns an owner secret, shown once: keep it, because later changes to an already verified server (note, alerts) need it as owner_secret. If it is lost, call with recover true, put the one-time code on the host, then call with recover_check. Verifying does not change how the server is measured or ranked. No charge.
Annotations the server declares
- title: Verify ownership of an MCP server on 7Maps
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
my_7maps_usageUse this when the person you work for asks what 7Maps has done for them: calls made with their personal 7Maps key today, in the last 7 days and in the last 30 days, servers checked…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when the person you work for asks what 7Maps has done for them: calls made with their personal 7Maps key today, in the last 7 days and in the last 30 days, servers checked, an estimate of the tokens saved compared with finding the same thing out without 7Maps, failures avoided (servers not answering that were skipped, risk changes caught by watch or verify_lock, calls that would have failed) and the average response time. It reads the optional personal key sent with this connection (the X-7Maps-Key header); without one it says so in one line, since every 7Maps answer already states its own saving. Only that person's own counts. No charge.
Annotations the server declares
- title: My 7Maps usage (personal key)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
my_server_reportUse this when the person you work for owns an MCP server on the 7Maps map and wants to know how AI agents look for servers like it: how often agents asked 7Maps for servers in its …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when the person you work for owns an MCP server on the 7Maps map and wants to know how AI agents look for servers like it: how often agents asked 7Maps for servers in its category in the last 7 or 30 days, how often this server was shown and picked, and, for a verified owner with owner_key, the words agents used, the servers picked instead, failure reasons agents reported, uptime, tool changes, and its token cost and handshake time against similar servers. Counts only, no agent identities; demand counts appear once the category has enough requests a week. Without owner_key it returns the public numbers and how to verify ownership with claim_mcp_server. Read-only; never changes ranking or routing. No charge.
Annotations the server declares
- title: What agents looked for around your MCP server (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
preflightUse this right before calling a tool on an MCP server you have not used today, with the exact arguments you plan to send: checks that the server answers, whether it needs sign-in, …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this right before calling a tool on an MCP server you have not used today, with the exact arguments you plan to send: checks that the server answers, whether it needs sign-in, that the tool still exists under that name, and that the arguments match the tool's input schema (required, types, allowed values, unknown keys). Returns go, no_go or fix with what to change (sign_in_first, with how to connect, for a server behind sign-in), so a failed round trip and retry are avoided. Paid per check (see list_paid_tools). Never calls the server.
Annotations the server declares
- title: Will this MCP call succeed? (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
report_roadUse this after calling a tool on an MCP server (especially one 7Maps pointed you to) to report how it went: whether it worked, why not, how long it took, whether the result matched…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Use this after calling a tool on an MCP server (especially one 7Maps pointed you to) to report how it went: whether it worked, why not, how long it took, whether the result matched the description, and anything it did that you did not ask for. Fixed fields only, no open text. Reports from many agents become the server's rating and, once 7Maps confirms them with its own check, live incident alerts that every agent sees. You can also pass the same fields as last_trip on your next call of any 7Maps tool. No charge.
Annotations the server declares
- title: Report how a call to an MCP server went (7Maps)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
road_conditionsUse this before connecting to or calling any MCP server you have not used today, or before installing one that runs locally: is it up, does it need sign-in, how fast it answers, ho…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this before connecting to or calling any MCP server you have not used today, or before installing one that runs locally: is it up, does it need sign-in, how fast it answers, how many of its tools are read-only, need approval or are high risk (delete, pay, run code; automated estimates from the public tool descriptions and annotations), when its tools last changed, and the chance the next call works, from a daily check of every remote server in the official MCP registry and 30 days of history. For a local server (npm or PyPI package): version, maintainers, publisher, install scripts and supply-chain changes. Paid per check (see list_paid_tools). Reads the map only; never calls the server.
Annotations the server declares
- title: Condition of an MCP server before connecting (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
routeUse this when you need a tool for a task and do not know which MCP server to use, or when several could do it: finds servers whose tools match the task and ranks them by the chance…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when you need a tool for a task and do not know which MCP server to use, or when several could do it: finds servers whose tools match the task and ranks them by the chance the call works, how stable the server is, and least privilege (a server that can do less harm than another is preferred when both can do the task). Returns the best server and tool, alternatives and servers to avoid. Placement is never sold: the order comes only from live checks and real use. Paid per task (see list_paid_tools). Reads the map only.
Annotations the server declares
- title: Safest MCP server for a task (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
submit_mcp_serverUse this when someone has built or runs an MCP server that is not in the official MCP registry (for example a small business's own server) and wants AI agents to be able to find it…Reads text others writeCan send data outNo findings
Why it is in this group
- The name "submit_mcp_server" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Use this when someone has built or runs an MCP server that is not in the official MCP registry (for example a small business's own server) and wants AI agents to be able to find it, or asks how to get their server listed. Give the server address, or just the business's domain and the usual endpoint paths are tried. The server is observed every 6 hours for 7 days; if it answers reliably, keeps its tools stable and describes every tool, it joins the 7Maps map that agents use to choose servers. Placement cannot be bought. Returns the status page and an optional owner-verification token. No charge.
Annotations the server declares
- title: Put a new MCP server on the 7Maps map
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tool_cardUse this instead of loading a server's full tool definitions when you only need to choose a tool or prepare a call: one compact card per tool (what it does, its arguments with requ…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this instead of loading a server's full tool definitions when you only need to choose a tool or prepare a call: one compact card per tool (what it does, its arguments with required ones marked *, risk level and side effects) plus a hash of the full definition. Usually 70 to 90% fewer tokens than the server's own tool list. Optionally only the named tools. For a server that asks for sign-in before listing its tools: that it is up and how to connect (no charge). Paid per server (see list_paid_tools). Reads the map only.
Annotations the server declares
- title: Compact tool cards for an MCP server (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_lockUse this to check that an MCP server's tools are still the ones a person approved, like a lockfile: pass the lock you saved at approval (tool name to hash, as returned by watch or …1 finding
Why it is in this group
- The name "verify_lock" says "lock": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "verify_lock" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "verify_lock" says "lock": a word for a change.
Description, as the server wrote it Use this to check that an MCP server's tools are still the ones a person approved, like a lockfile: pass the lock you saved at approval (tool name to hash, as returned by watch or tool_card) and get, per tool, unchanged, changed (with any rise in risk), removed or new. Catches rug pulls, where a tool changes after approval, which MCP clients do not re-ask about. Paid per server (see list_paid_tools). Reads the map only.
Annotations the server declares
- title: Verify a pinned tool list (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
watchUse this before reusing an MCP server that a person approved earlier: tells whether its tools changed since that date, and whether any change raised the risk (a tool that now delet…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this before reusing an MCP server that a person approved earlier: tells whether its tools changed since that date, and whether any change raised the risk (a tool that now deletes, pays or runs code), including silent changes made without a new server version. If the risk went up, ask the person to approve again before calling it. Paid per check (see list_paid_tools). Reads the map only.
Annotations the server declares
- title: Has an approved MCP server changed? (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
find_toolUse this when you need a tool for a job and do not know which MCP server has one: searches every tool of every public MCP server on the 7Maps map (over 200,000 tools, probed daily)…No findings
Why it is in this group
- The name "find_tool" says "find": a word for reading.
Description, as the server wrote it Use this when you need a tool for a job and do not know which MCP server has one: searches every tool of every public MCP server on the 7Maps map (over 200,000 tools, probed daily) and returns the best matches with an automated estimate of what each tool can do (read-only, changes data, high risk), whether its server is answering now, its handshake time, the tokens its tool list costs to load, and a page to check it. Filter to read-only tools, servers answering now, a latency or token ceiling. Copies of the same tool on several servers are collapsed. No charge. To have 7Maps pick one server and tool for you with alternatives, use route.
Annotations the server declares
- title: Find an MCP tool for a job (7Maps)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_paid_toolsUse this before calling a paid 7IT tool, to see what each costs and how to pay: per call in USDC on Base via x402 (no account; for agents whose owner approved a budget in advance),…No findings
Why it is in this group
- The name "list_paid_tools" says "list": a word for reading.
Description, as the server wrote it Use this before calling a paid 7IT tool, to see what each costs and how to pay: per call in USDC on Base via x402 (no account; for agents whose owner approved a budget in advance), or a monthly plan license key. No charge; returns prices, plans and payment details.
Annotations the server declares
- title: Prices of the paid 7IT tools
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
resolveUse this when you need an MCP server for a job and want a signed, expiring answer you can verify: returns up to 10 servers that answered at their last check, each with a stable ID,…No findings
Why it is in this group
- The name "resolve" says "resolve": a word for reading.
Description, as the server wrote it Use this when you need an MCP server for a job and want a signed, expiring answer you can verify: returns up to 10 servers that answered at their last check, each with a stable ID, its address, its status, when it was checked and an Ed25519 signature (JWS) valid for 48 hours. The keys are at https://7it.co.il/.well-known/capability-resolver. It never connects you to a server; your client decides. No charge.
Annotations the server declares
- title: Resolve a job to MCP servers (signed)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:01 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 13
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 13 tools that change things (13 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://7it.co.il/7maps/mcp?via=registry: tools/list returned 16 tools to an anonymous client, including report_road (write), submit_mcp_server (write), claim_mcp_server (write), my_server_report (write), my_7maps_usage (write) and 8 more
Findings
Matches of fixed checks, with the text they matched.
- Warnverify_lock
The server marks "verify_lock" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "verify_lock" says "lock": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:my_server_reportChanges thingsdescription
- Changed:report_roadChanges thingsdescription
- Changed:routeChanges thingsdescription
Tools1 added, 11 changed.+1 added~11 changedView diff
- Added:resolveOnly reads
- Changed:changes_sinceChanges thingsinputSchema
- Changed:claim_mcp_serverChanges thingsdescriptioninputSchema
- Changed:find_toolOnly readsinputSchema
- Changed:my_7maps_usageChanges thingsinputSchema
- Changed:preflightChanges thingsdescriptioninputSchema
- Changed:report_roadChanges thingsdescriptioninputSchema
- Changed:road_conditionsChanges thingsinputSchema
- Changed:routeChanges thingsinputSchema
- Changed:tool_cardChanges thingsdescriptioninputSchema
- Changed:verify_lockChanges thingsinputSchema
- Changed:watchChanges thingsinputSchema
Install
Pinned to version 1.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http 7maps https://7it.co.il/7maps/mcp?via=registryclaude mcp add --transport http 7maps https://7it.co.il/7maps/mcp?via=registryRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__7maps__find_tool",
"mcp__7maps__resolve",
"mcp__7maps__list_paid_tools"
],
"ask": [
"mcp__7maps__report_road",
"mcp__7maps__submit_mcp_server",
"mcp__7maps__claim_mcp_server",
"mcp__7maps__my_server_report",
"mcp__7maps__my_7maps_usage",
"mcp__7maps__about_7maps",
"mcp__7maps__road_conditions",
"mcp__7maps__watch",
"mcp__7maps__route",
"mcp__7maps__tool_card",
"mcp__7maps__preflight",
"mcp__7maps__verify_lock",
"mcp__7maps__changes_since"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as 7maps. Review it before you use it.
Capability tags behind 2 rules
- mcp__7maps__submit_mcp_server untrusted-input, outbound
- mcp__7maps__claim_mcp_server untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.XLSV777/7maps/verify?hash=700898091830a682e12825d5ae8c4ee86440049cef9cd0bf45b05dd9c0036b2f" | jq -e '.changed == false'Pinned hash 700898091830, from Nov 12, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.XLSV777/7maps/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.XLSV777/7maps)Source: MCP Registry. Synced Nov 12, 2026, 10:17 UTC.
7Maps MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the 7Maps MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 13 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the 7Maps MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the 7Maps MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the 7Maps MCP server have?
- 16 tools: 13 write, 3 read. report_road, submit_mcp_server, claim_mcp_server, my_server_report, my_7maps_usage, about_7maps, road_conditions, watch and 8 more.
Does the 7Maps MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the 7Maps MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): submit_mcp_server.
Has the 7Maps MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.