7Maps

Name: 7Maps
Author: XLSV777

MCP serverMCP

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

by XLSV777homepage ↗v1.0.2

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"7maps","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability22/22 checks ok

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	311 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
10 h ago	mcp initialize	ok	200	268 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
17 h ago	mcp initialize	ok	200	278 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
23 h ago	mcp initialize	ok	200	414 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
29 h ago	mcp initialize	ok	200	292 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
35 h ago	mcp initialize	ok	200	268 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	418 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	491 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	322 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools
3 d ago	mcp initialize	ok	200	267 ms	server 7maps 1.2.0 · protocol 2025-06-18 · 15 tools

Tools observed via MCP handshake

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, whethe
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 t
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
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
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 d
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
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
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 i
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
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
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 rank
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
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, whethe
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 r
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

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.XLSV777/7maps

first seen 6 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

6 d ago · declared · summary → "MCP server map (software, not geography): status, estimated tool risk, changes, tool search."
6 d ago · declared · description → "MCP server map (software, not geography): status, estimated tool risk, changes, tool search."
6 d ago · declared · publisherName → "XLSV777"
6 d ago · declared · homepageUrl → "https://7it.co.il/7maps/"
6 d ago · declared · version → "1.0.2"
6 d ago · declared · protocols → ["mcp"]

7Maps

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from