Trust Oracle MCP server
io.github.jdhart81/agent-trust-oraclejdhart81streamable-httpv0.1.2Scanned
Decay-weighted agent reputation and tamper-evident trust attestations.
6 tools: 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Trust Oracle MCP server can do
The Trust Oracle MCP server is published by the GitHub account jdhart81. It has 6 tools. It can create or change data (4 tools: record_outcome, attest, verify_attestation and history), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.1.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 4Claude Code: ask
attestIssue a tamper-evident (hash-chained) trust attestation for an agent.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Issue a tamper-evident (hash-chained) trust attestation for an agent.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Attest
historyFull outcome history + attestation count + current score for an agent.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Full outcome history + attestation count + current score for an agent.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: History
record_outcomeRecord an interaction outcome for an agent.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Record outcome
verify_attestationVerify a previously issued attestation by recomputing its hash.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Verify a previously issued attestation by recomputing its hash.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Verify attestation
Only reads 2Show 2 read-only tools
describe_agentDescribe this agent: name, version, purpose, every action it supports and the inputs each one takes.No findings
Why it is in this group
- The name "describe_agent" says "describe": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Describe this service
score_agentGet an agent's decay-weighted trust score in [0,1] and tier.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Score agent
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.viridisconservation.com/trust/mcp: tools/list returned 6 tools to an anonymous client, including record_outcome (write), attest (write), verify_attestation (write), history (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:attestChanges thingsinputSchema
- Changed:historyChanges thingsinputSchema
- Changed:record_outcomeChanges thingsinputSchema
- Changed:score_agentOnly readsinputSchema
- Changed:verify_attestationChanges thingsinputSchema
Tools6 changed.~6 changedView diff
- Changed:attestChanges thingstitleannotations
- Changed:describe_agentOnly readstitledescriptionannotations
- Changed:historyChanges thingstitleannotations
- Changed:record_outcomeChanges thingstitleannotations
- Changed:score_agentOnly readstitleannotations
- Changed:verify_attestationChanges thingstitleannotations
Install
Pinned to version 0.1.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http agent-trust-oracle https://mcp.viridisconservation.com/trust/mcpclaude mcp add --transport http agent-trust-oracle https://mcp.viridisconservation.com/trust/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__agent-trust-oracle__score_agent",
"mcp__agent-trust-oracle__describe_agent"
],
"ask": [
"mcp__agent-trust-oracle__record_outcome",
"mcp__agent-trust-oracle__attest",
"mcp__agent-trust-oracle__verify_attestation",
"mcp__agent-trust-oracle__history"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-trust-oracle. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.jdhart81/agent-trust-oracle/verify?hash=27cfa1ff711de22f48f1c54358a483d8e1d2ad5bf2f7f26dfd06d4f23b12bff8" | jq -e '.changed == false'Pinned hash 27cfa1ff711d, from Nov 16, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.jdhart81/agent-trust-oracle/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.jdhart81/agent-trust-oracle)Source: MCP Registry · repository. Synced Nov 16, 2026, 02:17 UTC.
Trust Oracle MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Trust Oracle MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Trust Oracle MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Trust Oracle MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Trust Oracle MCP server have?
- 6 tools: 4 write, 2 read. record_outcome, attest, verify_attestation, history, score_agent and describe_agent.
Does the Trust Oracle MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Trust Oracle MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Trust Oracle MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.