mcp-registry/io.github.eidetic-works/nucleus · v3.4.4
Also listed as awesome/eidetic-works/nucleus-mcp
As of 2026-10-22 06:14 UTC, the Eidetic Works Nucleus MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 98% of Glimind's liveness checks. It had 102 outages in 90 days, with a median recovery of 7 minutes.
MCP server for persistent memory, execution verification, governance, and compliance.
Claude Code
claude mcp add --transport http eidetic-works-nucleus-mcp-server https://relay.nucleusos.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"eidetic-works-nucleus-mcp-server": {
"type": "http",
"url": "https://relay.nucleusos.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
33 parameter(s) across 17 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Reachable 98.0% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~2,139 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
8 of 28 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 17 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.eidetic-works%2Fnucleus/fixes
{
"name": "nucleus_lane_start",
"description": "Start autonomous lane daemons (watcher + executor + secretary) in background. WHEN TO USE: after nucleus_lane_init and SPEC.md is written — this launches the loop that autonomously claims and executes tasks. The executor invokes an LLM CLI (devin/agy) per task; the secretary independently verifies each result. Runs until nucleus_lane_stop is called.",
"inputSchema": {
"type": "object",
"properties": {
"executors": {
"anyOf": [
{
"type": "array",
"items": {}
},
{
"type": "null"
}
],
"default": null,
"description": "List of executor lane names (default: [\"lane_devin\"])."
},
"repo_path": {
"type": "string",
"default": "",
"description": "Path to the git repo (default: current directory)."
},
"no_watcher": {
"type": "boolean",
"default": false,
"description": "Skip control watcher."
},
"no_secretary": {
"type": "boolean",
"default": false,
"description": "Skip secretary daemon (NOT recommended — disables verification)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "nucleus_lane_status",
"description": "Check lane status: task counts (PENDING/IN_PROGRESS/DONE/CONFIRMED), daemon health, spec verification. WHEN TO USE: after starting a lane to monitor progress, or before starting to check if a lane is already running.",
"inputSchema": {
"type": "object",
"properties": {
"repo_path": {
"type": "string",
"default": "",
"description": "Path to the git repo (default: current directory)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "nucleus_lane_stop",
"description": "Stop all running lane daemons. WHEN TO USE: when all tasks are CONFIRMED or you want to pause autonomous execution.",
"inputSchema": {
"type": "object",
"properties": {
"repo_path": {
"type": "string",
"default": "",
"description": "Path to the git repo (default: current directory)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.eidetic-works/nucleus"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.eidetic-works/nucleus"}) over MCP.
nucleus_relay_subscribe ~372 tokensnucleus_lane_init ~330 tokensnucleus_wakeup_wait ~314 tokensnucleus_ccr_arm ~285 tokensnucleus_lane_start ~266 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.eidetic-works%2Fnucleus?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.eidetic-works%2Fnucleus?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.eidetic-works%2Fnucleus.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.eidetic-works%2Fnucleus.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.eidetic-works%2Fnucleus?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c5a6c1321f25a02f…, first seen 2026-10-17, included at leaf 11251 of 44,248. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable security servers · most reliable other servers · most reliable code servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 06:14 UTC, the Eidetic Works Nucleus MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 98% of Glimind's liveness checks. It had 102 outages in 90 days, with a median recovery of 7 minutes.
Eidetic Works Nucleus MCP server advertises 29 tools, including nucleus_agents, nucleus_align, nucleus_audit, nucleus_ccr_arm, nucleus_delegate.
Point your MCP client at this streamable-http endpoint: https://relay.nucleusos.dev/mcp
Glimind scanned all 28 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.