io.github.jdhart81/agent-covenant
REMOTE · MCP.VIRIDISCONSERVATION.COM · SCANNED SEP 20
Deny-by-default authority leases for agents wielding real power.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 370 tokens (~52/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "revoke_covenant" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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
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
claude mcp add --transport http jdhart81-agent-covenant 'https://mcp.viridisconservation.com/covenant/mcp'
{
"mcpServers": {
"jdhart81-agent-covenant": {
"url": "https://mcp.viridisconservation.com/covenant/mcp"
}
}
} {
"servers": {
"jdhart81-agent-covenant": {
"type": "http",
"url": "https://mcp.viridisconservation.com/covenant/mcp"
}
}
} [mcp_servers.jdhart81-agent-covenant] url = "https://mcp.viridisconservation.com/covenant/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jdhart81-agent-covenant": {
"type": "remote",
"url": "https://mcp.viridisconservation.com/covenant/mcp",
"enabled": true
}
}
} openclaw mcp add jdhart81-agent-covenant --url 'https://mcp.viridisconservation.com/covenant/mcp' --transport streamable-http
mcp_servers:
jdhart81-agent-covenant:
url: "https://mcp.viridisconservation.com/covenant/mcp" {
"McpServers": {
"jdhart81-agent-covenant": {
"Transport": "http",
"Url": "https://mcp.viridisconservation.com/covenant/mcp"
}
}
} assistant mcp add jdhart81-agent-covenant -t streamable-http -u 'https://mcp.viridisconservation.com/covenant/mcp'
{
"mcpServers": {
"jdhart81-agent-covenant": {
"type": "http",
"url": "https://mcp.viridisconservation.com/covenant/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 0
- Schema quality: unverified → fair ▲ functional
- 11 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 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
- 30 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
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 20 Sept 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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| act_id | string | yes | – |
| amount_minor | integer | – | – |
| covenant_id | string | yes | – |
| scope | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
covenant_status ~28
Current state, consumed/remaining budget, and check count.
| Name | Type | Req | Description |
|---|---|---|---|
| covenant_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_agent ~13
Fleet-standard self-description.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| budget_minor | integer | yes | – |
| expires_at | string | yes | – |
| principal | string | yes | – |
| scopes | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_covenants ~46
List covenants, optionally filtered by state (ACTIVE|REVOKED|EXPIRED) and/or the bound agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
revoke_covenant ~39
Revoke a covenant immediately and terminally. All subsequent checks deny.
| Name | Type | Req | Description |
|---|---|---|---|
| covenant_id | string | yes | – |
| reason | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_audit ~33
Verify the tamper-evident audit chain of allowed/denied acts.
| Name | Type | Req | Description |
|---|---|---|---|
| covenant_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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 83 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 341 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.