7Maps-bot
You probably saw us in your server logs. 7Maps-bot is the crawler behind 7Maps, a live map of the MCP servers AI agents use: which ones answer, and what their tools can do. Here is exactly what it does, what your server's page shows, and how to stop it.
7Maps never sells placement. Rankings come only from live checks and real use.
Not on the map? Add your server. Adding a server costs nothing and never affects ranking, and 7Maps checks it itself before listing it. Agent results may also say when a server's owner verified it, as a plain dated fact ("owner verified on 2026-11-04"). It is added after the order is made and never changes it. Verifying costs nothing and is never tied to a payment.
What it does on your server
It sends initialize and tools/list, the same requests any MCP client sends when it connects, and once a day one server/discover, which only asks which protocol revisions the server supports. |
| It never calls a tool, never signs in, and never sends data of its own. |
| It visits once a day, once an hour for widely used servers, and every 5 minutes only when the server's verified owner asked for it. |
| When agents report that a server failed, it checks that server once more itself, at most once every 10 minutes. Only 7Maps' own checks can show a server as down; a report alone never does. |
| It checks servers listed in public MCP registries, at the address the listing gives. It also looks for MCP servers on public business websites, as described below. |
It identifies itself as 7Maps-bot/0.2 (+https://7it.co.il/7maps/bot/). The daily check of one server may also name that server's page on 7Maps after this page: 7Maps-bot/0.2 (+https://7it.co.il/7maps/bot/; this server: https://7it.co.il/7maps/s/<server>?via=bot). The 7Maps-bot name and this page stay first, so a robots.txt rule or a block on 7Maps-bot works the same, and a host that opted out is never contacted. |
If it visited your website
Many companies run an MCP server for their product without listing it anywhere. This is how we find them.
It looks up the name mcp. on your domain first. If that name does not exist, nothing is sent to it. |
On your site it reads robots.txt first, then asks for at most three addresses: /.well-known/mcp/server-card.json, the agent card /.well-known/agent-card.json (or /.well-known/agent.json when robots.txt rules out the server card), and /mcp (or / on the mcp. name) with the same initialize request any MCP client sends. |
| One request at a time to your site, at least a second apart. A 429 or a 403 ends the visit, and it does not retry. |
| A server it finds is checked like a newly submitted one, under observation for a week, before it can appear on the map. Only servers that answer, or that publish their sign-in details, are considered. |
If your site publishes an A2A agent card, it is checked once a day: the card, the key set its signature names, and one request to the endpoint the card declares that asks for a task that does not exist (JSON-RPC GetTask). It never sends your agent a message or a task. Details in the methodology. |
The same opt out below covers this too. A robots.txt rule for 7Maps-bot on your website is read before anything else.
If you run a Hugging Face Space
7Maps-bot never wakes a sleeping Space. It reads each Space's state from the public Hugging Face API, which does not start a Space, and sends its check only to a Space that is already running, right after reading that Space's state again. It checks a Space no more often than the Space's own sleep time, so its checks alone never keep a Space awake, and it does not check Spaces on paid hardware that would otherwise fall asleep. An asleep Space shows as asleep on the map, never as down.
Your Space's state and a README badge: Hugging Face MCP Spaces, live.
Is this your server?
Every server we visit has a page that shows what agents see before they connect.
Whether it answers, how fast, and what each tool can do. Find yours:
From your page you can verify that the server is yours. It takes one line in a file or a DNS record, at no cost. Verified owners get:
- An owner markand a note in your own words, next to your server.
- Checks every 5 minutesand alerts when it stops answering, on your phone or in Slack.
- A private reporton how agents look for servers like yours, and what they pick.
- A badge and a widgetfor your README and docs, with your uptime.
Every step is optional. If you do nothing, nothing changes and we never contact you. More for server owners.
What we publish
Observations with a date: whether the server answered, how fast, how many tools it listed, and the risk level of each tool (read only, needs approval, or high risk), estimated automatically from the tool's name, description and annotations. We report what a server listed. We do not judge whether a server is good or bad.
How the map is made: methodology.
Opt out
Either add this to your robots.txt:
User-agent: 7Maps-bot Disallow: /
The robots.txt rule works at once. Or enter your server's address below: you will get a short text to place at /.well-known/7maps-optout.txt on that host, so nobody can remove a server they do not control. Either way, 7Maps-bot stops visiting and the host is left out of what we publish.
7Maps is built by 7IT.