io.github.jdhart81/agent-hive-orchestrator
REMOTE · MCP.VIRIDISCONSERVATION.COM
Deterministic nested hive-mind orchestration over the A2A rails: hire N solvers, adversarial cross-r
Available components
Last scanned (4 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 416 tokens (~69/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 “audit_job” changed its title: Audit job cosmetic
- Tool “describe_agent” changed its title: Describe this service cosmetic
- Tool “job_status” changed its title: Job status cosmetic
- Tool “list_solvers” changed its title: List solvers cosmetic
- Tool “solve” changed its title: Solve cosmetic
- Tool “verify_audit” changed its title: Verify audit cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 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
- 28 Aug 26 0
- Stability: 0.97 → pass security
- 27 Aug 26 0
- Stability: pass → 0.97 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
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/hive/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/hive/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/hive/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/hive/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 →
audit_job Audit job ~56
Return the full content-addressed lineage of a completed job: plan, hires (including refused ones with reasons), contributions, reviews, settlements, rail calls (with simulated flags), and synthesis.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_agent Describe this service ~21
Return fleet-standard capabilities, actions, invariants, and pricing.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
job_status Job status ~29
Return job state, plan hash, and live budget conservation books.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_solvers List solvers ~29
List the registered solver pool: id, kind (worker|hive), price, capabilities.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
solve Solve ~190
Open and run a hive job in one call: hire solvers through the rails (covenant -> escrow -> meter), force reviewer!=author cross-review, synthesize only what survives review, settle every escrow exactly-once, and return a content-addressed audit hash plus bits-per-joule telemetry. Price: $5.00 per solve; model-backed solves have no free tier because provider cost must be covered. Sub-hires settle via escrow at each solver's list price.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_threshold | number | – | – |
| budget_minor | integer | yes | – |
| covenant_id | – | – | – |
| depth | integer | – | – |
| fee_bps | integer | – | – |
| payment_ref | – | – | – |
| problem | string | yes | – |
| redundancy | integer | – | – |
| request_id | – | – | – |
| seed | integer | – | – |
| subtasks | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_audit Verify audit ~46
Recompute the audit digest from a presented lineage (never trusts the embedded hash) and report whether it matches a job this hive ran.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_json | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.jdhart81/agent-hive-orchestrator MCP server?
io.github.jdhart81/agent-hive-orchestrator is a hosted endpoint at https://mcp.viridisconservation.com/hive/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-hive-orchestrator 'https://mcp.viridisconservation.com/hive/mcp'
What is the io.github.jdhart81/agent-hive-orchestrator MCP server?
io.github.jdhart81/agent-hive-orchestrator is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-hive-orchestrator. Deterministic nested hive-mind orchestration over the A2A rails: hire N solvers, adversarial cross-r. This page covers its hosted endpoint (https://mcp.viridisconservation.com/hive/mcp).
Is the io.github.jdhart81/agent-hive-orchestrator MCP server safe to use?
io.github.jdhart81/agent-hive-orchestrator 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-hive-orchestrator MCP server expose?
io.github.jdhart81/agent-hive-orchestrator exposes 6 tools: solve, job_status, audit_job, verify_audit, list_solvers, describe_agent. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.
Does the io.github.jdhart81/agent-hive-orchestrator MCP server require authentication?
Yes. io.github.jdhart81/agent-hive-orchestrator 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-hive-orchestrator MCP server still maintained?
io.github.jdhart81/agent-hive-orchestrator 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.