# attest — verification for AI agent artifacts (remote · attest.rta.lat)

Verify an AI agent artifact: schema, emptiness, provenance and mandate authority, Ed25519-signed.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `attest.rta.lat`: 65/100 (this document), [markdown](https://verifymcp.io/servers/mrpkk-attest/attest.md), [page](https://verifymcp.io/servers/mrpkk-attest/attest)

## Channel facts

- Endpoint: `https://attest.rta.lat/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-10-18.

- **Endpoint Security**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 444 tokens (~222/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**: 7/100
  - Stability observed for 2 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 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the attest — verification for AI agent artifacts MCP server?

attest — verification for AI agent artifacts is a hosted endpoint at https://attest.rta.lat/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 mrpkk-attest 'https://attest.rta.lat/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mrpkk-attest": {
      "url": "https://attest.rta.lat/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrpkk-attest": {
      "type": "http",
      "url": "https://attest.rta.lat/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mrpkk-attest]
url = "https://attest.rta.lat/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrpkk-attest": {
      "type": "remote",
      "url": "https://attest.rta.lat/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrpkk-attest --url 'https://attest.rta.lat/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mrpkk-attest:
    url: "https://attest.rta.lat/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mrpkk-attest": {
      "Transport": "http",
      "Url": "https://attest.rta.lat/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrpkk-attest -t streamable-http -u 'https://attest.rta.lat/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mrpkk-attest": {
      "type": "http",
      "url": "https://attest.rta.lat/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-10-18 (score 65, +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-10-17 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 64, +46)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-15 (score 18)

First indexed and scored.

## MCP tools (2)

### `verify_artifact` (~163 tokens)

Verify an AI agent artifact

Verify an artifact produced by an AI agent before accepting or paying for it. Four independent layers: schema conformance, whether there is anything inside (uniform lists, stubs, truncations), provenance bound to the artifact hash, and whether a signed mandate permitted the action. Returns a verdict (accept/review/reject), a 0-100 trust score, concrete findings and an Ed25519 signature. Rule-based, no LLM: the same artifact always yields the same result. Use before accepting work from another agent and before payment.

Input parameters:

- `artifact` (required): The agent artifact: object, array or string.
- `schema` (object): Optional JSON Schema the artifact must satisfy.
- `source` (string): Where the artifact came from, recorded in the attestation.

### `bridge_check` (~281 tokens)

Bridge: task to work to money

Settle a job between two agents through an escrow bridge. The client posts a task with a budget held in escrow, the worker delivers an artifact, the bridge verifies it and issues a signed RECEIPT. The budget is released only after verification passes. The RECEIPT is verifiable by a third party without access to the bridge, which is what makes it portable between worker, client and insurer. Actions: job (create), deliver (submit and verify), release (accept), refund (reject), verify (check someone else's receipt), trust (reputation). Use when an agent takes on paid work, or when you need to prove to a third party that the work was done.

Input parameters:

- `action` (string, required): What to do.
- `agent` (string): Agent identifier.
- `amount_minor` (integer): Budget in minor units; 1 USDC = 1000000.
- `artifact`: The agent artifact (for deliver).
- `client` (string): Who the client is (for job).
- `db` (string): Path to the bridge database.
- `job_id` (string): Job ID (any action except job).
- `receipt` (object): A third party receipt (for verify).
- `spec` (object): Expected result specification (for job).
- `title` (string): What needs to be done (for job).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mrpkk-attest/attest#diagnostics

## Score history

- 2026-10-18: 65
- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 18

## Common questions

### What is the attest — verification for AI agent artifacts MCP server?

attest — verification for AI agent artifacts is an MCP server listed in the public MCP registry as io.github.mrpkk/attest. Verify an AI agent artifact: schema, emptiness, provenance and mandate authority, Ed25519-signed. This page covers its hosted endpoint (https://attest.rta.lat/mcp).

### Is the attest — verification for AI agent artifacts MCP server safe to use?

attest — verification for AI agent artifacts scores 65 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 attest — verification for AI agent artifacts MCP server expose?

attest — verification for AI agent artifacts exposes 2 tools: verify_artifact, bridge_check. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.

### Does the attest — verification for AI agent artifacts MCP server require authentication?

No. We connected to attest — verification for AI agent artifacts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the attest — verification for AI agent artifacts MCP server still maintained?

attest — verification for AI agent artifacts is still listed as active in the MCP registry. We last reached this channel on 18 October 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://attest.rta.lat/mcp
- Repository: https://github.com/mrpkk/attest
- Website: https://attest.rta.lat/
- Changelog RSS feed: https://verifymcp.io/servers/mrpkk-attest/attest.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrpkk-attest/attest.json
- HTML version of this page: https://verifymcp.io/servers/mrpkk-attest/attest