Skip to content

mesh-01 / aethelon-nexus MCP server

com.mesh-01/aethelon-nexusmesh-01.comstreamable-httpv0.2.0Scanned

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

9 tools: 7 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 7 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the mesh-01 / aethelon-nexus MCP server can do

The mesh-01 / aethelon-nexus MCP server is published by mesh-01.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (7 tools: nexus_coordinate, nexus_arbitrage_quote, nexus_signal_scan, nexus_mesh_delegate and 3 more), but cannot delete data. 2 tools only read.

2 tools bring in text other people can write (nexus_signal_scan and nexus_mesh_delegate); 2 tools can send data out of your system (nexus_coordinate and nexus_mesh_delegate).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 7Claude Code: ask
  • nexus_arbitrage_quoteQuote a DEX arbitrage route — simulation only, no trades executed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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[]).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • nexus_coordinateSubmit a durable async task to this mesh node.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: false
  • nexus_healthNode health: RAM usage, durable queue depth, task counts by state.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Node health: RAM usage, durable queue depth, task counts by state.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • nexus_mesh_delegateDelegate a task to a peer node in the mesh (peer = node_id or endpoint_url).Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
  • nexus_opportunitiesLatest results from the node's autonomous arbitrage scanner.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Latest results from the node's autonomous arbitrage scanner. Simulated findings — reported, not promised.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • nexus_signal_scanConcurrently probe public HTTPS endpoints and extract fields via dotted paths.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Concurrently probe public HTTPS endpoints and extract fields via dotted paths. Public targets only (SSRF-guarded).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: true
  • nexus_statsPer-engine telemetry: invocation counts, p50/p99 latency in ms, cumulative declared value.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Per-engine telemetry: invocation counts, p50/p99 latency in ms, cumulative declared value.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • nexus_mesh_peersList active mesh peers.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List active mesh peers. Authenticated callers also see private peers not announced publicly.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • nexus_task_statusGet status and result of a task by task_id.No findings

    Why it is in this group

    • The name "nexus_task_status" says "status": a word for reading.
    Description, as the server wrote it
    Get status and result of a task by task_id. Finished tasks include their signed receipt.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:42 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
yes
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mesh-01.com/mcp: tools/list returned 9 tools to an anonymous client, including nexus_coordinate (write), nexus_arbitrage_quote (write), nexus_signal_scan (write), nexus_mesh_delegate (write), nexus_stats (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__aethelon-nexus__nexus_task_status",
      "mcp__aethelon-nexus__nexus_mesh_peers"
    ],
    "ask": [
      "mcp__aethelon-nexus__nexus_coordinate",
      "mcp__aethelon-nexus__nexus_arbitrage_quote",
      "mcp__aethelon-nexus__nexus_signal_scan",
      "mcp__aethelon-nexus__nexus_mesh_delegate",
      "mcp__aethelon-nexus__nexus_stats",
      "mcp__aethelon-nexus__nexus_opportunities",
      "mcp__aethelon-nexus__nexus_health"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as aethelon-nexus. Review it before you use it.

Capability tags behind 3 rules
  • mcp__aethelon-nexus__nexus_coordinate outbound
  • mcp__aethelon-nexus__nexus_signal_scan untrusted-input
  • mcp__aethelon-nexus__nexus_mesh_delegate untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.mesh-01/aethelon-nexus/verify?hash=46bd0b4b02137020a2b28a352782fd2031c3077b0bf6ef0f811d5671bcce790f" | jq -e '.changed == false'

Pinned hash 46bd0b4b0213, from Nov 13, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.mesh-01/aethelon-nexus/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.mesh-01/aethelon-nexus
[![Anlyon Radar](https://radar.anlyon.com/badge/com.mesh-01/aethelon-nexus.svg)](https://radar.anlyon.com/servers/com.mesh-01/aethelon-nexus)

Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.

mesh-01 / aethelon-nexus MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 9 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the mesh-01 / aethelon-nexus MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the mesh-01 / aethelon-nexus MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the mesh-01 / aethelon-nexus MCP server have?

9 tools: 7 write, 2 read. nexus_coordinate, nexus_arbitrage_quote, nexus_signal_scan, nexus_mesh_delegate, nexus_stats, nexus_opportunities, nexus_health, nexus_task_status and 1 more.

Does the mesh-01 / aethelon-nexus MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the mesh-01 / aethelon-nexus MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): nexus_coordinate and nexus_mesh_delegate.

Has the mesh-01 / aethelon-nexus MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.