7Maps · For MCP server owners
Agents choose the server. 7Maps shows them yours as it is.
Before an AI agent connects, it can ask 7Maps which server does the job, whether it answers now, and what changed. Here is what every owner gets at no charge, and what the owner plans add.
Why it matters
Agents decide in one call
An agent with many servers to choose from does not try each one. It asks, and goes where the answer is clear: open, answering, and the right tool for the job.
Down or slow loses the call
A server that does not answer, or answers slowly, is passed over for one that does. For a SaaS or API business, each call that goes elsewhere is usage, and revenue, that went elsewhere.
You hear it first
With checks every five minutes and an alert on your phone or in your team's channel, you know a server stopped answering before your users tell you.
At no charge, for every owner
- A page on the map. Every server in the official registry has one: status, uptime over 30 and 90 days, every tool's estimated risk level, and what changed.
- Daily checks. Every server, every day; the most used servers every hour.
- Verify that it is yours. One line in a file on your host, a DNS record, or a file in the GitHub repository. Your page gets an owner mark and a note in your words, and agents see both.
- Checks every five minutes. For verified servers, up to three per owner.
- Down and up alerts. To ntfy on your phone, Slack, Discord or any webhook, after two failed checks in a row. No email needed.
- A live badge. For your README: status, uptime, agents' stars, the owner mark, or "top 10%" when the server earns it.
- A status widget. One line of script or an iframe for your docs or status page.
- Feeds. An Atom feed per server with status changes, tool-list changes, new advisories and verification.
- What agents looked for. Every server page shows how often agents asked for servers in its category this week, and how often it was shown and picked.
Placement on the map cannot be bought, and verifying changes nothing about how a server is measured or ranked. Removal from the map is never charged.
What the owner plans add
What only the map can see: how agents look for servers like yours, and what they pick instead. Counts only; no agent's request text, address or identity is stored. Nothing here changes how a server is measured, ranked or routed.
Owner Insights
For an owner who wants to know how agents look for servers like theirs
- The words agents used when they asked for servers in your category
- How often your server was shown and picked, and at what position
- The servers agents picked instead
- Failure reasons agents reported, and what surprised them
- Uptime and the days your tool list changed
- Token cost and handshake time next to the median of similar servers
- Last 7 or 30 days, on a private page, as JSON, or through the my_server_report tool
Team
For teams and agencies that run several servers
- Everything in Owner Insights, for every server you verify Planned
- More servers on the five-minute checks and alerts Planned
- Checks more often than every five minutes Planned
Feed
For gateways and companies that keep a list of approved servers
- Status and tool-list changes across the whole map, as one data feed Planned
- Built on the same signed daily history the map publishes Planned
Owner Insights is open to every verified owner during the preview: the link comes with the verification result.
Plans open soon.
Start
Your agent can do the same with claim_mcp_server and read the report with my_server_report, both on https://7it.co.il/7maps/mcp at no charge. How the map is made: methodology. Prefer not to be listed: opting out.