Atomadic Nexus

tech.atomadicPublished by atomadic.techv0.1.1Updated Oct 24, 2026

Atomadic Nexus — trust layer for the agent economy. 32 tools: trust gates, x402, lineage, swarm.

The publisher's own server: Atomadic MCP

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

Atomadic Nexus is a local MCP server described as a trust layer for the agent economy, offering 32 tools for trust gates, x402, lineage and swarm.

What you can do
  • Apply trust gates, presumably to check or gate agent actions
  • Handle x402, a payment protocol for agents
  • Track lineage, likely provenance or history of agent activity
  • Coordinate swarm behavior among agents
  • The registry lists 32 tools in total but does not name or document them individually.
When to use it
Consider it if you are building or operating multi-agent systems and want trust checks, payment handling, provenance tracking or swarm coordination exposed to an assistant. The sparse documentation makes it hard to judge fit without inspecting the package yourself.
Requirements
Runs as a local process over stdio, installed from the PyPI package atomadic-nexus-sdk and started with the atomadic-nexus-mcp command. Desktop client only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The description mentions x402, a payment protocol, so tools may initiate or authorize spending; verify limits before use. Trust gates and swarm tools may act on or change state. No README, instructions or tool list is available, so behavior and data handling cannot be verified in advance.

Installation

In SourceWeft

  1. Open Atomadic Nexus in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Atomadic integrations