Skip to main content
Glama

Server Details

7Maps, the live directory of MCP servers, run by 7IT Solutions: which work today, what changed.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 16 tools

Disambiguation4/5

The descriptions do unusually heavy lifting with explicit 'Which to use' cross-references, which prevents most misselection between route/find_tool/resolve and watch/changes_since/verify_lock. Still, there are genuine three-way overlaps (three discovery tools, three change-tracking tools) whose only distinction is output format, so some confusion remains.

Naming Consistency3/5

Several tools follow verb_noun (find_tool, list_paid_tools, claim_mcp_server, submit_mcp_server, report_road), but others are bare verbs (resolve, route, watch, preflight) or noun phrases (road_conditions, tool_card, changes_since), or possessives (my_7maps_usage, my_server_report). The set is readable and thematically coherent but uses mixed conventions.

Tool Count4/5

Sixteen tools is at the upper edge but each covers a distinct phase of the lifecycle: discovery, safety checks, token-saving, reporting, ownership and billing. The count feels slightly heavy given the overlapping discovery and change-tracking groups, but no tool is clearly redundant.

Completeness4/5

The surface spans discovery, pre-call validation, change/rug-pull monitoring, token reduction, post-call reporting, server submission, ownership verification and usage/cost introspection—an unusually full lifecycle. Minor gaps remain: there is no way to unlist or update an already-submitted server, and no tool to manage or revoke an existing paid plan or owner claim.

Available Tools

16 tools
about_7mapsWhat 7Maps is (no charge)A
Read-onlyIdempotent
Inspect

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.

Inputs: server.

changes_sinceWhat changed on my MCP servers (7Maps)A
Read-onlyIdempotent
Inspect

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

Inputs: since (required), servers (required), last_trip, license_key.

claim_mcp_serverVerify ownership of an MCP server on 7MapsA
Idempotent
Inspect

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. The first verification returns an owner secret, shown once: keep it as owner_secret (lost: recover, then recover_check). Never changes ranking. No charge.

Inputs: server (required), note, recover, alert_url, +3 more.

find_toolFind an MCP tool for a job (7Maps)A
Read-onlyIdempotent
Inspect

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. Which to use: find_tool searches tools yourself; route has 7Maps pick and rank servers for a task; resolve returns a signed list a client can verify.

Inputs: job (required), may, limit, payment, +6 more. Returns: matched, results, tools_indexed

list_paid_toolsPrices of the paid 7IT toolsA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters. Returns: open, plans, tools, network

my_7maps_usageMy 7Maps usage (personal key)A
Read-onlyIdempotent
Inspect

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.

Inputs: window, last_trip.

my_server_reportWhat agents looked for around your MCP server (7Maps)A
Read-onlyIdempotent
Inspect

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 changes ranking. No charge.

Inputs: server (required), days, owner_key.

preflightWill this MCP call succeed? (7Maps)A
Read-onlyIdempotent
Inspect

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

Inputs: tool (required), server (required), arguments, last_trip, +1 more.

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

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 that every agent sees. You can also pass the same fields as last_trip on your next call of any 7Maps tool. No charge.

Inputs: ok (required), server (required), ms, fail, +8 more.

resolveResolve a job to MCP servers (signed)A
Read-onlyIdempotent
Inspect

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. Which to use: resolve for a signed, verifiable list; route for a ranked pick; find_tool to search tools. No charge.

Inputs: need (required), max_ms, payment, read_only, +1 more.

road_conditionsCondition of an MCP server before connecting (7Maps)A
Read-onlyIdempotent
Inspect

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, maintainers, install scripts and supply-chain changes. Paid per check (see list_paid_tools). Reads the map only; never calls the server.

Inputs: server (required), last_trip, task_type, agent_model, +1 more.

routeSafest MCP server for a task (7Maps)A
Read-onlyIdempotent
Inspect

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. Placement is never sold: the order comes only from live checks and real use. Which to use: route picks for you; find_tool lets you search tools yourself; resolve returns a signed list a client can verify. Paid per task (see list_paid_tools). Reads the map only.

Inputs: task (required), need, payment, last_trip, +3 more.

submit_mcp_serverPut a new MCP server on the 7Maps mapA
Idempotent
Inspect

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.

Inputs: url (required), about, charges, country, +2 more.

tool_cardCompact tool cards for an MCP server (7Maps)A
Read-onlyIdempotent
Inspect

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 before listing its tools: that it is up and how to connect (no charge). Paid per server (see list_paid_tools). Reads the map only.

Inputs: server (required), tools, last_trip, license_key.

verify_lockVerify a pinned tool list (7Maps)A
Read-onlyIdempotent
Inspect

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 your saved lock; watch for one server since a date; changes_since for many servers. Paid per server (see list_paid_tools). Reads the map only.

Inputs: lock (required), server (required), last_trip, license_key.

watchHas an approved MCP server changed? (7Maps)A
Read-onlyIdempotent
Inspect

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 against a lock you saved; changes_since for up to 50 servers at once. Paid per check (see list_paid_tools). Reads the map only.

Inputs: server (required), approved_at (required), last_trip, license_key.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources