io.github.jdhart81/neurogenesis
REMOTE · MCP.VIRIDISCONSERVATION.COM · SCANNED SEP 20
Developmental agents for the agent economy: create an agent from a digital genome, then evolve it wi
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 921 tokens (~65/item across 14 items; 14 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_agent" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 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
How do I install the io.github.jdhart81/neurogenesis MCP server?
io.github.jdhart81/neurogenesis is a hosted endpoint at https://mcp.viridisconservation.com/neurogenesis/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-neurogenesis 'https://mcp.viridisconservation.com/neurogenesis/mcp'
{
"mcpServers": {
"jdhart81-neurogenesis": {
"url": "https://mcp.viridisconservation.com/neurogenesis/mcp"
}
}
} {
"servers": {
"jdhart81-neurogenesis": {
"type": "http",
"url": "https://mcp.viridisconservation.com/neurogenesis/mcp"
}
}
} [mcp_servers.jdhart81-neurogenesis] url = "https://mcp.viridisconservation.com/neurogenesis/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jdhart81-neurogenesis": {
"type": "remote",
"url": "https://mcp.viridisconservation.com/neurogenesis/mcp",
"enabled": true
}
}
} openclaw mcp add jdhart81-neurogenesis --url 'https://mcp.viridisconservation.com/neurogenesis/mcp' --transport streamable-http
mcp_servers:
jdhart81-neurogenesis:
url: "https://mcp.viridisconservation.com/neurogenesis/mcp" {
"McpServers": {
"jdhart81-neurogenesis": {
"Transport": "http",
"Url": "https://mcp.viridisconservation.com/neurogenesis/mcp"
}
}
} assistant mcp add jdhart81-neurogenesis -t streamable-http -u 'https://mcp.viridisconservation.com/neurogenesis/mcp'
{
"mcpServers": {
"jdhart81-neurogenesis": {
"type": "http",
"url": "https://mcp.viridisconservation.com/neurogenesis/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 10 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compute_efficiency_report” rewrote its description, which is the text the model reads security
- Tool “register_compute_profile” rewrote its description, which is the text the model reads security
- Tool “route_task” rewrote its description, which is the text the model reads security
- Schema quality: 808 → 921 ▼ functional
- New tool “record_route_outcome” functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 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
- 30 Jul 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 20 Sept 2026 · Probed https://mcp.viridisconservation.com/neurogenesis/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/neurogenesis/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/neurogenesis/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/neurogenesis/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 →
best_next_steps ~54
Routing recommendation: the strongest next cognitive steps from a given node, by learned edge weight and trust.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| from_node | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
compute_efficiency_report ~61
Free read: decision/outcome receipts, route modes, compute avoided, predicted savings, predicted-vs-observed cost/latency/energy coverage, and Landauer-floor context. Estimates and observations stay distinct.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_agent ~70
Create a developmental agent from a digital genome: {agent_name, purpose, initial_nodes (unique, >=1), fitness_metrics (>=1), optional growth_rules / safety_axioms}. Returns agent_id + initial graph summary.
| Name | Type | Req | Description |
|---|---|---|---|
| genome | object | yes | – |
| request_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_agent ~30
Remove a developmental agent from this mount.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| request_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_agent ~14
Return capabilities and input contract.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_state ~44
Portable state document for an agent (import_state recreates it anywhere — including a self-hosted verdigraph-neurogenesis).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_agent ~39
Full current state: genome, cognitive graph (nodes/edges with weights and trust), and summary counts.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ledger ~50
The append-only developmental ledger: every growth, pruning, and evaluation event with reasons (NG3 — returned verbatim).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
import_state ~31
Recreate an agent from an export_state document.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | – | – | – |
| state | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_agents ~19
All developmental agents on this mount, with summary counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
record_route_outcome ~102
Attach one observed outcome to a Wu Wei decision. Actual cost, latency, and energy are optional and remain explicitly unknown when omitted. One append-only, hash-bound outcome is allowed per decision.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_cost_usd | – | – | – |
| actual_energy_wh | – | – | – |
| actual_latency_ms | – | – | – |
| decision_id | string | yes | – |
| notes | string | – | – |
| request_id | – | – | – |
| success_score | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
register_compute_profile ~94
Register a caller-owned Wu Wei execution profile: reuse/cache, deterministic rule, local model, tool/workflow, or cloud model. Profiles can declare quality, reliability, capabilities, token costs, latency, locality, energy rates or average power, carbon intensity, and cache confidence/age. Routing never invents capacity or energy evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object | yes | – |
| request_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
route_task ~94
Choose the least-burden eligible route for a task. Hard constraints include quality, reliability, locality, capabilities, context, cost, latency, and energy. Optional baselines quantify predicted savings. Explicit allow_defer/value/urgency fields may produce a no-work decision; no result is then claimed. Returns a hash-bound decision receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | – | – | – |
| task | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
submit_evaluation ~119
Evolve an agent with one task outcome: {task_id, task_type, success_score in [0,1], optional accuracy/user_satisfaction/ cost_efficiency/safety_score/notes/used_nodes/used_edges}. Success strengthens the used edges, failure weakens them; growth and pruning follow the genome's rules under its safety axioms (NG1). Returns the new developmental-ledger events.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| evaluation | object | yes | – |
| request_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.jdhart81/neurogenesis MCP server?
io.github.jdhart81/neurogenesis is an MCP server listed in the public MCP registry as io.github.jdhart81/neurogenesis. Developmental agents for the agent economy: create an agent from a digital genome, then evolve it wi. This page covers its hosted endpoint (https://mcp.viridisconservation.com/neurogenesis/mcp).
Is the io.github.jdhart81/neurogenesis MCP server safe to use?
io.github.jdhart81/neurogenesis scores 73 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/neurogenesis MCP server expose?
io.github.jdhart81/neurogenesis exposes 14 tools: create_agent, submit_evaluation, get_agent, list_agents, best_next_steps, and 9 more. Their descriptions and schemas cost roughly 821 tokens of context every time the server is loaded.
Does the io.github.jdhart81/neurogenesis MCP server require authentication?
No. We connected to io.github.jdhart81/neurogenesis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.jdhart81/neurogenesis MCP server still maintained?
io.github.jdhart81/neurogenesis is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.