What the 7Maps resolver commits to
An AI agent can ask the 7Maps resolver which MCP servers can do a job. It gets up to ten servers that answered at their last check, each one signed by 7IT and valid for 48 hours. This page is what we promise about those answers.
On this page
No paid placement
| Nothing is for sale | No server is added to an answer, or placed higher in one, for money or for anything else of value. |
| Paying does not help | Owner plans, paid 7Maps tools and verifying a server change nothing about whether or where it is offered. |
| Our own servers | 7IT runs its own MCP servers. They are treated exactly like every other server, with no preference. Any other relationship with a server would be listed on this page. |
Where the answers come from
- From the checks 7Maps runs itself. A server is offered only if it answered at its last check, with or without sign-in.
- Each answer says when the server was last checked. That is a record of what we saw, not a promise about the next call.
- Reports from agents or other sources never set a server's status on their own.
- How candidates are chosen and ordered is ours and is not published. What changes in it, and when, is in the changelog. How the checks themselves work is in the methodology.
Method changes
Every material change to how the resolver chooses candidates gets a dated entry here: what changed and why, never the method itself.
v1.0 · 2026-10-28
First published version. Candidates come from the same checks and the same tool search that answer find_tool.
No user data
- The text of a request is never kept with anything that identifies who asked.
- Signed answers carry only facts about the server. Nothing about the request or the caller is in them, so they can be passed on safely.
- Requests are never sold or shared.
- We keep counts only. To count how many different jobs were asked in a week, a one-way code of each job is kept; it changes every week and cannot be turned back into the text.
Ask for the job only, never user content, file names or credentials. More in the privacy policy.
Fair use
Fair-use limits apply to every client. A client over the limit gets status 429 with a Retry-After header, and should try again later.
A client should never depend on the resolver: when it is slow, limited or unreachable, or an answer does not verify, the client carries on as it would without it.
Report a wrong answer
| An agent | Use report_road on https://7it.co.il/7maps/mcp after the call, in its fixed fields. No charge. |
| A person | Write to the contact address with the server id and the signed answer (the jws field). The signature shows exactly what we said and when. |
We compare every report with our own checks. A signed answer is never changed after it is issued; it expires within 48 hours. When the cause is a wrong rule, the rule is fixed and the change is logged above.
Server owners and opt-out
- Opt out. Add
User-agent: 7Maps-botandDisallow: /to the host's robots.txt, or use the form on the 7Maps-bot page. The host is no longer checked, so it stops being offered after its next daily check. Removal is never charged. - Add your words. Owners can verify their server to add a short note. Verifying changes nothing about whether or where a server is offered.
- Something wrong about your server. Write to the contact address, as in reporting a wrong answer.
What it never does
- It never connects an agent to a server. An answer is advice; the agent's own client and its user decide.
- It never hosts, relays or stands in for a server. Every address in an answer is the server's own.
- It never signs a status it did not see, or a check time later than the check.
- It never returns an unsigned candidate.
Keys
Answers are signed with Ed25519. The public key is published at /.well-known/capability-resolver.
| 2026-10-28 | Signing key in use. Key id LTqdVkY_ye_PXMIW0DRwfj8h-LB3QEc3XmCvF--V5Ss, the same key that signs the daily history of 7Maps. |
A new key is published next to the old one before it is used. The old key stays published until every answer signed with it has expired, at least 48 hours. A key that is ever exposed is removed at once. Every change is listed here with its date.
7Maps by 7IT. Also: Methodology · Verify · 7Maps-bot · Terms.