ViridisOS MCP server
io.github.jdhart81/viridisosjdhart81streamable-httpv1.0.1Scanned
ViridisOS: theorem-backed conservation certification and the fleet's trust root.
7 tools: 6 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
6 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 ViridisOS MCP server can do
The ViridisOS MCP server is published by the GitHub account jdhart81. It has 7 tools. It can create or change data (6 tools: viridis_certify, viridis_certify_envelope, viridis_verify_mark, viridis_bind_did and 2 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
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 1.0.1.
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.
7 tools
Changes things 6Claude Code: ask
viridis_agent_attestationIssue a mark-stamped agent-attestation envelope under the shared trust root.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 mark-stamped agent-attestation envelope under the shared trust root.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Viridis agent attestation
viridis_bind_didDerive the canonical did:viridis identity for an agent (fleet R1 formula) under the shared root.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 Derive the canonical did:viridis identity for an agent (fleet R1 formula) under the shared root.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Viridis bind did
viridis_certifyCertify a subject (parcel/portfolio) with a module -> a certificate.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 Certify a subject (parcel/portfolio) with a module -> a certificate. Errors if the module's backing theorem is not gate-passed (BLOCKED).
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Viridis certify
viridis_certify_envelopeCertify then return a 'Certified by ViridisOS' mark envelope (profile conservation-claim).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 Certify then return a 'Certified by ViridisOS' mark envelope (profile conservation-claim).
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Viridis certify envelope
viridis_compute_tollCompute the unified Viridis protocol margin (the take) + pass-through card cost for a settlement.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 Compute the unified Viridis protocol margin (the take) + pass-through card cost for a settlement.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Viridis compute toll
viridis_verify_markVerify a 'Certified by ViridisOS' envelope against the shared trust root.1 finding
Why it is in this group
- The name "viridis_verify_mark" says "mark": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "viridis_verify_mark" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "viridis_verify_mark" says "mark": a word for a change.
Description, as the server wrote it Verify a 'Certified by ViridisOS' envelope against the shared trust root.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Viridis verify mark
Only reads 1Show 1 read-only tool
viridis_list_modulesList ViridisOS modules and their LIVE/BLOCKED state (A-1 against the live canon).No findings
Why it is in this group
- The name "viridis_list_modules" says "list": a word for reading.
Description, as the server wrote it List ViridisOS modules and their LIVE/BLOCKED state (A-1 against the live canon).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Viridis list modules
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:30 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
- 6
- 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 6 tools that change things (6 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/viridisos/mcp: tools/list returned 7 tools to an anonymous client, including viridis_certify (write), viridis_certify_envelope (write), viridis_verify_mark (write), viridis_bind_did (write), viridis_agent_attestation (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "viridis_verify_mark" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "viridis_verify_mark" says "mark": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools6 changed.~6 changedView diff
- Changed:viridis_agent_attestationChanges thingsinputSchema
- Changed:viridis_bind_didChanges thingsinputSchema
- Changed:viridis_certifyChanges thingsinputSchema
- Changed:viridis_certify_envelopeChanges thingsinputSchema
- Changed:viridis_compute_tollChanges thingsinputSchema
- Changed:viridis_verify_markChanges thingsinputSchema
Tools7 changed.~7 changedView diff
- Changed:viridis_agent_attestationChanges thingstitleannotations
- Changed:viridis_bind_didChanges thingstitleannotations
- Changed:viridis_certifyChanges thingstitleannotations
- Changed:viridis_certify_envelopeChanges thingstitleannotations
- Changed:viridis_compute_tollChanges thingstitleannotations
- Changed:viridis_list_modulesOnly readstitleannotations
- Changed:viridis_verify_markChanges thingstitleannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http viridisos https://mcp.viridisconservation.com/viridisos/mcpclaude mcp add --transport http viridisos https://mcp.viridisconservation.com/viridisos/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__viridisos__viridis_list_modules"
],
"ask": [
"mcp__viridisos__viridis_certify",
"mcp__viridisos__viridis_certify_envelope",
"mcp__viridisos__viridis_verify_mark",
"mcp__viridisos__viridis_bind_did",
"mcp__viridisos__viridis_agent_attestation",
"mcp__viridisos__viridis_compute_toll"
],
"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 viridisos. 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/viridisos/verify?hash=a2b730c5d7321cc638e0cae20be83de755a7342cebd37eab82d6b49e7c84d42d" | jq -e '.changed == false'Pinned hash a2b730c5d732, from Nov 16, 2026, 02:19 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/viridisos/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.jdhart81/viridisos)Source: MCP Registry · repository. Synced Nov 16, 2026, 02:18 UTC.
ViridisOS MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ViridisOS MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ViridisOS MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ViridisOS 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 ViridisOS MCP server have?
- 7 tools: 6 write, 1 read. viridis_certify, viridis_certify_envelope, viridis_verify_mark, viridis_bind_did, viridis_agent_attestation, viridis_compute_toll and viridis_list_modules.
Does the ViridisOS MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ViridisOS MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ViridisOS 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.