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

io.github.jdhart81/agent-covenant

REMOTE · MCP.VIRIDISCONSERVATION.COM

Deny-by-default authority leases for agents wielding real power.

+1 this week 84 Trust /100

Last scanned (23 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Security

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 406 tokens (~58/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 Management97
  • Stability observed for 29 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 3 Nov 26 0
    • Tool “check_act” changed its title: Check act cosmetic
    • Tool “covenant_status” changed its title: Covenant status cosmetic
    • Tool “describe_agent” changed its title: Describe this service cosmetic
    • Tool “grant_covenant” changed its title: Grant covenant cosmetic
    • Tool “list_covenants” changed its title: List covenants cosmetic
    • Tool “revoke_covenant” changed its title: Revoke covenant cosmetic
    • Tool “verify_audit” changed its title: Verify audit cosmetic

    7 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 31 Oct 26 +2
    • Tool “describe_agent” rewrote its description, which is the text the model reads security
    • Tool “revoke_covenant” is now declared destructive security
    • Schema quality: 52 → 58 ▼ functional
    • Schema quality: fair → good functional
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
  • 28 Sept 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
  • 25 Sept 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 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 12 Aug 26 0
    • Schema quality: unverified → fair ▲ functional
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 4 Nov 2026 · Probed https://mcp.viridisconservation.com/covenant/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 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA384 5abb43a3acf241ca07b1eb9ff25cafac4e4
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

Background: What to check on a remote MCP endpoint →

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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.viridisconservation.com/covenant/mcp Verified 200
http (plaintext) http://mcp.viridisconservation.com/covenant/mcp HTTPS enforced 308 https://mcp.viridisconservation.com/covenant/mcp
MCP tools · 7 exposed · ~377 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_act ~84

Check (and if allowed, record) a proposed act against a covenant. Deny-by-default. Idempotent on act_id — retries never double-consume budget. Every check lands on the audit chain.

NameTypeReqDescription
act_idstringyes–
amount_minorinteger––
covenant_idstringyes–
scopestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

covenant_status ~28

Current state, consumed/remaining budget, and check count.

NameTypeReqDescription
covenant_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

describe_agent ~49

Describe this agent: name, version, purpose, every action it supports and the inputs each one takes. Read-only and free; call it first to learn how to use this server.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

grant_covenant ~98

Grant an agent a covenant: an explicit lease of authority. scopes support wildcards ('payments.*', '*'); budget_minor is the total spend ceiling in minor units; expires_at is ISO-8601. Returns the covenant_id.

NameTypeReqDescription
agent_idstringyes–
budget_minorintegeryes–
expires_atstringyes–
principalstringyes–
scopesarrayyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_covenants ~46

List covenants, optionally filtered by state (ACTIVE|REVOKED|EXPIRED) and/or the bound agent.

NameTypeReqDescription
agent_id–––
state–––
NameTypeReqDescription
resultstringyes–

No examples provided.

revoke_covenant ~39

Revoke a covenant immediately and terminally. All subsequent checks deny.

NameTypeReqDescription
covenant_idstringyes–
reasonstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_audit ~33

Verify the tamper-evident audit chain of allowed/denied acts.

NameTypeReqDescription
covenant_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the io.github.jdhart81/agent-covenant MCP server?

io.github.jdhart81/agent-covenant is a hosted endpoint at https://mcp.viridisconservation.com/covenant/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.

remote · mcp.viridisconservation.com

# add to Claude Code
claude mcp add --transport http jdhart81-agent-covenant 'https://mcp.viridisconservation.com/covenant/mcp'
Common questions

What is the io.github.jdhart81/agent-covenant MCP server?

io.github.jdhart81/agent-covenant is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-covenant. Deny-by-default authority leases for agents wielding real power. This page covers its hosted endpoint (https://mcp.viridisconservation.com/covenant/mcp).

Is the io.github.jdhart81/agent-covenant MCP server safe to use?

io.github.jdhart81/agent-covenant scores 84 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 io.github.jdhart81/agent-covenant MCP server expose?

io.github.jdhart81/agent-covenant exposes 7 tools: grant_covenant, check_act, revoke_covenant, covenant_status, verify_audit, and 2 more. Their descriptions and schemas cost roughly 377 tokens of context every time the server is loaded.

Does the io.github.jdhart81/agent-covenant MCP server require authentication?

Yes. io.github.jdhart81/agent-covenant asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.github.jdhart81/agent-covenant MCP server still maintained?

io.github.jdhart81/agent-covenant is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.