# 7Maps (remote · 7it.co.il)

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

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `7it.co.il`: 74/100 (this document), [markdown](https://verifymcp.io/servers/xlsv777-7maps/7maps-mcp-2.md), [page](https://verifymcp.io/servers/xlsv777-7maps/7maps-mcp-2)

## Channel facts

- Endpoint: `https://7it.co.il/7maps/mcp?via=registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4067 tokens (~271/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
  - Structured output schemas are declared (13% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the 7Maps MCP server?

7Maps is a hosted endpoint at https://7it.co.il/7maps/mcp?via=registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "xlsv777-7maps": {
      "url": "https://7it.co.il/7maps/mcp?via=registry"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.xlsv777-7maps]
url = "https://7it.co.il/7maps/mcp?via=registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xlsv777-7maps": {
      "type": "remote",
      "url": "https://7it.co.il/7maps/mcp?via=registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xlsv777-7maps --url 'https://7it.co.il/7maps/mcp?via=registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xlsv777-7maps:
    url: "https://7it.co.il/7maps/mcp?via=registry"
```

### Netclaw

```json
{
  "McpServers": {
    "xlsv777-7maps": {
      "Transport": "http",
      "Url": "https://7it.co.il/7maps/mcp?via=registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xlsv777-7maps -t streamable-http -u 'https://7it.co.il/7maps/mcp?via=registry'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-07 (score 74, +1)

- [security] Tool “claim_mcp_server” rewrote its description, which is the text the model reads
- [cosmetic] “claim_mcp_server” added an optional parameter “owner_secret”
- [cosmetic] “claim_mcp_server” added an optional parameter “recover”
- [cosmetic] “claim_mcp_server” added an optional parameter “recover_check”
- [cosmetic] “my_server_report” reworded the description of “owner_key”

### 2026-10-04 (score 73, +1)

- [security] Tool “my_7maps_usage” rewrote its description, which is the text the model reads

### 2026-10-03 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “road_conditions” rewrote its description, which is the text the model reads
- [security] Tool “submit_mcp_server” rewrote its description, which is the text the model reads
- [security] Tool “claim_mcp_server” rewrote its description, which is the text the model reads
- [security] Tool “report_road” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2809 → 3819
- [functional improvement] Tool coverage: 8% → 13%
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “find_tool”
- [functional] New tool “my_server_report”
- [functional] New tool “my_7maps_usage”
- [cosmetic] “claim_mcp_server” added an optional parameter “alert_url”
- [cosmetic] “road_conditions” reworded the description of “last_trip”
- [cosmetic] “route” reworded the description of “last_trip”
- [cosmetic] “tool_card” reworded the description of “last_trip”
- [cosmetic] “verify_lock” reworded the description of “last_trip”
- [cosmetic] “watch” reworded the description of “last_trip”
- [cosmetic] “changes_since” reworded the description of “last_trip”
- [cosmetic] “preflight” reworded the description of “last_trip”

### 2026-10-02 (score 72)

First indexed and scored.

## MCP tools (15)

### `report_road` (~298 tokens)

Report how a call to an MCP server went (7Maps)

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, live incident alerts that every agent sees. You can also pass the same fields as last_trip on any paid 7Maps call. No charge.

Input parameters:

- `charged_usd` (number): What the server charged, if anything
- `fail` (string): If it failed: unreachable, auth, args, server_error, timeout, rate_limited or wrong_result
- `matched_description` (boolean): Whether the result matched what the tool description promised
- `ms` (number): How long the call took, in milliseconds
- `ok` (boolean, required): Whether the call did what you needed
- `result_tokens` (number): About how many tokens the result was
- `server` (string, required): The MCP server you called (URL or registry name)
- `surprise` (string): Anything the tool did that you did not ask for
- `tool` (string): The tool you called
- `tools_hash` (string): The tool_list_hash of the tool list you received, if you computed it as 7Maps does

### `submit_mcp_server` (~240 tokens)

Put a new MCP server on the 7Maps map

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 tools stable and describes every tool, it joins the 7Maps map that agents use to choose servers. Placement cannot be bought. Returns the status page and an optional owner-verification token. No charge.

Input parameters:

- `about` (string): One sentence: what the business does and for whom
- `category` (string): What the business does; agents also see the category its tools show
- `charges` (boolean): Whether the server charges agents (x402 or a subscription)
- `country` (string): Where the business serves customers
- `language` (string): Main language of the tools and their data
- `url` (string, required): The MCP server address, or the business domain (example.com)

### `claim_mcp_server` (~488 tokens)

Verify ownership of an MCP server on 7Maps

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 agents (rate limits, sign-up, what the tools are for), or get a live status badge for their README. Verified owners' servers are checked every 5 minutes (uptime on the page and badge), and with alert_url the owner gets a message when the server stops answering and when it is back. First call returns the proof options (a line in /.well-known/7maps-verify.txt on the server's host, a DNS TXT record, or for io.github registry names a file in the GitHub repo); after one is in place, call again to confirm. The first verification returns an owner secret, shown once: keep it, because later changes to an already verified server (note, alerts) need it as owner_secret. If it is lost, call with recover true, put the one-time code on the host, then call with recover_check. Verifying does not change how the server is measured or ranked. No charge.

Input parameters:

- `alert_url` (string): Optional: where to send down and up alerts. An ntfy topic for phone push without email (https://ntfy.sh/<hard-to-guess topic, at least 10 characters>, a self-hosted https://ntfy.<domain>/<topic>, or…
- `note` (string): Optional plain-text note from the owner, no links, up to 280 characters
- `owner_secret` (string): The owner secret returned once at the first verification. Needed to change an already verified server.
- `recover` (boolean): Lost the owner secret: true returns a one-time code to put on the host, and a check value
- `recover_check` (string): The check value from the recover step, once its code is on the host
- `server` (string, required): The MCP server address as it appears on its 7Maps page

### `my_server_report` (~225 tokens)

What agents looked for around your MCP server (7Maps)

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 for servers in its category in the last 7 or 30 days, how often this server was shown and picked, and, for a verified owner with owner_key, the words agents used, the servers picked instead, failure reasons agents reported, uptime, tool changes, and its token cost and handshake time against similar servers. Counts only, no agent identities. Without owner_key it returns the public numbers and how to verify ownership with claim_mcp_server. Read-only; never changes ranking or routing. No charge.

Input parameters:

- `days`: Window in days: 7 (default) or 30
- `owner_key` (string): The owner key returned to the verified owner by claim_mcp_server (the newest one; each verification issues a new key)
- `server` (string, required): The MCP server address as it appears on its 7Maps page, or its official registry name

### `my_7maps_usage` (~191 tokens)

My 7Maps usage (personal key)

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 failed) and the average response time. It reads the optional personal key sent with this connection (the X-7Maps-Key header); without one it says so in one line, since every 7Maps answer already states its own saving. Only that person's own counts. No charge.

Input parameters:

- `window` (string): Which window to lead with: day (today), week (last 7 days) or month (last 30 days); all three are returned

### `find_tool` (~326 tokens)

Find an MCP tool for a job (7Maps)

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 a page to check it. Filter to read-only tools, servers answering now, a latency or token ceiling. Copies of the same tool on several servers are collapsed. No charge. To have 7Maps pick one server and tool for you with alternatives, use route.

Input parameters:

- `answering_now` (boolean): Only servers that answered with tools on the last check (default true)
- `job` (string, required): What the tool should do, in plain words, for example "send a transactional email" or "query a postgres database"
- `limit` (integer): How many results (default 10)
- `max_handshake_ms` (integer)
- `max_tool_list_tokens` (integer)
- `may` (string): What the tool may do: read = read-only only; change = read or change data; any = include high-risk tools (default any)
- `payment` (string): Payment terms: any (default); free_only = only servers that declare no payment; paid_ok = servers that charge are fine, servers whose payment terms are unknown are left out. Paid servers show their d…

Output parameters:

- `matched` (number)
- `results` (array)
- `tools_indexed` (number)

### `list_paid_tools` (~72 tokens)

Prices of the paid 7IT 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.

Output parameters:

- `network` (string)
- `open` (boolean)
- `plans` (array)
- `tools` (array)

### `about_7maps` (~147 tokens)

What 7Maps is (no charge)

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 it (tokens and time) before you pay. No charge.

Input parameters:

- `server` (string): A server you are considering: get a quote of the tokens and time 7Maps would save on it, before paying

### `road_conditions` (~276 tokens)

Condition of an MCP server before connecting (7Maps)

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 fast it answers, how many of its tools are read-only, need approval or are high risk (delete, pay, run code; automated estimates from the public tool descriptions and annotations), when its tools last changed, and the chance the next call works, from a daily check of every remote server in the official MCP registry and 30 days of history. For a local server (npm or PyPI package): version, maintainers, publisher, install scripts and supply-chain changes. Paid per check (see list_paid_tools). Reads the map only; never calls the server.

Input parameters:

- `last_trip` (object): Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge.
- `license_key` (string): A 7IT monthly plan license key, if you have one; otherwise pay per call with x402
- `server` (string, required): The server URL (https://mcp.example.com/mcp), its official registry name, or npm:<package> / pypi:<package> for a server that runs locally

### `watch` (~209 tokens)

Has an approved MCP server changed? (7Maps)

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. Paid per check (see list_paid_tools). Reads the map only.

Input parameters:

- `approved_at` (string, required): When the person approved this server (YYYY-MM-DD)
- `last_trip` (object): Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge.
- `license_key` (string): A 7IT monthly plan license key, if you have one; otherwise pay per call with x402
- `server` (string, required): The server URL, its official registry name, or npm:<package> / pypi:<package>

### `route` (~299 tokens)

Safest MCP server for a task (7Maps)

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. Paid per task (see list_paid_tools). Reads the map only.

Input parameters:

- `last_trip` (object): Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge.
- `license_key` (string): A 7IT monthly plan license key, if you have one; otherwise pay per call with x402
- `need` (string): How much the task must be allowed to do: read only, change something, or a high-risk action such as payments or deletion. Guessed from the task when omitted
- `payment` (string): Payment terms: any (default); free_only = only servers that declare no payment; paid_ok = servers that charge are fine, servers whose payment terms are unknown are left out. Paid servers show their d…
- `task` (string, required): What you need to do, for example "send a transactional email" or "search company records"

### `tool_card` (~205 tokens)

Compact tool cards for an MCP server (7Maps)

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. Paid per server (see list_paid_tools). Reads the map only.

Input parameters:

- `last_trip` (object): Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge.
- `license_key` (string): A 7IT monthly plan license key, if you have one; otherwise pay per call with x402
- `server` (string, required): The server URL or its official registry name
- `tools` (array): Only these tools; all when omitted

### `preflight` (~228 tokens)

Will this MCP call succeed? (7Maps)

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, so a failed round trip and retry are avoided. Paid per check (see list_paid_tools). Never calls the server.

Input parameters:

- `arguments` (object): The arguments you plan to send
- `last_trip` (object): Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge.
- `license_key` (string): A 7IT monthly plan license key, if you have one; otherwise pay per call with x402
- `server` (string, required): The server URL or its official registry name
- `tool` (string, required): The tool you plan to call

### `verify_lock` (~213 tokens)

Verify a pinned tool list (7Maps)

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. Paid per server (see list_paid_tools). Reads the map only.

Input parameters:

- `last_trip` (object): Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge.
- `license_key` (string): A 7IT monthly plan license key, if you have one; otherwise pay per call with x402
- `lock` (object, required): Tool name to hash, saved at approval
- `server` (string, required): The server URL or its official registry name

### `changes_since` (~201 tokens)

What changed on my MCP servers (7Maps)

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". Paid per call (see list_paid_tools). Reads the map only.

Input parameters:

- `last_trip` (object): Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge.
- `license_key` (string): A 7IT monthly plan license key, if you have one; otherwise pay per call with x402
- `servers` (array, required): Server URLs or official registry names
- `since` (string, required): Date of your last check (YYYY-MM-DD); up to 30 days back

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xlsv777-7maps/7maps-mcp-2#diagnostics

## Score history

- 2026-10-07: 74
- 2026-10-04: 73
- 2026-10-03: 72
- 2026-10-02: 72

## Common questions

### What is the 7Maps MCP server?

7Maps is an MCP server listed in the public MCP registry as io.github.XLSV777/7maps. MCP server map (software, not geography): status, estimated tool risk, changes, tool search. This page covers its hosted endpoint (https://7it.co.il/7maps/mcp?via=registry).

### Is the 7Maps MCP server safe to use?

7Maps scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the 7Maps MCP server expose?

7Maps exposes 15 tools: report_road, submit_mcp_server, claim_mcp_server, my_server_report, my_7maps_usage, and 10 more. Their descriptions and schemas cost roughly 3,618 tokens of context every time the server is loaded.

### Does the 7Maps MCP server require authentication?

No. We connected to 7Maps without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 7Maps MCP server still maintained?

7Maps is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://7it.co.il/7maps/mcp?via=registry
- Website: https://7it.co.il/7maps/
- Changelog RSS feed: https://verifymcp.io/servers/xlsv777-7maps/7maps-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/xlsv777-7maps/7maps-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/xlsv777-7maps/7maps-mcp-2