io.github.jdhart81/viridisos
REMOTE · MCP.VIRIDISCONSERVATION.COM
ViridisOS — theorem-backed conservation certification + the unified trust root/mark/toll. Certify pa
Available components
Last scanned (4 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 381 tokens (~54/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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
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 “viridis_agent_attestation” changed its title: Viridis agent attestation cosmetic
- Tool “viridis_bind_did” changed its title: Viridis bind did cosmetic
- Tool “viridis_certify” changed its title: Viridis certify cosmetic
- Tool “viridis_certify_envelope” changed its title: Viridis certify envelope cosmetic
- Tool “viridis_compute_toll” changed its title: Viridis compute toll cosmetic
- Tool “viridis_list_modules” changed its title: Viridis list modules cosmetic
- Tool “viridis_verify_mark” changed its title: Viridis verify mark cosmetic
7 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 31 Oct 26 +7
- Authorization: unverified → partial ▲ security
- 10 Oct 26 +10
- Transport: fail → pass ▲ security
- 7 Oct 26 −10
- Transport: pass → fail ▼ security
- 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
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/viridisos/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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
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/viridisos/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/viridisos/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/viridisos/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 →
viridis_agent_attestation Viridis agent attestation ~33
Issue a mark-stamped agent-attestation envelope under the shared trust root.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viridis_bind_did Viridis bind did ~50
Derive the canonical did:viridis identity for an agent (fleet R1 formula) under the shared root.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| pubkey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viridis_certify Viridis certify ~66
Certify a subject (parcel/portfolio) with a module -> a certificate. Errors if the module's backing theorem is not gate-passed (BLOCKED).
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | object | yes | – |
| module_id | string | yes | – |
| subject | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viridis_certify_envelope Viridis certify envelope ~54
Certify then return a 'Certified by ViridisOS' mark envelope (profile conservation-claim).
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | object | yes | – |
| module_id | string | yes | – |
| subject | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viridis_compute_toll Viridis compute toll ~49
Compute the unified Viridis protocol margin (the take) + pass-through card cost for a settlement.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | yes | – |
| payee_tier | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viridis_list_modules Viridis list modules ~31
List ViridisOS modules and their LIVE/BLOCKED state (A-1 against the live canon).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viridis_verify_mark Viridis verify mark ~40
Verify a 'Certified by ViridisOS' envelope against the shared trust root.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | – |
| profile | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.jdhart81/viridisos MCP server?
io.github.jdhart81/viridisos is a hosted endpoint at https://mcp.viridisconservation.com/viridisos/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-viridisos 'https://mcp.viridisconservation.com/viridisos/mcp'
What is the io.github.jdhart81/viridisos MCP server?
io.github.jdhart81/viridisos is an MCP server listed in the public MCP registry as io.github.jdhart81/viridisos. ViridisOS, theorem-backed conservation certification + the unified trust root/mark/toll. Certify pa. This page covers its hosted endpoint (https://mcp.viridisconservation.com/viridisos/mcp).
Is the io.github.jdhart81/viridisos MCP server safe to use?
io.github.jdhart81/viridisos 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/viridisos MCP server expose?
io.github.jdhart81/viridisos exposes 7 tools: viridis_list_modules, viridis_certify, viridis_certify_envelope, viridis_verify_mark, viridis_bind_did, and 2 more. Their descriptions and schemas cost roughly 323 tokens of context every time the server is loaded.
Does the io.github.jdhart81/viridisos MCP server require authentication?
No. We connected to io.github.jdhart81/viridisos without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.jdhart81/viridisos MCP server still maintained?
io.github.jdhart81/viridisos 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.