Skip to main content
Glama

MCP Verification Gate: check an MCP server or an A2A agent before you connect or delegate

Check an MCP server for conformance and disclosure

check_conformance
Read-only

Measure a public MCP endpoint against five conditions: it speaks MCP, it publishes an A2A agent card, it declares who pays it, identical input returns identical output, and the verdict itself can be recomputed by anyone. Free, no key. Conformance and disclosure only; this says nothing about whether any figure the checked server returns is correct. By default no tool on the checked server is called, so determinism comes back as not measured rather than guessed. It is measured when the owner has published /.well-known/mcp-conduct.json with allow_tool_call true.

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": {
      "endpoint": "<endpoint>"
    },
    "name": "check_conformance"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpointYeshttps URL of the MCP endpoint to measure
allow_tool_callNoKept for compatibility. Since 2026-10-08 an assertion alone calls no tool: consent is proven only by the owner's /.well-known/mcp-conduct.json. Default false.

Output Schema

NameRequiredDescriptionDefault
gateNoName of this gate.
checksNoOne entry per condition, each with whether it was measured, whether it passed, and the detail.
statusNoverified = every measured condition passed. pending = measured, not all passing. held = could not be reached, nothing established.
endpointNoThe MCP endpoint that was measured.
reachableNoThree-valued on purpose (gate58). true = measured and answered. false = measured and did not answer. null = NOT MEASURED. null is never to be read as a failing endpoint; it means this gate has nothing to say.
checked_atNoWhen the measurement started, ISO 8601 UTC.
probed_viaNoThe network path the probe took (relay or direct).
scope_noteNoWhat this measurement covers and what it does not.
establishesNoWhat this verdict establishes, as sentences.
gate_commitNoGit commit of the deployed gate, or a sentence saying the deployment did not pin one.
gate_versionNoVersion of the gate code that took this measurement.
tools_calledNoWhether a tool on the checked server was executed, in words.
consent_basisNoOn what basis a tool call was or was not made.
measured_fromNoWhere this measurement was taken, inside the hashed bytes: platform (cloudflare, azure, ...) and origin, the public origin that serves this record and its history. Absent on records before 0.4.23.
number_safetyNoWhether every number in this verdict survives a JSON round trip unchanged.
record_sha256NoHash of this verdict with record_sha256 and recompute_note removed. Recompute it yourself; verify_verdict does the same arithmetic.
consent_lookupNoPresent when no proven consent was found: the consent file that was read, the result, and how to consent.
consent_sourceNoWhere the consent came from: operator_list, well_known, requester or none.
recompute_noteNoHow to recompute record_sha256. Not part of the hashed bytes.
canonicalizationNoCondition 07, disclosed and never a verdict: whether the declared tool surface canonicalizes under RFC 8785.
measurement_noteNoPresent only when the gate's own relay failed, so that nothing here is read as a statement about the target.
absence_vs_failureNoCondition 06, disclosed and never a verdict: whether the server's tools can tell a failed lookup from an empty one.
does_not_establishNoWhat this verdict does not establish, as sentences.
coordinate_derivationNoHow the measured tool and instant were derived, or that the legacy rule applied.
consent_assertion_ignoredNoPresent when the request set allow_tool_call true without proven consent: the assertion was recorded and no tool was called.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / measured_from
      Added value: +{
      +  "description": "Where this measurement was taken, inside the hashed bytes: platform (cloudflare, azure, ...) and origin, the public origin that serves this record and its history. Absent on records before 0.4.23.",
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / allow_tool_call / description
      Previous value: -"Consent to executing one tool on the checked server, twice, with empty arguments. Only set this for a server you own. Default false."New value: +"Kept for compatibility. Since 2026-10-08 an assertion alone calls no tool: consent is proven only by the owner's /.well-known/mcp-conduct.json. Default false."
    • addedOutput schema / properties / consent_assertion_ignored
      Added value: +{
      +  "description": "Present when the request set allow_tool_call true without proven consent: the assertion was recorded and no tool was called.",
      +  "type": "object"
      +}
  3. Changed24 schema fields changed
    • addedOutput schema / properties / absence_vs_failure
      Added value: +{
      +  "description": "Condition 06, disclosed and never a verdict: whether the server's tools can tell a failed lookup from an empty one.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / canonicalization
      Added value: +{
      +  "description": "Condition 07, disclosed and never a verdict: whether the declared tool surface canonicalizes under RFC 8785.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / checked_at
      Added value: +{
      +  "description": "When the measurement started, ISO 8601 UTC.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / checks
      Added value: +{
      +  "description": "One entry per condition, each with whether it was measured, whether it passed, and the detail.",
      +  "type": "object"
      +}
    • removedOutput schema / properties / conditions
      Removed value: -{
      -  "type": [
      -    "array",
      -    "object"
      -  ]
      -}
    • addedOutput schema / properties / consent_basis
      Added value: +{
      +  "description": "On what basis a tool call was or was not made.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / consent_lookup
      Added value: +{
      +  "description": "Present when no proven consent was found: the consent file that was read, the result, and how to consent.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / consent_source
      Added value: +{
      +  "description": "Where the consent came from: operator_list, well_known, requester or none.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / coordinate_derivation
      Added value: +{
      +  "description": "How the measured tool and instant were derived, or that the legacy rule applied.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / does_not_establish
      Added value: +{
      +  "description": "What this verdict does not establish, as sentences.",
      +  "type": "array"
      +}
    • addedOutput schema / properties / endpoint / description
      Added value: +"The MCP endpoint that was measured."
    • addedOutput schema / properties / establishes
      Added value: +{
      +  "description": "What this verdict establishes, as sentences.",
      +  "type": "array"
      +}
    • addedOutput schema / properties / gate
      Added value: +{
      +  "description": "Name of this gate.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / gate_commit
      Added value: +{
      +  "description": "Git commit of the deployed gate, or a sentence saying the deployment did not pin one.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / gate_version
      Added value: +{
      +  "description": "Version of the gate code that took this measurement.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / measurement_note
      Added value: +{
      +  "description": "Present only when the gate's own relay failed, so that nothing here is read as a statement about the target.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / number_safety
      Added value: +{
      +  "description": "Whether every number in this verdict survives a JSON round trip unchanged.",
      +  "type": "object"
      +}
    • removedOutput schema / properties / pass
      Removed value: -{
      -  "type": [
      -    "boolean",
      -    "null"
      -  ]
      -}
    • addedOutput schema / properties / probed_via
      Added value: +{
      +  "description": "The network path the probe took (relay or direct).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / reachable / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • addedOutput schema / properties / recompute_note / description
      Added value: +"How to recompute record_sha256. Not part of the hashed bytes."
    • addedOutput schema / properties / scope_note
      Added value: +{
      +  "description": "What this measurement covers and what it does not.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / status
      Added value: +{
      +  "description": "verified = every measured condition passed. pending = measured, not all passing. held = could not be reached, nothing established.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / tools_called
      Added value: +{
      +  "description": "Whether a tool on the checked server was executed, in words.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "conditions": {
      +      "type": [
      +        "array",
      +        "object"
      +      ]
      +    },
      +    "endpoint": {
      +      "type": "string"
      +    },
      +    "pass": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "reachable": {
      +      "description": "Three-valued on purpose (gate58). true = measured and answered. false = measured and did not answer. null = NOT MEASURED. null is never to be read as a failing endpoint; it means this gate has nothing to say."
      +    },
      +    "recompute_note": {
      +      "type": "string"
      +    },
      +    "record_sha256": {
      +      "description": "Hash of this verdict with record_sha256 and recompute_note removed. Recompute it yourself; verify_verdict does the same arithmetic.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses cost (free), auth (no key), and the key side-effect profile: by default no tool on the checked server is invoked, so determinism is returned as 'not measured' rather than guessed. It also explains the consent mechanism that gates the only potentially invasive path, which is exactly the behavioral detail an agent needs. This does not contradict readOnlyHint, since the consent file, not this tool, authorizes any tool call.

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?

Four sentences, front-loaded with the five conditions, then scope limits, then default behavior, then the consent exception — a logical progression with no filler. The five-condition list is dense in a single sentence but still readable, and 'Free, no key' is a terse, useful standalone fact.

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?

An output schema means return values need no explanation here, and the description covers the remaining gaps an agent would have: scope limits, cost, default non-invasive behavior, and the precise condition under which determinism is actually measured. Nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so both parameters are already fully documented in the input schema. The description's statement that determinism is measured via the owner's well-known file restates what the allow_tool_call schema text already says about the parameter being a no-op, adding no new syntax or constraints beyond the schema baseline.

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 opens with a specific verb and resource ('Measure a public MCP endpoint') and enumerates the five exact conditions being tested. The clause 'Conformance and disclosure only; this says nothing about whether any figure the checked server returns is correct' sharply bounds the scope and implicitly separates it from verdict-recomputation siblings like verify_verdict.

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?

It gives clear operating context: free, no key, no tool called by default, and determinism is measured only when the owner publishes /.well-known/mcp-conduct.json with allow_tool_call true. What it lacks is explicit routing language naming when to prefer verify_verdict or is_verified instead, leaving that inference to the agent.

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.