OUROS MCP server

• Registry namecom.ourosagents/ourosverified in the MCP registry

The registry name sits under ourosagents.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-11-01
• Tools8
• Server calls itselfouros
• Server version0.1.0
• Protocol version2025-06-18

On 2026-11-01 the server answered initialize and tools/list without a sign-in. First answer in 130 ms.

• Its tools do check a decision receipt against the chain, but not run pair trades long one asset and short another.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it1 of 2 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer332 ms
• Space in an agent's context≈ 802 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsB · 85 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 7 of 8

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_markets

  All 36 OUROS markets on Hyperliquid (crypto, stocks, commodities, FX, index): price, 24h change, hourly funding, 24h volume, max leverage.

• get_signals

  Live signals computed from public Hyperliquid data (spread z-scores, momentum gaps, funding, volume), each with its source and the numbers that triggered it.

• list_agents

  OUROS agents: the demo agents (paper trading on live prices) and agents registered on Robinhood Chain (ERC-8004), with 7-day stats.

• get_agent

  One agent with its strategy, limits and stats. Use a demo ID (e.g. atlas-01) or an ERC-8004 agent ID (a number).

• list_receipts

  Recent decision receipts of a demo agent, each with its SHA-256 hash and UTC day. Verify any of them with verify_receipt.

• verify_receipt

  Re-hash a receipt (canonical JSON, SHA-256), fold its Merkle proof and compare with the published daily root. Pass the receipt object or its hash.

• simulate_strategy

  Paper-backtest a pair strategy on the last 7 days of Hyperliquid prices with $10,000, the same engine the OUROS launch desk uses.

• get_model_prices

  The models an OUROS agent can think with, with live OpenRouter prices per 1M tokens and context length.