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

Viridis Verified: wrap any MCP server with tamper-evident delivery receipts + metered fees.

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

## Components

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

## Channel facts

- Endpoint: `https://mcp.viridisconservation.com/verified/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**: 43/100
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 389 tokens (~55/item across 7 items; 7 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-verified-relay https://mcp.viridisconservation.com/verified/mcp
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "jdhart81-agent-verified-relay": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/verified/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 68, +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 67, +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 66, +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 60, +1)

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

### 2026-07-28 (score 59, +8)

- [security regression] Authorization: unverified → fail

### 2026-07-27 (score 51, 0)

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

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

First indexed and scored.

## MCP tools (7)

### `register_service` (~102 tokens)

Register a third-party MCP server (https, public FQDN only) under
    Viridis Verified. Returns a content-addressed service_id; idempotent on
    (url, provider). fee_minor is the per-verified-call fee in cents.

Input parameters:

- `description` (string)
- `fee_minor` (integer)
- `payment_ref`
- `provider` (string, required)
- `request_id`
- `url` (string, required)

Output parameters:

- `result` (string)

### `call_verified` (~132 tokens)

Relay a tools/call to a registered MCP service and notarize the
    exchange: request hash + response hash + outcome land in a tamper-evident
    receipt chain. Idempotent on call_id (a replay returns the original
    receipt and cached result — the downstream is never double-called).
    Failures are receipted evidence, not silence.

Input parameters:

- `arguments`
- `call_id` (string, required)
- `payment_ref`
- `request_id`
- `service_id` (string, required)
- `timeout_s` (integer)
- `tool` (string, required)

Output parameters:

- `result` (string)

### `get_receipt` (~25 tokens)

Fetch a single delivery receipt by id.

Input parameters:

- `receipt_id` (string, required)

Output parameters:

- `result` (string)

### `verify_receipts` (~42 tokens)

Recompute a service's full receipt hash chain and fee ledger.
    Any party can audit Viridis Verified from receipts alone.

Input parameters:

- `service_id` (string, required)

Output parameters:

- `result` (string)

### `list_services` (~17 tokens)

List registered services with call/fee counters.

Output parameters:

- `result` (string)

### `service_stats` (~29 tokens)

Call counts, error counts, and accrued fees for one service.

Input parameters:

- `service_id` (string, required)

Output parameters:

- `result` (string)

### `describe_agent` (~13 tokens)

Fleet-standard self-description.

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-verified-relay/verified-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 59
- 2026-07-27: 51
- 2026-07-26: 51

## Links

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