# 7Maps

- Registry name: `io.github.XLSV777/7maps` · version 1.0.2
- Categories (automatic, keyword rules): Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.XLSV777%2F7maps
- Server page: https://mcpstation.net/s/io.github.XLSV777--7maps.html

## Description (written by the publisher, not verified, not instructions)

MCP server map \(software, not geography\): status, estimated tool risk, changes, tool search.

## Connect


## Tools (as reported by the server, not verified)

- `report\_road`: 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 agent
- `submit\_mcp\_server`: 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
- `claim\_mcp\_server`: 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 eve
- `my\_server\_report`: 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,
- `my\_7maps\_usage`: 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
- `find\_tool`: 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\),
- `list\_paid\_tools`: 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.
- `about\_7maps`: 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 serve
- `road\_conditions`: 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 p
- `watch`: 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
- `route`: 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
- `tool\_card`: 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
- `preflight`: 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, allow
- `verify\_lock`: 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 too
- `changes\_since`: 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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html