Skip to main content
MCP resources expose stable read-only snapshots assistants can fetch without calling action tools. List them with resources/list after MCP initialize.

​
Resource catalog

URIScopeContent
echozero://user/profileread:agentsAuthenticated user profile
echozero://user/subscriptionsread:agentsAgent subscriptions
echozero://user/activationsread:strategiesActive strategy activations
echozero://tokens/trendingread:tokensTrending tokens
echozero://agents/pinnedread:agentsPinned agents
echozero://strategies/status-countsread:strategiesStrategy status breakdown
echozero://earn/rewardsread:earnEarn rewards summary
echozero://notifications/recentread:notificationsRecent notifications
echozero://developer-agents/featuredread:agentsFeatured marketplace agents
echozero://developer-agents/top-performersread:agentsTop performing agents

​
Example resources/read

curl -sS https://mcp.echozero.app/mcp \
  -H "x-api-key: $EZ_API_KEY" \
  -H "Content-Type: application/json" \
  -H "mcp-session-id: $MCP_SESSION_ID" \
  -d '{
    "jsonrpc": "2.0",
    "id": 4,
    "method": "resources/read",
    "params": { "uri": "echozero://tokens/trending" }
  }'
Resources return JSON text suitable for model context. They respect the same scopes as the equivalent REST routes.

​
Prompts vs resources

  • Resources = static URI-addressable snapshots
  • Prompts = templated multi-step instructions (prompts/get)
See MCP tools for the full tool catalog.