Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.jdhart81/agent-verified-relay

REMOTE · MCP.VIRIDISCONSERVATION.COM · SCANNED AUG 3

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

+17 this week 68 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability43
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 389 tokens (~55/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.viridisconservation.com

# add to Claude Code
claude mcp add --transport http jdhart81-agent-verified-relay https://mcp.viridisconservation.com/verified/mcp
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add jdhart81-agent-verified-relay --url https://mcp.viridisconservation.com/verified/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jdhart81-agent-verified-relay:
    url: "https://mcp.viridisconservation.com/verified/mcp"
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +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.

  • 1 Aug 26 +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.

  • 31 Jul 26 +6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +8
    • Authorization: unverified → fail security
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 51

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.viridisconservation.com/verified/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.viridisconservation.com CN=YE1,O=Let's Encrypt,C=US 10 Jul 2026 8 Oct 2026 ECDSA 256 ECDSA-SHA384 5c5a470e8a8f6a38757f4cfdb556662b95a
SANs: mcp.viridisconservation.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of mcp.viridisconservation.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
viridisconservation.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.viridisconservation.com/verified/mcp Verified 200
http (plaintext) http://mcp.viridisconservation.com/verified/mcp HTTPS enforced 308 https://mcp.viridisconservation.com/verified/mcp
MCP tools — 7 exposed · ~360 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
call_verified ~132

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.

NameTypeReqDescription
arguments
call_idstringyes
payment_ref
request_id
service_idstringyes
timeout_sinteger
toolstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

describe_agent ~13

Fleet-standard self-description.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

get_receipt ~25

Fetch a single delivery receipt by id.

NameTypeReqDescription
receipt_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

list_services ~17

List registered services with call/fee counters.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

register_service ~102

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.

NameTypeReqDescription
descriptionstring
fee_minorinteger
payment_ref
providerstringyes
request_id
urlstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

service_stats ~29

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

NameTypeReqDescription
service_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

verify_receipts ~42

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

NameTypeReqDescription
service_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.