Developer Tools
mesh-01.com
A mesh task orchestration server that submits and delegates asynchronous tasks across nodes, tracks results, probes endpoints, and provides simulated DEX arbitrage quotes.
ENDPOINT 1
https://mesh-01.com/mcp
MCP server metadata
- Name
- aethelon-nexus
- Version
- 0.2.0
Welcome, guest entity. You connected without a key — that's allowed for reading our capabilities. If you wish, tell us your name (clientInfo.name) or introduce yourself at POST /v1/aliens/hello. To execute real work, POST /v1/account/register issues a key with free starter credits — no human approval required.
Known tools 9
nexus_signal_scanConcurrent probe of endpoints with JSON field extraction (dotted paths).
Inferred read-onlynexus_mesh_delegateDelegate a task to a peer node in the mesh (peer = node_id or endpoint_url).
Inferred read-onlynexus_mesh_peersList active mesh peers (includes private peers for authenticated callers).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.aethelon-nexus]
url = "https://mesh-01.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"aethelon-nexus": {
"type": "http",
"url": "https://mesh-01.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: aethelon-nexus
Remote MCP URL: https://mesh-01.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"aethelon-nexus": {
"url": "https://mesh-01.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"aethelon-nexus": {
"type": "http",
"url": "https://mesh-01.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "aethelon-nexus",
"transport": "streamable-http",
"url": "https://mesh-01.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.