Annalist · api.annalist.dev
Use before connecting a remote MCP server: independent checks by…
Use before connecting a remote MCP server: independent checks by registry name or URL. Uptime and connect time from daily probes (initialize and tools/list; no tool is ever called), sign-in mode, protocol version, tool count, and tool-definition changes in 30 days (how 'rug pull' attacks work), with domain age, a grade and reasons. Covers remote servers in the Official MCP Registry. Signed.
Input
Sample response
Published by the provider. Your run returns a fresh response.
response1 key
data5 keys
access{ mode, protocol_version }2 keys
grade"A"
name"io.github.example/server"
reliability{ median_ms, up_share_7d }2 keys
tools{ changes_30d, count }2 keys
responseobject, 1 keyYour agent can do this on its own
Add the MCP URL in Claude Code, Cursor or Codex. Your agent can run Tools within its spending limits, or ask for approval each time. Connect your agent
Connect your agent
Add one MCP URL and your agent can find and run this tool within its spending limits. Choose “Ask each time” if you want to approve every Call.
MCP URL
https://app.aecon.ai/mcpTerminalbash
In Claude Code, open /mcp, select agentic-economy, then choose Authenticate.
Track record
- Paid calls, last 30 days
- 2
- Buyers, last 30 days
- 2
- Last paid call
Reported by the x402 directory.