# Agent Output Verifier by SarnAI (remote · verify.sarnai.dev)

Independent schema and rule check of AI agent output before you pay. Signed attestation and receipt.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `verify.sarnai.dev`: 80/100 (this document), [markdown](https://verifymcp.io/servers/dev-sarnai-agent-output-verifier/verify.md), [page](https://verifymcp.io/servers/dev-sarnai-agent-output-verifier/verify)

## Channel facts

- Endpoint: `https://verify.sarnai.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.9`

## 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-11-05.

- **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**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1128 tokens (~564/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Agent Output Verifier by SarnAI MCP server?

Agent Output Verifier by SarnAI is a hosted endpoint at https://verify.sarnai.dev/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.

### Claude

```bash
claude mcp add --transport http dev-sarnai-agent-output-verifier 'https://verify.sarnai.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-sarnai-agent-output-verifier": {
      "url": "https://verify.sarnai.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-sarnai-agent-output-verifier": {
      "type": "http",
      "url": "https://verify.sarnai.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-sarnai-agent-output-verifier]
url = "https://verify.sarnai.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-sarnai-agent-output-verifier": {
      "type": "remote",
      "url": "https://verify.sarnai.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-sarnai-agent-output-verifier --url 'https://verify.sarnai.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-sarnai-agent-output-verifier:
    url: "https://verify.sarnai.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-sarnai-agent-output-verifier": {
      "Transport": "http",
      "Url": "https://verify.sarnai.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-sarnai-agent-output-verifier -t streamable-http -u 'https://verify.sarnai.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-sarnai-agent-output-verifier": {
      "type": "http",
      "url": "https://verify.sarnai.dev/mcp"
    }
  }
}
```

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-11-04 (score 80, +1)

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

### 2026-11-02 (score 79, +1)

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

### 2026-10-31 (score 78, +1)

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

### 2026-10-30 (score 77, 0)

- [functional] Server version: 0.5.8 → 0.5.9
- [cosmetic] “get_verification_record” reworded the description of “agent_id”

### 2026-10-29 (score 77, +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.

### 2026-10-27 (score 76, +1)

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

### 2026-10-24 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_verification_record” rewrote its description, which is the text the model reads
- [security] Tool “verify_schema” rewrote its description, which is the text the model reads
- [functional] Server version: 0.5.7 → 0.5.8

### 2026-10-22 (score 74, +1)

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

## MCP tools (2)

### `verify_schema` (~792 tokens)

Independent check of AI agent output before you pay: verify and validate an AI agent's JSON against your JSON Schema and business rules, for example validate an invoice, check its total, or confirm a deliverable meets the agreed schema before you accept it. Checks structure, formats, ranges, and cross-field rules such as 'line totals must equal the total.' Returns pass/fail, % of checks passed, fix hints, and an Ed25519-signed attestation and receipt you can show as evidence of why you paid or refused. 1,000 free checks a day per caller, then $0.02 per check (x402, USDC on Base or Solana).

Input parameters:

- `agent_id`: Optional label identifying the AI agent that produced submitted_output (for example, the seller), used for /reputation and the trust score: records and scores belong to the producer, not to whoever c…
- `bounds`: Optional per-field min/max, keyed by dotted path with '[]' array wildcard (e.g. 'items[].price'). Numbers or ISO-8601 dates. Violations are reported as informational flags unless enforce_rules is tru…
- `detail` (string): 'full' (default) returns everything; 'compact' returns only the summary, next actions, receipt and signature. Use compact inside verify-repair loops to save tokens. 'compact' fields: summary, next_ac…
- `enforce_rules` (boolean): Opt-in. When true, every configured bound and consistency rule must hold, or the result is 'fail' (like strict_content_check), with an 'enforce_rules: ...' entry in errors. That includes a rule or bo…
- `expected_schema` (object, required): Required. The JSON Schema (draft-04 to 2020-12) that submitted_output must satisfy: your own requirements, as a JSON object.
- `rules`: Optional cross-field rules: sum_equals, gte, lte, exists_in, unique (duplicate detection). Violations are reported as informational flags unless enforce_rules is true.
- `strict_content_check` (boolean): Opt-in. When true, any string in submitted_output containing control characters (e.g. null bytes) or embedded HTML/script markup makes the result 'fail'. When false (default) this is not checked at a…
- `submitted_output` (required): Required. The output being checked: any JSON value (object, array, string, number, boolean or null), exactly as the AI agent produced it.
- `task_id` (string, required): Your own identifier for this verification. 1-200 printable characters, no control characters and no lone Unicode surrogate; a request outside that range is rejected (422), not truncated.

### `get_verification_record` (~199 tokens)

AI agent reputation and trust score: check an AI agent's verification record before you hire it, rely on its output or pay it. Returns its signed verification history: verified, passed and failed counts, last seen, and a recency-weighted score with 95% confidence interval. Check a counterparty before you pay, or see the record buyers will see. AI Agent Scores: $0.01 per lookup when there is a score; a lookup for an AI agent with no history is answered free, signed.

Input parameters:

- `agent_id` (string, required): The agent_id whose verification history to score (as passed to /verify/schema): the AI agent that produced the output checked by those calls (for example, the seller). agent_ids starting with 'test-'…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-sarnai-agent-output-verifier/verify#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 68
- 2026-10-12: 68
- 2026-10-11: 68
- 2026-10-09: 67

## Common questions

### What is the Agent Output Verifier by SarnAI MCP server?

Agent Output Verifier by SarnAI is an MCP server listed in the public MCP registry as dev.sarnai/agent-output-verifier. Independent schema and rule check of AI agent output before you pay. Signed attestation and receipt. This page covers its hosted endpoint (https://verify.sarnai.dev/mcp).

### Is the Agent Output Verifier by SarnAI MCP server safe to use?

Agent Output Verifier by SarnAI scores 80 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 Agent Output Verifier by SarnAI MCP server expose?

Agent Output Verifier by SarnAI exposes 2 tools: verify_schema, get_verification_record. Their descriptions and schemas cost roughly 991 tokens of context every time the server is loaded.

### Does the Agent Output Verifier by SarnAI MCP server require authentication?

No. We connected to Agent Output Verifier by SarnAI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agent Output Verifier by SarnAI MCP server still maintained?

Agent Output Verifier by SarnAI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://verify.sarnai.dev/mcp
- Repository: https://github.com/sarnai-dev/agent-output-verifier
- Changelog RSS feed: https://verifymcp.io/servers/dev-sarnai-agent-output-verifier/verify.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-sarnai-agent-output-verifier/verify.json
- HTML version of this page: https://verifymcp.io/servers/dev-sarnai-agent-output-verifier/verify