Skip to main content
Glama
aiden-network

aiden-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AIDEN_API_URLNoAIDEN indexer API. Use `http://127.0.0.1:4000` for a local indexerhttps://api.aiden.network
AIDEN_TIMEOUT_MSNoPer-request timeout, 1000 to 6000010000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_agentsA

Search the AIDEN directory of AI agents registered on Robinhood Chain (ERC-8004). Supports full-text search over names and descriptions, filtering by owner address, and sorting by trust score, feedback count or settled USDG.

get_agentA

Full AIDEN record for one agent: profile, owner, agent wallet, reputation summary, validations, trust score and the USDG settlement evidence behind it.

get_agent_feedbackA

Feedback left for an agent in the ERC-8004 Reputation Registry, newest first. Each entry is classified (receipt, rating, metric, self, revoked) with a normalised 0-100 rating where applicable.

get_agent_validationsB

The latest 100 validation requests and responses for an agent from the ERC-8004 Validation Registry.

get_registry_statsA

Totals across the AIDEN index: agents, owners, feedback, validations and settled USDG.

get_indexer_healthA

How far the AIDEN indexer is behind the Robinhood Chain head. Check this when results look empty or stale.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

Most tools target clearly distinct resources: feedback, validations, agent detail, search, stats, and indexer health. The only mild overlap is that get_agent returns a reputation/validation summary while get_agent_feedback and get_agent_validations return detailed registry entries, so an agent might occasionally pick the summary tool when it needs the full detail.

Naming Consistency5/5

All tools use a consistent snake_case verb_noun pattern: get_agent_feedback, get_agent_validations, get_indexer_health, search_agents, get_agent, get_registry_stats. The verb choice (get for retrieval, search for discovery) is predictable and uniform.

Tool Count5/5

Six tools is well-scoped for a read-only agent directory and registry explorer. Each tool covers a distinct facet (search, detail, reputation, validation, aggregate stats, indexer health) without redundancy.

Completeness4/5

Discovery, detail, reputation, validation, aggregate stats, and indexer health are all covered, which is strong for this domain. Minor gaps include no dedicated owner-centric lookup or explicit pagination/listing tool, though search_agents with owner filtering partially compensates.

Maintenance

ActivityMaintained
ResponsivenessNo issues