MCP Server for Crypto Staking Agents: Stakao Tools and Safety Model
How Stakao exposes public read-only MCP tools for catalog discovery, x402 instructions, safety metadata, and public content search.
Published Jul 6, 2026 . Stakao . 8 min read
Direct answer
A Model Context Protocol server gives AI agents structured tools instead of forcing them to scrape pages. For staking products, MCP is best used first for read-only discovery, quoting, safety explanation, and public content search.
Stakao uses two complementary MCP surfaces
The product MCP and the content search MCP solve different problems. Keeping them separate makes the agent architecture clearer.
| Surface | Endpoint | Purpose |
|---|---|---|
| Product MCP | https://api.stakao.com/agent/mcp | Catalog, manifest, x402 instructions, pricing quote, safety metadata, and strategy explanation. |
| Content Search MCP | https://stakao.search.ai.cloudflare.com/mcp | Semantic search over public Stakao website content, blog posts, llms.txt, pricing, and docs. |
Read-only MCP tools available in V1
The V1 tool list is deliberately non-destructive. It gives agents context and product metadata, but not account authority.
- get_stakao_catalog returns public products available for recommendation-only agent use.
- get_agent_manifest returns endpoints, x402 price metadata, and safety boundaries.
- get_paid_allocation_instructions explains the USDC x402 request flow.
- get_reference_allocation_status reports freshness for hourly reference allocations.
- explain_strategy explains a selected catalog item.
- quote_allocation_product returns price, endpoint, payment rail, and safety metadata.
- search_public_content searches public Stakao content through Cloudflare AI Search.
Why the public MCP does not need OAuth
OAuth should exist only when an agent needs account-bound data or user-authorized actions. Stakao V1 MCP does neither.
The public MCP can answer what Stakao sells, how much it costs, which endpoints exist, how x402 payment works, and what the safety boundary is. None of that requires reading a user account.
Later, OAuth can be added for user-specific wallets, saved strategies, decision history, or activation requests that require explicit human consent. Publishing fake OAuth just for a score would make the architecture worse.
When should an agent use REST instead of MCP?
MCP is excellent for exploration and tool use. REST is still the cleaner contract for paid allocation creation and idempotent HTTP payment behavior.
- Use MCP to discover catalog items, explain products, quote the price, and search public documentation.
- Use REST OpenAPI when building deterministic integrations.
- Use POST /agent/recommendations/allocation for the paid x402 recommendation call.
- Use /agent/search when a simple search API is easier than an MCP client.
FAQ
Is the Stakao MCP public?
Yes. The V1 product MCP at https://api.stakao.com/agent/mcp is public and read-only. It does not require login.
Does the MCP expose user wallets or account data?
No. The V1 MCP exposes only public catalog, manifest, pricing, safety, and content-search tools.
Can the MCP create paid allocation recommendations?
Not directly in V1. Paid recommendations use the x402-protected HTTP endpoint so payment, idempotence, and audit are handled in one path.
Related pages
Agent entrypoints
These endpoints are public discovery surfaces. Paid allocation creation remains gated by x402 USDC and returns recommendation-only output.