AFMR Discovery
REMOTE · AFMR.AI · 2 COMPONENTS · SCANNED SEP 22
Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 406 tokens (~33/item across 12 items; 4 tools + 8 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the AFMR Discovery MCP server?
AFMR Discovery is a hosted endpoint at https://afmr.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · afmr.ai
claude mcp add --transport http ai-afmr-discovery 'https://afmr.ai/mcp'
{
"mcpServers": {
"ai-afmr-discovery": {
"url": "https://afmr.ai/mcp"
}
}
} {
"servers": {
"ai-afmr-discovery": {
"type": "http",
"url": "https://afmr.ai/mcp"
}
}
} [mcp_servers.ai-afmr-discovery] url = "https://afmr.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-afmr-discovery": {
"type": "remote",
"url": "https://afmr.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-afmr-discovery --url 'https://afmr.ai/mcp' --transport streamable-http
mcp_servers:
ai-afmr-discovery:
url: "https://afmr.ai/mcp" {
"McpServers": {
"ai-afmr-discovery": {
"Transport": "http",
"Url": "https://afmr.ai/mcp"
}
}
} assistant mcp add ai-afmr-discovery -t streamable-http -u 'https://afmr.ai/mcp'
{
"mcpServers": {
"ai-afmr-discovery": {
"type": "http",
"url": "https://afmr.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://afmr.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=afmr.ai | CN=WE1,O=Google Trust Services,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 99248797734976df0efd73039e0530ea |
| SANs: afmr.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of afmr.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| afmr.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://afmr.ai/mcp | Verified | 200 | |
| http (plaintext) | http://afmr.ai/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
discover_afmr Discover AFMR resources ~26
Return canonical AFMR specifications, registries, schemas, endpoints, and scope boundaries.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_lift_evidence_contract Get the Lift Evidence public-card contract ~31
Return the stable configuration-scoped public-card schema and empty public index; no results are asserted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_reputation_attestation_contract Get the reputation-attestation contract ~32
Return the portable attestation, trust-profile, verifier-result, endpoint-registry, and lifecycle contracts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_failure_mode Look up AFMR failure modes ~71
Find exact AFMR 1.0 failure-mode records by permanent ID or bounded text query.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Exact permanent family identifier, for example AFMR-F010. |
| limit | integer | – | – |
| query | string | – | Text matched against ID, name, definition, and class. |
No output schema declared.
No examples provided.
What is the AFMR Discovery MCP server?
AFMR Discovery is an MCP server listed in the public MCP registry as ai.afmr/discovery. Read AFMR failure modes and discover scoped attestation and lift-evidence contracts. This page covers its hosted endpoint (https://afmr.ai/mcp).
Is the AFMR Discovery MCP server safe to use?
AFMR Discovery scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AFMR Discovery MCP server expose?
AFMR Discovery exposes 4 tools: discover_afmr, lookup_failure_mode, get_reputation_attestation_contract, get_lift_evidence_contract. Their descriptions and schemas cost roughly 160 tokens of context every time the server is loaded.
Does the AFMR Discovery MCP server require authentication?
No. We connected to AFMR Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AFMR Discovery MCP server still maintained?
AFMR Discovery is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.