io.github.jdhart81/agent-identity-registry
REMOTE · MCP.VIRIDISCONSERVATION.COM · SCANNED SEP 21
Verifiable agent DIDs + capability discovery — the passport & directory of the A2A economy.
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 Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 300 tokens (~50/item across 6 items; 6 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_agent" 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 7 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-identity-registry MCP server?
io.github.jdhart81/agent-identity-registry is a hosted endpoint at https://mcp.viridisconservation.com/identity/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-identity-registry 'https://mcp.viridisconservation.com/identity/mcp'
{
"mcpServers": {
"jdhart81-agent-identity-registry": {
"url": "https://mcp.viridisconservation.com/identity/mcp"
}
}
} {
"servers": {
"jdhart81-agent-identity-registry": {
"type": "http",
"url": "https://mcp.viridisconservation.com/identity/mcp"
}
}
} [mcp_servers.jdhart81-agent-identity-registry] url = "https://mcp.viridisconservation.com/identity/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jdhart81-agent-identity-registry": {
"type": "remote",
"url": "https://mcp.viridisconservation.com/identity/mcp",
"enabled": true
}
}
} openclaw mcp add jdhart81-agent-identity-registry --url 'https://mcp.viridisconservation.com/identity/mcp' --transport streamable-http
mcp_servers:
jdhart81-agent-identity-registry:
url: "https://mcp.viridisconservation.com/identity/mcp" {
"McpServers": {
"jdhart81-agent-identity-registry": {
"Transport": "http",
"Url": "https://mcp.viridisconservation.com/identity/mcp"
}
}
} assistant mcp add jdhart81-agent-identity-registry -t streamable-http -u 'https://mcp.viridisconservation.com/identity/mcp'
{
"mcpServers": {
"jdhart81-agent-identity-registry": {
"type": "http",
"url": "https://mcp.viridisconservation.com/identity/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
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 28 Jul 26 0
- Authorization: unverified → fail ▼ security
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 21 Sept 2026 · Probed https://mcp.viridisconservation.com/identity/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/identity/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/identity/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/identity/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 →
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.
discover_agents ~43
Find ACTIVE agents matching ALL requested capabilities (AND semantics), deterministically ordered by match count then reputation.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_registrations ~29
List registrations, optionally filtered by status (ACTIVE|REVOKED).
| Name | Type | Req | Description |
|---|---|---|---|
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
register_agent ~99
Register (or idempotently update) an agent identity. Returns a deterministic content-addressed DID. capabilities is a non-empty list of lowercase capability tags other agents can discover you by.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| capabilities | array | yes | – |
| endpoint | string | – | – |
| name | string | – | – |
| pricing | – | – | – |
| pubkey | string | – | – |
| reputation_hint | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve_agent ~37
Resolve an identity by agent_id or DID to its full public registration.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| did | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
revoke_agent ~46
Revoke an identity: it disappears from discovery (terminal) but its record is retained for auditability.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| did | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.jdhart81/agent-identity-registry MCP server?
io.github.jdhart81/agent-identity-registry is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-identity-registry. Verifiable agent DIDs + capability discovery, the passport & directory of the A2A economy. This page covers its hosted endpoint (https://mcp.viridisconservation.com/identity/mcp).
Is the io.github.jdhart81/agent-identity-registry MCP server safe to use?
io.github.jdhart81/agent-identity-registry scores 81 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-identity-registry MCP server expose?
io.github.jdhart81/agent-identity-registry exposes 6 tools: register_agent, resolve_agent, discover_agents, revoke_agent, list_registrations, describe_agent. Their descriptions and schemas cost roughly 267 tokens of context every time the server is loaded.
Does the io.github.jdhart81/agent-identity-registry MCP server require authentication?
Yes. io.github.jdhart81/agent-identity-registry 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-identity-registry MCP server still maintained?
io.github.jdhart81/agent-identity-registry is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.