Skip to main content
Glama

Verify ownership of an MCP server on 7Maps

claim_mcp_server
Idempotent

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "claim_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional plain-text note from the owner, no links, up to 280 characters
serverYesThe MCP server address as it appears on its 7Maps page
recoverNoLost the owner secret: true returns a one-time code to put on the host, and a check value
alert_urlNoOptional: 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 ntfy:https://<host>/<topic>), a Slack incoming webhook (https://hooks.slack.com/services/...), a Discord webhook (https://discord.com/api/webhooks/...), or any https webhook that receives JSON. Stored encrypted, saved only once ownership is proven; a test message is sent on save. An empty string turns alerts off.
claim_checkNoThe claim_check from the first call
owner_secretNoThe owner secret returned once at the first verification. Needed to change an already verified server.
recover_checkNoThe check value from the recover step, once its code is on the host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / claim_check
      Added value: +{
      +  "description": "The claim_check from the first call",
      +  "maxLength": 700,
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / owner_secret
      Added value: +{
      +  "description": "The owner secret returned once at the first verification. Needed to change an already verified server.",
      +  "maxLength": 80,
      +  "type": "string"
      +}
    • addedInput schema / properties / recover
      Added value: +{
      +  "description": "Lost the owner secret: true returns a one-time code to put on the host, and a check value",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / recover_check
      Added value: +{
      +  "description": "The check value from the recover step, once its code is on the host",
      +  "maxLength": 700,
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / alert_url
      Added value: +{
      +  "description": "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 ntfy:https://<host>/<topic>), a Slack incoming webhook (https://hooks.slack.com/services/...), a Discord webhook (https://discord.com/api/webhooks/...), or any https webhook that receives JSON. Stored encrypted, saved only once ownership is proven; a test message is sent on save. An empty string turns alerts off.",
      +  "maxLength": 600,
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover mutability and idempotency, and the description goes well beyond them: it discloses that checks run every 5 minutes with alerts, that it never changes ranking, that there is no charge, that the owner secret is shown only once and can be recovered, and that alert_url is stored encrypted with a test message sent on save. These are behaviorally load-bearing details an agent could not infer from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical trigger is front-loaded in the first clause and every sentence carries content, but the dense parenthetical stacking (alert_url variants, recover flow) makes it harder to scan than it needs to be. It is compact for the amount of information conveyed, with little true waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With seven parameters, no output schema, and a multi-step claim/recover flow, the description supplies exactly what is missing structurally: what the first call returns, what the second call consumes, when the secret appears, and how to recover it. An agent has enough to drive the whole flow correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every parameter is already documented in the input schema, which sets the baseline at 3. The description adds sequencing semantics (claim_check comes from the first call, recover_check follows recover), but it does not add format or constraint detail beyond what the schema fields already state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Verify ownership of an MCP server on 7Maps') and enumerates the concrete deliverables: verified page, README badge, agent note, 5-minute checks. That level of specificity separates it from the sibling admin tools like submit_mcp_server or verify_lock without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger condition is explicit ('Use this when the person you work for owns an MCP server... and wants it owner verified'), and the two-step calling pattern is spelled out ('The first call returns the proof options... call again once the proof is in place'). What's missing is an explicit when-not or a named alternative for the adjacent recover path, which is described inline rather than routed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources