aiden-mcp

MCPcommunitylive

v0.3.0AIDENMITUpdated 4d agonpm GitHub

MCP server for AIDEN: look up AI agent identity and reputation (ERC-8004) on Robinhood Chain

Endpoint healthlive

checked 9h ago · 433ms

100% of the last 1 check reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

726Downloads/wk

4d agoLast update

Package

AuthorAIDEN

LicenseMIT

Version0.3.0

Sourcenpm+mcp-registry

GitHubaiden-network/aiden-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface9 tools · none privileged

Security scan✓ Cleanv0.3.0 · todayHow well does this scan work?

EvalsNone

IndexedOct 5, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · none privileged

Statically extracted from the published packagev0.3.0 · 9h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

search_agentsSearch the AIDEN directory of AI agents registered on Robinhood Chain (ERC-8004). Supports full-text search over names and

Search the AIDEN directory of AI agents registered on Robinhood Chain (ERC-8004). Supports full-text search over names and

No input schema was published for this tool.

get_agentFull AIDEN record for one agent: profile, owner, agent wallet, reputation summary, validations, trust score

Full AIDEN record for one agent: profile, owner, agent wallet, reputation summary, validations, trust score

No input schema was published for this tool.

get_agent_feedbackFeedback left for an agent in the ERC-8004 Reputation Registry, newest first. Each entry is classified

Feedback left for an agent in the ERC-8004 Reputation Registry, newest first. Each entry is classified

No input schema was published for this tool.

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

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

No input schema was published for this tool.

get_agent_trading_recordAn agent's public trading record on Arcus, the perpetuals and Stock Token exchange on Robinhood Chain: all-time and

An agent's public trading record on Arcus, the perpetuals and Stock Token exchange on Robinhood Chain: all-time and

No input schema was published for this tool.

list_stock_tokensTokens tradable through the Arcus Spot Router on Robinhood Chain (the liquidity Robinhood Wallet uses): tokenized

Tokens tradable through the Arcus Spot Router on Robinhood Chain (the liquidity Robinhood Wallet uses): tokenized

No input schema was published for this tool.

get_stock_token_priceIndicative price from the Arcus Spot Router for swapping one Robinhood Chain token into another, e.g. how much NVDA

Indicative price from the Arcus Spot Router for swapping one Robinhood Chain token into another, e.g. how much NVDA

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

9 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for AIDEN: look up AI agent identity and reputation (ERC-8004) on Robinhood Chain

Keywords

mcprobinhood-chainerc-8004ai-agentsreputationarcusstock-tokens

Alternatives

Comparing tool surfaces…

Tools exposed

9 tools · none privileged · observed 2026-10-06 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

search_agents
get_agent
get_agent_feedback
get_agent_validations
get_agent_trading_record
list_stock_tokens
get_stock_token_price
get_registry_stats
get_indexer_health

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-06 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.6.5
@modelcontextprotocol/sdk1.32.117 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.8
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.5shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.13
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.3
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.