Back to MCP servers

Verdigraph

https://mcp.viridisconservation.com/verdigraph/mcp
● healthy

Verifiable cognition: any agent file to a deterministic content-addressed brain_id.

What we measured

Over the last 30 days we probed this MCP server 30 times on 29 days; it answered 30 (100%). Median response 161 ms, 95th percentile 195 ms.

When we called tools/list it returned 4 tools, including build_brain, verify_brain, detect_format, over MCP protocol revision 2025-11-25.

Among the 53,545 reachable MCP servers in our snapshot of 2026-11-18 02:53 UTC, it is faster than 81% and higher on readiness than 92%.

From agent-tools.cloud's own probes, last checked 2026-11-17. How we measure

Tools (4)

As returned by the server's own tools/list when we called it.

build_brain
Compile an agent file into a deterministic, content-addressed brain. content = the file as a string; format = verdigraph_genome | claude_project_export…
verify_brain
Machine-check a cognition claim: recompute the brain from the submitted content and compare against the claimed brain_id and/or content_hash. valid=true…
detect_format
Detect which supported agent-file format the content is (verdigraph_genome, claude_project_export, openai_assistant, prompt_list) before building.
describe_agent
Return capabilities and input contract.
Transport
streamable-http
Auth
none
Cost
Free to connect, list tools and call read-only tools. Paid tools answer payment_required with the exact price and how to pay (card credits, seat, or x402 USDC); see the docs page.
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 89/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here A, 100.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (187 ms).
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 4 tool(s) with descriptions.
Verified identity 8/10 Publisher declared (repository, package or homepage) and domain control verified on agent-tools.cloud (company-registry check not available yet).
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 85 points, scaled to 100.
Responsiveness: Responsive (187 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-17.
Eight criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 85 points are scaled to 100. For a server that answers HTTP 401 we also check weekly, without credentials, the MCP authorization discovery (Bearer challenge, protected-resource and authorization-server metadata, PKCE, client registration): it earns up to 5 handshake points, the full live points and up to 5 auth points; initialize, the protocol revision and tools need credentials and score 0. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,545 reachable MCP servers in our daily snapshot (2026-11-18 02:53 UTC). Display only; it does not change search order.

Readiness
Higher than 92% of peers
This listing 89 · peer median 85
Latency
Faster than 81% of peers
This listing 163 ms · peer median 370 ms

Where it loses the most points, and how to win them back

  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Protocol revision −2 — Support the current protocol revision.
    Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
  • Verified identity −2 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage) and domain control verified on agent-tools.cloud (company-registry check not available yet).

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

GitHub
★ 0 · 1 forks
last push 2026-11-11

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://mcp.viridisconservation.com/verdigraph/mcp
JSON-RPC initialize probe
curl -X POST https://mcp.viridisconservation.com/verdigraph/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://github.com/jdhart81/viridis-agent-fleet/blob/main/docs/servers/verdigraph.md
Source code
https://github.com/jdhart81/viridis-agent-fleet