mesh-01 / aethelon-nexus
REMOTE · MESH-01.COM · 2 COMPONENTS
Sovereign orchestration node: signed receipts, self-serve agent keys, peer federation.
Available components
Last scanned (11 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 719 tokens (~79/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
- HSTS header: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Stability: unverified → 0.53 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 3 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.43 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 −3
- Authorization: fail → partial ▲ security
- 26 Oct 26 +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.
- 23 Oct 26 +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.
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 5 Nov 2026 · Probed https://mesh-01.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mesh-01.com | CN=YE1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6259b87e146f962ff70af869fbedded28b5 |
| SANs: mesh-01.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 mesh-01.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mesh-01.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer-when-downgrade |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mesh-01.com/mcp | Verified | 200 | |
| http (plaintext) | http://mesh-01.com/mcp | HTTPS enforced | 308 | https://mesh-01.com/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 →
nexus_arbitrage_quote Quote a DEX arbitrage route (simulation only) ~188
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[]).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_coordinate Submit a durable task for verifiable execution ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| task_id | string | – | – |
No examples provided.
nexus_health Check node health and queue depth ~23
Node health: RAM usage, durable queue depth, task counts by state.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
nexus_mesh_delegate Delegate a task to a federated peer node ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | public HTTPS URL for the signed result |
| payload_value | number | – | declared task value |
| peer | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_mesh_peers List active federation peers ~26
List active mesh peers. Authenticated callers also see private peers not announced publicly.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| peers | array | – | – |
No examples provided.
nexus_opportunities List latest autonomous scan findings ~29
Latest results from the node's autonomous arbitrage scanner. Simulated findings — reported, not promised.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
nexus_signal_scan Scan endpoints and extract JSON signal fields ~51
Concurrently probe public HTTPS endpoints and extract fields via dotted paths. Public targets only (SSRF-guarded).
| Name | Type | Req | Description |
|---|---|---|---|
| signals | array | yes | list of signal specs: url, method, fields to extract |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_stats Read per-engine telemetry counters ~27
Per-engine telemetry: invocation counts, p50/p99 latency in ms, cumulative declared value.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
nexus_task_status Check status and result of a submitted task ~41
Get status and result of a task by task_id. Finished tasks include their signed receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | task id returned by nexus_coordinate |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| task_id | string | – | – |
No examples provided.
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.
remote · mesh-01.com
claude mcp add --transport http com-mesh-01-aethelon-nexus 'https://mesh-01.com/mcp'
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.