Skip to content
MCP server

7Maps

Daily-checked map of public MCP servers, with signed uptime history

Status and history

Answered our latest tool-list check 15 hours ago with 16 tools. It will be marked verified after 3 successful checks in 7 days.

Pricing
Freemium
Platforms
API, Web, CLI
Runs
Remotely
Version
1.0.3
Listing updated
2 days ago

About 7Maps

7Maps is a freemium MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.

7Maps is a lookup service for agents: instead of connecting to many servers and loading each tool list, an agent asks one question and gets back the server and tool, its risk level and what changed. The site says it checks every remote server in the official MCP registry daily, the most used ones hourly and owner-verified ones every five minutes, and it counts more than 45,000 servers.

Every check is signed. Each UTC day is hashed into one root, chained to the previous day and signed with Ed25519, and a browser can recompute and verify any day. The daily record starts on 2 October 2026. Risk levels for tools are automated estimates from names, descriptions and annotations and can be wrong. The site says it never sells placement and, per its description, never pays or calls a tool; payment-aware routing only reports what servers declare they charge.

The endpoint uses streamable HTTP with no sign-in, and a Claude Code plugin and Gemini CLI extension are also offered. An optional personal key shows your own usage totals.

Install

Run in a terminal

claude mcp add --transport http 7maps 'https://7it.co.il/7maps/mcp?via=registry'

Add to Settings → Connectors → Add custom connector

https://7it.co.il/7maps/mcp?via=registry
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "7maps": {
      "url": "https://7it.co.il/7maps/mcp?via=registry"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "7maps": {
      "type": "http",
      "url": "https://7it.co.il/7maps/mcp?via=registry"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "7maps": {
      "serverUrl": "https://7it.co.il/7maps/mcp?via=registry"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "7maps": {
      "type": "http",
      "url": "https://7it.co.il/7maps/mcp?via=registry"
    }
  }
}

Tools this server provides (16)

Read directly from the server.

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 agents become the server's rating and, once 7Maps confirms them with its own check, live incident alerts
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 paths are tried. The server is observed every 6 hours for 7 days; if it answers reliably, keeps its
claim_mcp_server
Use this when the person you work for owns an MCP server on the 7Maps map and wants it owner verified: a verified page and README badge, a note for agents, checks every 5 minutes and alerts (alert_url). The first call returns the proof options (a line in /.well-known/7maps-verify.txt, a DNS TXT record, or a GitHub file for io.github names) and claim_check; call again once the proof is in place. Th
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: requests in its category (7 or 30 days), how often it was shown and picked, and, with owner_key, the words agents used, servers picked instead, reported failures, uptime and its token cost against similar servers. Counts only, no agent identities. Read-only; never cha
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 answering that were skipped, risk changes caught by watch or verify_lock, calls that would have fail
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), whether its server is answering now, its handshake time, the tokens its tool list costs to load, and
resolve
Use this when you need an MCP server for a job and want a signed, expiring answer you can verify: returns up to 10 servers that answered at their last check, each with a stable ID, its address, its status, when it was checked and an Ed25519 signature (JWS) valid for 48 hours. The keys are at https://7it.co.il/.well-known/capability-resolver. It never connects you to a server; your client decides.
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 server from the map (changes daily), and, if you name a server, a quote of what 7Maps would save you on i
road_conditions
Use this before connecting to or calling any MCP server you have not used today, or installing a local one: is it up, does it need sign-in, how fast it answers, how many tools are read-only, need approval or are high risk (estimated from public tool descriptions), when its tools last changed and the chance the next call works (daily checks, 30 days of history). For an npm or PyPI server: version,
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 to approve again before calling it. Which to use: watch for one server since a date; verify_lock aga
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 when both can do the task). Returns the best server and tool, alternatives and servers to avoid. Pl
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 the server's own tool list. Optionally only the named tools. For a server that asks for sign-in bef
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, allowed values, unknown keys). Returns go, no_go or fix with what to change (sign_in_first, with how to c
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 tool changes after approval, which MCP clients do not re-ask about. Which to use: verify_lock against y
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". Which to use: changes_since for up to 50 servers at once; watch for one server; verify_lock again

What it does

Daily server checks
Every remote registry server is tested daily, popular ones hourly.
Signed history
Daily Ed25519-signed roots let anyone verify past checks.
Tool search
Describe a job and get matching tools with server status.
Route and status
Tools to see whether a server answers and which to use.
Payment filter
Shows declared per-call prices for servers that take agent payments.
Risk estimates
Labels tools as read-only, data-changing or high risk, as estimates.

Good for

  • Check whether an MCP server is up before connecting
  • Find the right tool for a task across thousands of servers
  • Compare declared per-call prices of paid servers
  • Verify a server's uptime record before relying on it
  • Learn when a server your agent uses goes down

Pricing

Freemium

Some tools free; route is 20 a day on the free tier, paid tools per call via x402 or with a 7IT key

Prices change. Check 7it.co.il before you buy.

7Maps FAQ

Do I need to sign in?

No. The endpoint is streamable HTTP with no sign-in; a personal key is optional and only adds your own usage dashboard.

How often are servers checked?

Every server daily, the most used hourly, and owner-verified servers every five minutes.

Can a server buy ranking?

The site says 7Maps never sells placement and ranks only from live checks and real use.

Does it handle payments?

No. It only shows what servers declare they charge, and the agent pays the server directly.

How are risk levels set?

They are automated estimates from tool names, descriptions and annotations, and can be wrong.

Is 7Maps free?

7Maps has a free plan, with paid plans for more usage or features.

How do I add 7Maps to Claude Code?

Run this command in your terminal: claude mcp add --transport http 7maps 'https://7it.co.il/7maps/mcp?via=registry'

What are the best alternatives to 7Maps?

The closest alternatives to 7Maps are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to 7Maps

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools