Home / MCP registry index / services.ottoai/otto

Otto Intel

services.ottoai/otto in the official MCP registry. Endpoint https://mcp.ottoai.services/mcp.

The registry describes it as: Otto AI hosted MCP: 16 pay-per-call market-intelligence tools, USDC via x402 on Base, no API keys.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http otto https://mcp.ottoai.services/mcp

{
  "mcpServers": {
    "otto": {
      "url": "https://mcp.ottoai.services/mcp"
    }
  }
}

code --add-mcp '{"name":"otto","type":"http","url":"https://mcp.ottoai.services/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

otto_crypto_news otto_news_recaps otto_tokenized_equities otto_rh_season otto_equity_intel otto_insider_trades otto_institutional_holdings otto_equity_smart_money otto_equity_smart_money_brief otto_base_season otto_pm_markets otto_pm_crypto otto_stock_pools otto_tokenized_stock_movers otto_equity_news otto_earnings_calendar otto_financial_statements otto_material_events otto_proposed_insider_sales otto_pools_search otto_token_security otto_prepare_swap otto_prepare_bridge otto_prepare_polymarket_order otto_prepare_yield_deposit otto_prepare_yield_withdraw otto_prepare_stock_buy otto_sponsored_account otto_native_yield_userop otto_submit_under_delegation otto_delegation_fence_status otto_delegation_fence otto_delegation_status otto_delegation_revoke otto_delegation_cap otto_delegation_operations otto_delegation_reconcile otto_delegation_exit otto_lp_collect_userop otto_muse_autopay_availability otto_muse_autopay_prepare otto_muse_autopay_enroll otto_muse_autopay_sign otto_muse_autopay_status otto_muse_autopay_revoke otto_catalog otto_x_recipes

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): 3cf91aa816c68d00. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/services-ottoai-otto/badge.svg)](https://lazaretto.dev/mcp-registry/services-ottoai-otto)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers