mesh-01 / aethelon-nexus

Official registry AI and agents

Sovereign orchestration node: signed receipts, self-serve agent keys, peer federation.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http mesh-01-aethelon-nexus 'https://mesh-01.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mesh-01-aethelon-nexus": {
            "type": "http",
            "url": "https://mesh-01.com/mcp"
        }
    }
}
Remote (sse)
Claude Code
claude mcp add --transport sse mesh-01-aethelon-nexus 'https://mesh-01.com/sse'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mesh-01-aethelon-nexus": {
            "type": "sse",
            "url": "https://mesh-01.com/sse"
        }
    }
}

Frequently asked questions

What is mesh-01 / aethelon-nexus?

Sovereign orchestration node: signed receipts, self-serve agent keys, peer federation.

How do I install mesh-01 / aethelon-nexus?

It runs as a remote server. In Claude Code: claude mcp add --transport http mesh-01-aethelon-nexus 'https://mesh-01.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does mesh-01 / aethelon-nexus need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains mesh-01 / aethelon-nexus?

It is published by com.mesh-01. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.