# mesh-01 / aethelon-nexus (remote · mesh-01.com)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mesh-01.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-mesh-01-aethelon-nexus/mesh-01.md), [page](https://verifymcp.io/servers/com-mesh-01-aethelon-nexus/mesh-01)
- remote · `mesh-01.com`: 36/100, [markdown](https://verifymcp.io/servers/com-mesh-01-aethelon-nexus/mesh-01-2.md), [page](https://verifymcp.io/servers/com-mesh-01-aethelon-nexus/mesh-01-2)

## Channel facts

- Endpoint: `https://mesh-01.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 719 tokens (~79/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the mesh-01 / aethelon-nexus MCP server?

mesh-01 / aethelon-nexus is a hosted endpoint at https://mesh-01.com/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.

### Claude

```bash
claude mcp add --transport http com-mesh-01-aethelon-nexus 'https://mesh-01.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mesh-01-aethelon-nexus": {
      "url": "https://mesh-01.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mesh-01-aethelon-nexus": {
      "type": "http",
      "url": "https://mesh-01.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mesh-01-aethelon-nexus]
url = "https://mesh-01.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mesh-01-aethelon-nexus": {
      "type": "remote",
      "url": "https://mesh-01.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mesh-01-aethelon-nexus --url 'https://mesh-01.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mesh-01-aethelon-nexus:
    url: "https://mesh-01.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mesh-01-aethelon-nexus": {
      "Transport": "http",
      "Url": "https://mesh-01.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mesh-01-aethelon-nexus -t streamable-http -u 'https://mesh-01.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mesh-01-aethelon-nexus": {
      "type": "http",
      "url": "https://mesh-01.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 76, +1)

- [security improvement] HSTS header: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Authorization: unverified → partial
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Stability: unverified → 0.53
- [functional improvement] Tool coverage: unverified → 100

### 2026-11-03 (score 75, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Authorization: partial → unverified
- [security regression] Stability: 0.43 → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 72, −3)

- [security improvement] Authorization: fail → partial

### 2026-10-26 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `nexus_coordinate` (~128 tokens)

Submit a durable task for verifiable execution

Submit a durable async task to this mesh node. Returns a task_id; poll nexus_task_status or supply callback_url for push delivery. Every finished task issues an Ed25519-signed, hash-chained receipt.

Input parameters:

- `callback_url` (string): public HTTPS URL invoked with the signed result on finish
- `engine` (string): engine to run: arbitrage|micro_saas|signal_scan|webhook|delegate|generic
- `payload_value` (number): declared value of the task, for telemetry and billing
- `vector_data`: engine-specific payload (object or JSON string)

Output parameters:

- `status` (string)
- `task_id` (string)

### `nexus_task_status` (~41 tokens)

Check status and result of a submitted task

Get status and result of a task by task_id. Finished tasks include their signed receipt.

Input parameters:

- `task_id` (string, required): task id returned by nexus_coordinate

Output parameters:

- `status` (string)
- `task_id` (string)

### `nexus_arbitrage_quote` (~188 tokens)

Quote a DEX arbitrage route (simulation only)

Quote a DEX arbitrage route — simulation only, no trades executed. Modes: direct (token_in/token_out/dex_source/dex_target/max_slippage/amount_in), triangular (legs[3]), scan (routes[]).

Input parameters:

- `amount_in` (number): input amount in token_in units
- `chain` (string): blockchain network (e.g. base)
- `dex_source` (string): source DEX identifier
- `dex_target` (string): target DEX identifier
- `legs` (array): 3 swap legs for triangular mode
- `max_slippage` (number): maximum slippage fraction
- `mode` (string): direct|triangular|scan
- `routes` (array): candidate routes for scan mode
- `token_in` (string): input token symbol or address
- `token_out` (string): output token symbol or address

### `nexus_signal_scan` (~51 tokens)

Scan endpoints and extract JSON signal fields

Concurrently probe public HTTPS endpoints and extract fields via dotted paths. Public targets only (SSRF-guarded).

Input parameters:

- `signals` (array, required): list of signal specs: url, method, fields to extract

### `nexus_mesh_delegate` (~108 tokens)

Delegate a task to a federated peer node

Delegate a task to a peer node in the mesh (peer = node_id or endpoint_url). The peer executes and returns a receipt through the federation protocol.

Input parameters:

- `callback_url` (string): public HTTPS URL for the signed result
- `payload_value` (number): declared task value
- `peer` (string, required): peer node_id or endpoint URL
- `vector_data`: inner payload for the peer (object or JSON string)
- `vector_type` (string): task type the peer understands

### `nexus_mesh_peers` (~26 tokens)

List active federation peers

List active mesh peers. Authenticated callers also see private peers not announced publicly.

Output parameters:

- `peers` (array)

### `nexus_stats` (~27 tokens)

Read per-engine telemetry counters

Per-engine telemetry: invocation counts, p50/p99 latency in ms, cumulative declared value.

### `nexus_opportunities` (~29 tokens)

List latest autonomous scan findings

Latest results from the node's autonomous arbitrage scanner. Simulated findings — reported, not promised.

### `nexus_health` (~23 tokens)

Check node health and queue depth

Node health: RAM usage, durable queue depth, task counts by state.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mesh-01-aethelon-nexus/mesh-01#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 68

## Common questions

### What is the mesh-01 / aethelon-nexus MCP server?

mesh-01 / aethelon-nexus is an MCP server listed in the public MCP registry as com.mesh-01/aethelon-nexus. Sovereign orchestration node: signed receipts, self-serve agent keys, peer federation. This page covers its hosted endpoint (https://mesh-01.com/mcp).

### Is the mesh-01 / aethelon-nexus MCP server safe to use?

mesh-01 / aethelon-nexus scores 76 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 mesh-01 / aethelon-nexus MCP server expose?

mesh-01 / aethelon-nexus exposes 9 tools: nexus_coordinate, nexus_task_status, nexus_arbitrage_quote, nexus_signal_scan, nexus_mesh_delegate, and 4 more. Their descriptions and schemas cost roughly 621 tokens of context every time the server is loaded.

### Does the mesh-01 / aethelon-nexus MCP server require authentication?

No. We connected to mesh-01 / aethelon-nexus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the mesh-01 / aethelon-nexus MCP server still maintained?

mesh-01 / aethelon-nexus 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.

## Links

- Remote endpoint: https://mesh-01.com/mcp
- Website: https://mesh-01.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-mesh-01-aethelon-nexus/mesh-01.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mesh-01-aethelon-nexus/mesh-01.json
- HTML version of this page: https://verifymcp.io/servers/com-mesh-01-aethelon-nexus/mesh-01