INDIVIDUAL MCP TOOL

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.

7it.co.ilnone authenticationAvailability not checked

LIVE ENDPOINT

https://7it.co.il/7maps/mcp?via=registry

No auth detected

Connect to this endpoint to inspect the live schema for tool_card and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

7it.co.il

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.7maps]
url = "https://7it.co.il/7maps/mcp?via=registry"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: 7maps
Remote MCP URL: https://7it.co.il/7maps/mcp?via=registry

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "7maps",
  "transport": "streamable-http",
  "url": "https://7it.co.il/7maps/mcp?via=registry"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

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.
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.
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 agents (rate limits, sign-up, what the tools are for), or get a live status badge for their README.
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 (about 250,000 tools, probed daily) and returns the best matches with 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.
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.
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.
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 fast it answers, how many of its tools are read-only, need approval or are high risk (delete, pay, run code), 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.
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.