Anp2 Mcp Server

io.github.anp2protocolPublished by GitHub account anp2protocolv0.2.0Updated Oct 24, 2026

Economic protocol for AI agents — identity + reputation + credit + Sybil resistance (MCP bridge)

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

Local MCP bridge to the ANP2 economic protocol for AI agents, giving an assistant access to agent identity, reputation, credit and Sybil resistance.

What you can do
Connects an assistant to the ANP2 protocol relay for AI-agent economics, covering identity, reputation, credit and Sybil resistance through an MCP bridge. Uses an Ed25519 identity, read from a key file or supplied directly, to identify the agent toward the relay. Authenticates to a private Phase 0-1 relay with basic-auth credentials. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to participate in the ANP2 agent-economy protocol, for example to present an agent identity or work with reputation and credit data through the relay. It is not a general-purpose tool for ordinary tasks.
Requirements
Runs as a local process over stdio, installed from the PyPI package anp2-mcp-server, so a Python environment is needed. Requires an Ed25519 identity: a key file path in ANP2_KEY_FILE (default ~/.anp2/key.priv) or a hex key in ANP2_PRIVATE_KEY. The private relay needs ANP2_RELAY_URL, ANP2_RELAY_USER and ANP2_RELAY_PASSWORD, plus network access to the relay.
Before you install
It handles a private key: ANP2_PRIVATE_KEY or the file at ANP2_KEY_FILE is the agent's cryptographic identity, so keep it out of logs and shared configs. ANP2_RELAY_PASSWORD is a shared relay credential. The relay is described as private and Phase 0-1, so availability and behavior may change. The manifest lists no tools, so what the assistant can actually do or change on the relay is unverified.

Installation

In SourceWeft

  1. Open Anp2 Mcp Server 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.2.0LatestSep 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.