A
licenseA
qualityB
maintenanceMCP server that preflights endpoints before agent payments, returning a trust verdict with proceed/caution/avoid recommendation.
1
MIT
Probe V0
Server Details
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- lexbritten/probe-mcp
- GitHub Stars
- 0
Available Tools
2 toolsprobe.historyInspect Historical HTTP EvidenceARead-onlyIdempotentInspect
Retrieve up to 20 persisted observations for an existing Probe experiment ID without making a new HTTP request. Use after verify_http_claim to inspect repeated results, PASS/FAIL/ERROR counts, agreement, or whether the observed verdict changed between the two latest decisive observations. This is historical evidence lookup, not a current live verification; use verify_http_claim when freshness or present endpoint behavior matters.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of newest stored observations to return, from 1 through 20. | |
| probe_id | Yes | The 64-character lowercase hexadecimal Probe experiment ID returned by verify_http_claim. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| summary | Yes | |
| probe_id | Yes | |
| protocol | Yes | |
| observations | Yes |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses a key behavioral trait: it retrieves persisted observations 'without making a new HTTP request.' It also explains the kind of evidence an agent can derive, such as PASS/FAIL/ERROR counts, agreement, and verdict changes between decisive observations, which adds valuable behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences with no filler: the first sentence states the core function, the second lists concrete use cases, and the third explicitly draws the boundary against the sibling tool. It is front-loaded and every sentence earns its place.
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?
Given the simple parameter set, rich annotations, and the presence of an output schema, the description covers everything needed for selection and invocation. It explains the historical nature, when to use it, which sibling to prefer for live checks, and what evidence types can be inspected—leaving no material gaps.
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 the input schema already fully documents both parameters, including defaults, bounds, format, and role. The description adds little parameter-specific meaning beyond reinforcing that probe_id is 'returned by verify_http_claim' and that up to 20 observations can be returned, both of which are already in the schema.
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: 'Retrieve up to 20 persisted observations for an existing Probe experiment ID'. It clearly distinguishes itself from the sibling by emphasizing this is historical evidence lookup, not a live verification, which makes the tool's purpose unmistakable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells the agent when to use this tool: 'Use after verify_http_claim to inspect repeated results...' and when not to: 'use verify_http_claim when freshness or present endpoint behavior matters.' This provides clear decision criteria versus the only sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
verify_http_claimVerify Live HTTP ClaimARead-onlyIdempotentInspect
Use this to verify a current public HTTPS claim by direct observation rather than web search, documentation, browser inference, or shell/curl. Use for explicit assertions that a GET/HEAD currently returns an expected HTTP status, exact header value, JSON value at a JSON Pointer, or body substring. It evaluates assertions, persists bounded evidence, reuses sufficiently fresh matching evidence, and summarizes recent observations. follow_redirects defaults to false; when true, Probe manually follows at most 3 validated HTTPS redirects. Every fetch uses redirect: manual. V0 supports only public HTTPS URLs without credentials, query strings, fragments, IP literals, or non-443 ports. Redirect validation is hostname/policy based; the Worker cannot guarantee protection against DNS rebinding between validation and platform DNS resolution.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public HTTPS URL to observe. V0 forbids credentials, query strings, fragments, IP literals, private or local destinations, and non-443 ports. | |
| method | No | HTTP method to observe. Use HEAD only when response headers and status are sufficient. | GET |
| assertions | Yes | One to eight explicit assertions evaluated against the same HTTP response. | |
| follow_redirects | No | Whether to follow up to three validated HTTPS redirects. Defaults to false. | |
| freshness_seconds | No | Maximum acceptable age of reusable matching evidence, in seconds. Public Probe V0 requires exactly 300. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | |
| summary | Yes | |
| protocol | Yes | |
| evidence_source | Yes | |
| evidence_age_seconds | Yes |
TDQS
A4.5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already signal read-only, open-world, and idempotent behavior, so the description adds substantial context beyond them: it evaluates assertions, persists bounded evidence, reuses sufficiently fresh matching evidence, summarizes recent observations, defaults follow_redirects to false, manually follows at most three validated HTTPS redirects, uses redirect: manual on every fetch, and warns about DNS rebinding limitations. This is exemplary behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense but every sentence contributes new information: purpose, assertion types, caching/evidence behavior, redirect mechanics, URL restrictions, and a security caveat. It is front-loaded with the primary use case and maintains a logical flow from high-level intent to low-level operational details without redundancy.
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?
For a tool with five parameters, a non-trivial assertion schema, and an output schema, the description covers all relevant operational context: why to use it, what assertions it supports, how redirects and evidence reuse behave, what URL forms are allowed, and a security limitation. Nothing essential to correct invocation is omitted.
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 each parameter is already documented in the schema. The description adds useful operational color, especially for follow_redirects ('Probe manually follows at most 3 validated HTTPS redirects') and for url constraints ('without credentials, query strings, fragments, IP literals, or non-443 ports'), but it does not need to and does not deeply elaborate on the assertion structure, since the schema already defines that.
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 begins with a specific verb and resource: 'verify a current public HTTPS claim by direct observation.' It clearly enumerates the assertion types (HTTP status, exact header value, JSON value at a JSON Pointer, body substring) and explicitly contrasts itself with web search, documentation, browser inference, and shell/curl, making the tool's unique role unmistakable.
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 description gives explicit when-to-use guidance: 'Use for explicit assertions that a GET/HEAD currently returns...' and lists alternatives to avoid ('rather than web search, documentation, browser inference, or shell/curl'). It also conveys constraints on supported URLs and redirects. However, it does not directly address the sibling tool probe.history, leaving the boundary with historical evidence lookup implicit rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Changed
probe.history3 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"Maximum number of newest stored observations to return, from 1 through 20." - added
Input schema / properties / probe_id / descriptionAdded value: +"The 64-character lowercase hexadecimal Probe experiment ID returned by verify_http_claim." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "observations": { + "items": { + "additionalProperties": false, + "properties": { + "assertion_results": { + "items": { + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "actual": { + "type": "number" + }, + "expected": { + "type": "number" + }, + "kind": { + "const": "status", + "type": "string" + }, + "passed": { + "type": "boolean" + } + }, + "required": [ + "kind", + "expected", + "actual", + "passed" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "actual_fingerprint": { + "additionalProperties": false, + "properties": { + "sha256": { + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "type", + "sha256" + ], + "type": "object" + }, + "expected": { + "type": "string" + }, + "key": { + "type": "string" + }, + "kind": { + "const": "header_equals", + "type": "string" + }, + "passed": { + "type": "boolean" + } + }, + "required": [ + "kind", + "key", + "expected", + "actual_fingerprint", + "passed" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "error_code": { + "type": "string" + }, + "expected": { + "type": "string" + }, + "key": { + "type": "string" + }, + "kind": { + "const": "header_equals", + "type": "string" + }, + "passed": { + "const": false, + "type": "boolean" + } + }, + "required": [ + "kind", + "key", + "expected", + "passed", + "error_code" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "actual_fingerprint": { + "additionalProperties": false, + "properties": { + "sha256": { + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "type", + "sha256" + ], + "type": "object" + }, + "expected": {}, + "key": { + "type": "string" + }, + "kind": { + "const": "json_equals", + "type": "string" + }, + "passed": { + "type": "boolean" + } + }, + "required": [ + "kind", + "key", + "expected", + "actual_fingerprint", + "passed" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "error_code": { + "type": "string" + }, + "expected": {}, + "key": { + "type": "string" + }, + "kind": { + "const": "json_equals", + "type": "string" + }, + "passed": { + "const": false, + "type": "boolean" + } + }, + "required": [ + "kind", + "key", + "expected", + "passed", + "error_code" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "contains": { + "type": "boolean" + }, + "expected": { + "type": "string" + }, + "kind": { + "const": "body_contains", + "type": "string" + }, + "passed": { + "type": "boolean" + } + }, + "required": [ + "kind", + "expected", + "contains", + "passed" + ], + "type": "object" + } + ] + }, + "type": "array" + }, + "body_sha256": { + "type": [ + "string", + "null" + ] + }, + "body_truncated": { + "type": "boolean" + }, + "bytes_observed": { + "type": "number" + }, + "error_code": { + "type": "string" + }, + "final_url": { + "type": "string" + }, + "latency_ms": { + "type": [ + "number", + "null" + ] + }, + "observed_at": { + "type": "string" + }, + "probe_id": { + "type": "string" + }, + "protocol": { + "const": "probe.evidence.v0", + "type": "string" + }, + "redirect_chain": { + "items": { + "additionalProperties": false, + "properties": { + "from_url": { + "type": "string" + }, + "hop": { + "type": "number" + }, + "location": { + "type": "string" + }, + "rejection": { + "type": "string" + }, + "resolved_url": { + "type": "string" + }, + "status_code": { + "type": "number" + }, + "validated": { + "type": "boolean" + } + }, + "required": [ + "hop", + "from_url", + "status_code", + "validated" + ], + "type": "object" + }, + "type": "array" + }, + "redirect_count": { + "type": "number" + }, + "redirects_followed": { + "type": "boolean" + }, + "status_code": { + "type": [ + "number", + "null" + ] + }, + "target": { + "additionalProperties": false, + "properties": { + "host": { + "type": "string" + }, + "method": { + "enum": [ + "GET", + "HEAD" + ], + "type": "string" + } + }, + "required": [ + "host", + "method" + ], + "type": "object" + }, + "termination": { + "type": "string" + }, + "verdict": { + "enum": [ + "PASS", + "FAIL", + "ERROR" + ], + "type": "string" + } + }, + "required": [ + "protocol", + "probe_id", + "observed_at", + "verdict", + "target", + "status_code", + "latency_ms", + "body_sha256", + "bytes_observed", + "body_truncated", + "assertion_results", + "redirects_followed", + "redirect_count", + "final_url", + "redirect_chain", + "termination" + ], + "type": "object" + }, + "type": "array" + }, + "probe_id": { + "type": "string" + }, + "protocol": { + "const": "probe.history.v0", + "type": "string" + }, + "summary": { + "additionalProperties": false, + "properties": { + "agreement": { + "type": [ + "number", + "null" + ] + }, + "changed_since_previous": { + "type": "boolean" + }, + "counts": { + "additionalProperties": false, + "properties": { + "ERROR": { + "type": "number" + }, + "FAIL": { + "type": "number" + }, + "PASS": { + "type": "number" + } + }, + "required": [ + "PASS", + "FAIL", + "ERROR" + ], + "type": "object" + }, + "dominant_verdict": { + "anyOf": [ + { + "enum": [ + "PASS", + "FAIL" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "observations": { + "type": "number" + } + }, + "required": [ + "observations", + "counts", + "dominant_verdict", + "agreement", + "changed_since_previous" + ], + "type": "object" + } + }, + "required": [ + "protocol", + "probe_id", + "observations", + "summary" + ], + "type": "object" +}
- Changed
verify_http_claim7 fields changed- added
Input schema / properties / assertions / descriptionAdded value: +"One to eight explicit assertions evaluated against the same HTTP response." - changed
Input schema / properties / assertions / items / oneOfPrevious value: -[ - { - "properties": { - "expected": { - "maximum": 599, - "minimum": 100, - "type": "integer" - }, - "kind": { - "const": "status", - "type": "string" - } - }, - "required": [ - "kind", - "expected" - ], - "type": "object" - }, - { - "properties": { - "expected": { - "maxLength": 1024, - "type": "string" - }, - "key": { - "maxLength": 80, - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "header_equals", - "type": "string" - } - }, - "required": [ - "kind", - "key", - "expected" - ], - "type": "object" - }, - { - "properties": { - "expected": {}, - "key": { - "maxLength": 256, - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "json_equals", - "type": "string" - } - }, - "required": [ - "kind", - "key", - "expected" - ], - "type": "object" - }, - { - "properties": { - "expected": { - "maxLength": 256, - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "body_contains", - "type": "string" - } - }, - "required": [ - "kind", - "expected" - ], - "type": "object" - } -]New value: +[ + { + "properties": { + "expected": { + "description": "Expected HTTP status code from 100 through 599.", + "maximum": 599, + "minimum": 100, + "type": "integer" + }, + "kind": { + "const": "status", + "description": "Assert the HTTP response status code.", + "type": "string" + } + }, + "required": [ + "kind", + "expected" + ], + "type": "object" + }, + { + "properties": { + "expected": { + "description": "Exact expected response header value.", + "maxLength": 1024, + "type": "string" + }, + "key": { + "description": "Response header name to compare case-insensitively.", + "maxLength": 80, + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "header_equals", + "description": "Assert an exact response header value.", + "type": "string" + } + }, + "required": [ + "kind", + "key", + "expected" + ], + "type": "object" + }, + { + "properties": { + "expected": { + "description": "Exact JSON value expected at the JSON Pointer." + }, + "key": { + "description": "JSON Pointer identifying the response value to compare, for example /status.", + "maxLength": 256, + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "json_equals", + "description": "Assert an exact JSON value at a JSON Pointer.", + "type": "string" + } + }, + "required": [ + "kind", + "key", + "expected" + ], + "type": "object" + }, + { + "properties": { + "expected": { + "description": "Literal case-sensitive substring expected in the bounded response body.", + "maxLength": 256, + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "body_contains", + "description": "Assert that the response body contains a literal substring.", + "type": "string" + } + }, + "required": [ + "kind", + "expected" + ], + "type": "object" + } +] - added
Input schema / properties / follow_redirects / descriptionAdded value: +"Whether to follow up to three validated HTTPS redirects. Defaults to false." - added
Input schema / properties / freshness_seconds / descriptionAdded value: +"Maximum acceptable age of reusable matching evidence, in seconds. Public Probe V0 requires exactly 300." - added
Input schema / properties / method / descriptionAdded value: +"HTTP method to observe. Use HEAD only when response headers and status are sufficient." - changed
Input schema / properties / url / descriptionPrevious value: -"Public HTTPS URL. V0 forbids credentials, query strings, redirects, IP literals, and non-443 ports."New value: +"Public HTTPS URL to observe. V0 forbids credentials, query strings, fragments, IP literals, private or local destinations, and non-443 ports." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "evidence_age_seconds": { + "type": "number" + }, + "evidence_source": { + "enum": [ + "cached", + "fresh_execution" + ], + "type": "string" + }, + "protocol": { + "const": "probe.check.v0", + "type": "string" + }, + "result": { + "additionalProperties": false, + "properties": { + "assertion_results": { + "items": { + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "actual": { + "type": "number" + }, + "expected": { + "type": "number" + }, + "kind": { + "const": "status", + "type": "string" + }, + "passed": { + "type": "boolean" + } + }, + "required": [ + "kind", + "expected", + "actual", + "passed" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "actual_fingerprint": { + "additionalProperties": false, + "properties": { + "sha256": { + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "type", + "sha256" + ], + "type": "object" + }, + "expected": { + "type": "string" + }, + "key": { + "type": "string" + }, + "kind": { + "const": "header_equals", + "type": "string" + }, + "passed": { + "type": "boolean" + } + }, + "required": [ + "kind", + "key", + "expected", + "actual_fingerprint", + "passed" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "error_code": { + "type": "string" + }, + "expected": { + "type": "string" + }, + "key": { + "type": "string" + }, + "kind": { + "const": "header_equals", + "type": "string" + }, + "passed": { + "const": false, + "type": "boolean" + } + }, + "required": [ + "kind", + "key", + "expected", + "passed", + "error_code" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "actual_fingerprint": { + "additionalProperties": false, + "properties": { + "sha256": { + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "type", + "sha256" + ], + "type": "object" + }, + "expected": {}, + "key": { + "type": "string" + }, + "kind": { + "const": "json_equals", + "type": "string" + }, + "passed": { + "type": "boolean" + } + }, + "required": [ + "kind", + "key", + "expected", + "actual_fingerprint", + "passed" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "error_code": { + "type": "string" + }, + "expected": {}, + "key": { + "type": "string" + }, + "kind": { + "const": "json_equals", + "type": "string" + }, + "passed": { + "const": false, + "type": "boolean" + } + }, + "required": [ + "kind", + "key", + "expected", + "passed", + "error_code" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "contains": { + "type": "boolean" + }, + "expected": { + "type": "string" + }, + "kind": { + "const": "body_contains", + "type": "string" + }, + "passed": { + "type": "boolean" + } + }, + "required": [ + "kind", + "expected", + "contains", + "passed" + ], + "type": "object" + } + ] + }, + "type": "array" + }, + "body_sha256": { + "type": [ + "string", + "null" + ] + }, + "body_truncated": { + "type": "boolean" + }, + "bytes_observed": { + "type": "number" + }, + "error_code": { + "type": "string" + }, + "final_url": { + "type": "string" + }, + "latency_ms": { + "type": [ + "number", + "null" + ] + }, + "observed_at": { + "type": "string" + }, + "probe_id": { + "type": "string" + }, + "protocol": { + "const": "probe.evidence.v0", + "type": "string" + }, + "redirect_chain": { + "items": { + "additionalProperties": false, + "properties": { + "from_url": { + "type": "string" + }, + "hop": { + "type": "number" + }, + "location": { + "type": "string" + }, + "rejection": { + "type": "string" + }, + "resolved_url": { + "type": "string" + }, + "status_code": { + "type": "number" + }, + "validated": { + "type": "boolean" + } + }, + "required": [ + "hop", + "from_url", + "status_code", + "validated" + ], + "type": "object" + }, + "type": "array" + }, + "redirect_count": { + "type": "number" + }, + "redirects_followed": { + "type": "boolean" + }, + "status_code": { + "type": [ + "number", + "null" + ] + }, + "target": { + "additionalProperties": false, + "properties": { + "host": { + "type": "string" + }, + "method": { + "enum": [ + "GET", + "HEAD" + ], + "type": "string" + } + }, + "required": [ + "host", + "method" + ], + "type": "object" + }, + "termination": { + "type": "string" + }, + "verdict": { + "enum": [ + "PASS", + "FAIL", + "ERROR" + ], + "type": "string" + } + }, + "required": [ + "protocol", + "probe_id", + "observed_at", + "verdict", + "target", + "status_code", + "latency_ms", + "body_sha256", + "bytes_observed", + "body_truncated", + "assertion_results", + "redirects_followed", + "redirect_count", + "final_url", + "redirect_chain", + "termination" + ], + "type": "object" + }, + "summary": { + "additionalProperties": false, + "properties": { + "agreement": { + "type": [ + "number", + "null" + ] + }, + "changed_since_previous": { + "type": "boolean" + }, + "counts": { + "additionalProperties": false, + "properties": { + "ERROR": { + "type": "number" + }, + "FAIL": { + "type": "number" + }, + "PASS": { + "type": "number" + } + }, + "required": [ + "PASS", + "FAIL", + "ERROR" + ], + "type": "object" + }, + "dominant_verdict": { + "anyOf": [ + { + "enum": [ + "PASS", + "FAIL" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "observations": { + "type": "number" + } + }, + "required": [ + "observations", + "counts", + "dominant_verdict", + "agreement", + "changed_since_previous" + ], + "type": "object" + } + }, + "required": [ + "protocol", + "evidence_source", + "evidence_age_seconds", + "result", + "summary" + ], + "type": "object" +}
2 tool updates
- First observed
probe.history - First observed
verify_http_claim
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Public MCP server for summaries, DNS lookup, catalog, replies, and JSON checks.
Trust, freshness, policy, and discovery layer for public MCP servers.
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for verifying high-impact decisions with Trust OS.2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for witnessd, enabling agents to create tamper-evident, signed, and Merkle-anchored certificates of any public URL or API response at a moment in time.48MIT
FactGridofficial
AlicenseNot gradedqualityCmaintenanceMCP server providing dependency upgrade advisories, developer API schemas, and electronic component specifications with evidence-backed, Ed25519-signed responses.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
verify_http_claim performs live current verification while probe.history retrieves persisted past observations. The descriptions explicitly separate the two use cases, so an agent should not confuse them.
Naming Consistency3/5
verify_http_claim follows a verb_object pattern, while probe.history uses a namespace.noun pattern. Both names are readable and lowercase, but the two naming styles are mixed rather than following one predictable convention.
Tool Count3/5
With only two tools the surface feels thin, but the narrow purpose of live HTTP verification plus historical evidence lookup is served without unnecessary additions. The minimal count is appropriate but borderline on the calibration scale.
Completeness4/5
The core workflow is covered: verify a claim with current evidence and later inspect the persisted history. Minor gaps such as listing or clearing experiments are absent but not required for the stated verification loop.