# io.github.jdhart81/agent-notary (remote · mcp.viridisconservation.com)

Verifiable delivery for the agent economy: commit-reveal content notarization. Sellers commit to a d

- Trust score: 71/100 (medium)
- Change this week: +16
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.viridisconservation.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/jdhart81-agent-notary/notary-mcp.md), [page](https://verifymcp.io/servers/jdhart81-agent-notary/notary-mcp)

## Channel facts

- Endpoint: `https://mcp.viridisconservation.com/notary/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-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 347 tokens (~57/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 jdhart81-agent-notary https://mcp.viridisconservation.com/notary/mcp
```

### Codex

```toml
[mcp_servers.jdhart81-agent-notary]
url = "https://mcp.viridisconservation.com/notary/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jdhart81-agent-notary": {
      "type": "remote",
      "url": "https://mcp.viridisconservation.com/notary/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jdhart81-agent-notary --url https://mcp.viridisconservation.com/notary/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jdhart81-agent-notary:
    url: "https://mcp.viridisconservation.com/notary/mcp"
```

### Other

```json
{
  "mcpServers": {
    "jdhart81-agent-notary": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/notary/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-08-03 (score 71, +1)

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

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

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

### 2026-07-31 (score 69, +6)

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

### 2026-07-30 (score 63, 0)

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

### 2026-07-29 (score 63, +1)

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

### 2026-07-28 (score 62, +7)

- [security regression] Authorization: unverified → fail

### 2026-07-27 (score 55, +1)

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

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (6)

### `commit` (~96 tokens)

Commit to a deliverable BEFORE handover. commit_hash =
    sha256(salt || sha256(content)) as 64 hex chars; deadline is ISO-8601;
    context links the escrow/job. Idempotent per (committer, nonce).

Input parameters:

- `commit_hash` (string, required)
- `committer` (string, required)
- `context` (string)
- `deadline` (string, required)
- `nonce` (string, required)

Output parameters:

- `result` (string)

### `reveal` (~74 tokens)

Reveal the committed content's digest + salt after handover. Verifies
    against the commitment (one bit of drift fails); returns a delivery_proof
    string for escrow release. Late reveals expire the commitment.

Input parameters:

- `commitment_id` (string, required)
- `content_digest` (string, required)
- `salt` (string, required)

Output parameters:

- `result` (string)

### `verify` (~41 tokens)

Independently verify a revealed commitment; optionally check it against
    the digest of content you received.

Input parameters:

- `commitment_id` (string, required)
- `content_digest`

Output parameters:

- `result` (string)

### `commitment_status` (~32 tokens)

Current record for a commitment (pre-reveal, salt/digest stay hidden).

Input parameters:

- `commitment_id` (string, required)

Output parameters:

- `result` (string)

### `list_commitments` (~35 tokens)

List commitments, optionally filtered by state
    (PENDING|REVEALED|EXPIRED).

Input parameters:

- `state`

Output parameters:

- `result` (string)

### `describe_agent` (~14 tokens)

Return capabilities and input contract.

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-08-03: 71
- 2026-08-02: 70
- 2026-08-01: 70
- 2026-07-31: 69
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 55
- 2026-07-26: 54

## Links

- Remote endpoint: https://mcp.viridisconservation.com/notary/mcp
- Repository: https://github.com/jdhart81/viridis-agent-fleet
- Changelog RSS feed: https://verifymcp.io/servers/jdhart81-agent-notary/notary-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/jdhart81-agent-notary/notary-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/jdhart81-agent-notary/notary-mcp