io.github.jdhart81/agent-trust-oracle
REMOTE · MCP.VIRIDISCONSERVATION.COM
Decay-weighted reputation + tamper-evident trust attestations for the agent economy.
Available components
Last scanned (5 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 333 tokens (~55/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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
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 Nov 26 0
- Tool “attest” changed its title: Attest cosmetic
- Tool “describe_agent” changed its title: Describe this service cosmetic
- Tool “history” changed its title: History cosmetic
- Tool “record_outcome” changed its title: Record outcome cosmetic
- Tool “score_agent” changed its title: Score agent cosmetic
- Tool “verify_attestation” changed its title: Verify attestation cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 31 Oct 26 +1
- Tool “describe_agent” rewrote its description, which is the text the model reads security
- Schema quality: 49 → 55 ▼ 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
- 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
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 5 Nov 2026 · Probed https://mcp.viridisconservation.com/trust/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/trust/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/trust/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/trust/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 →
attest Attest ~41
Issue a tamper-evident (hash-chained) trust attestation for an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| claim | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_agent Describe this service ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
history History ~29
Full outcome history + attestation count + current score for an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
record_outcome Record outcome ~91
Record an interaction outcome for an agent. kind: success | delivered | dispute_won | failure | undelivered | dispute_lost | timeout | security_incident (security incidents carry a 3x penalty).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| counterparty | string | – | – |
| kind | string | yes | – |
| note | string | – | – |
| weight | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
score_agent Score agent ~55
Get an agent's decay-weighted trust score in [0,1] and tier. Unknown agents get a neutral 0.5 prior — no blind trust, no unfair zero.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_attestation Verify attestation ~39
Verify a previously issued attestation by recomputing its hash.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| attestation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.jdhart81/agent-trust-oracle MCP server?
io.github.jdhart81/agent-trust-oracle is a hosted endpoint at https://mcp.viridisconservation.com/trust/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-trust-oracle 'https://mcp.viridisconservation.com/trust/mcp'
What is the io.github.jdhart81/agent-trust-oracle MCP server?
io.github.jdhart81/agent-trust-oracle is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-trust-oracle. Decay-weighted reputation + tamper-evident trust attestations for the agent economy. This page covers its hosted endpoint (https://mcp.viridisconservation.com/trust/mcp).
Is the io.github.jdhart81/agent-trust-oracle MCP server safe to use?
io.github.jdhart81/agent-trust-oracle scores 85 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-trust-oracle MCP server expose?
io.github.jdhart81/agent-trust-oracle exposes 6 tools: record_outcome, score_agent, attest, verify_attestation, history, describe_agent. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.
Does the io.github.jdhart81/agent-trust-oracle MCP server require authentication?
Yes. io.github.jdhart81/agent-trust-oracle 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-trust-oracle MCP server still maintained?
io.github.jdhart81/agent-trust-oracle is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.