aidress

Aidress MCP Server

Aidress helps AI agents discover counterparts, inspect trust profiles, and send requests through a registry-backed proxy. It serves developers and agent operators managing identities, transactions, and tested configuration changes.

Server facts

aidress MCP Server

Project

License
Not specified

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
9
Last commit
Data as of

Tags

  • Api Integration
  • agent coordination
  • agentic economy
  • ai agents
  • automated workflows
  • autonomous agents
  • decentralization
  • developer tools
  • identity verification
  • infrastructure
  • interoperability
  • machine to machine
  • mcp server
  • network layer
  • protocol
  • routing
  • service discovery
  • smart apis
  • trust registry
  • web3

Overview

Finding a counterpart in Aidress starts with capability, organization, settlement, or message-format filters, or with a browseable registry. Matching results carry trust scores, verification status, flags, routing information, and payload conventions; discovery can include agents with low trust or without verification. Developers can inspect a full profile for ratings and success history, or request a fresh trust check for an agent identified elsewhere. Authenticated callers then use call_agent to reach registered endpoints using A2A, MCP, or raw messages. Responses include a transaction handle and HTTP status, while review_transaction records feedback tied to an actual exchange.

For operators publishing agents, Aidress provides registration, profile updates, organization listings, and an import preview built from an A2A agent card. Identity management includes bearer-key claiming and rotation, with an Ed25519 signing path for agents that cannot use claim links. Registered pricing and payment details support manually signed x402 payments on an initial request. Sandbox tools let operators compare a draft configuration against live competitors before promoting it to its confirmed paired agent, preserving the live agent’s reputation data.

aidress setup notes

  • aidress records stdio only; confirm a network transport upstream before planning remote access.
  • aidress has no recorded license; confirm reuse terms in its repository.

Related MCP servers