# AFMR Discovery (remote · afmr.ai)

Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `afmr.ai`: 69/100 (this document), [markdown](https://verifymcp.io/servers/ai-afmr-discovery/api-rpc.md), [page](https://verifymcp.io/servers/ai-afmr-discovery/api-rpc)

## Channel facts

- Endpoint: `https://afmr.ai/api/rpc`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 406 tokens (~33/item across 12 items; 4 tools + 8 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-afmr-discovery https://afmr.ai/api/rpc
```

### Codex

```toml
[mcp_servers.ai-afmr-discovery]
url = "https://afmr.ai/api/rpc"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-afmr-discovery": {
      "type": "remote",
      "url": "https://afmr.ai/api/rpc",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-afmr-discovery --url https://afmr.ai/api/rpc --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-afmr-discovery:
    url: "https://afmr.ai/api/rpc"
```

### Other

```json
{
  "mcpServers": {
    "ai-afmr-discovery": {
      "type": "http",
      "url": "https://afmr.ai/api/rpc"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64)

First indexed and scored.

## MCP tools (4)

### `discover_afmr` (~26 tokens)

Discover AFMR resources

Return canonical AFMR specifications, registries, schemas, endpoints, and scope boundaries.

### `lookup_failure_mode` (~71 tokens)

Look up AFMR failure modes

Find exact AFMR 1.0 failure-mode records by permanent ID or bounded text query.

Input parameters:

- `id` (string): Exact permanent family identifier, for example AFMR-F010.
- `limit` (integer)
- `query` (string): Text matched against ID, name, definition, and class.

### `get_reputation_attestation_contract` (~32 tokens)

Get the reputation-attestation contract

Return the portable attestation, trust-profile, verifier-result, endpoint-registry, and lifecycle contracts.

### `get_lift_evidence_contract` (~31 tokens)

Get the Lift Evidence public-card contract

Return the stable configuration-scoped public-card schema and empty public index; no results are asserted.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-afmr-discovery/api-rpc#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 67
- 2026-07-30: 64

## Links

- Remote endpoint: https://afmr.ai/api/rpc
- Website: https://afmr.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-afmr-discovery/api-rpc/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-afmr-discovery/api-rpc/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-afmr-discovery/api-rpc