mcp-registry/services.ottoai/otto · v0.1.4
As of 2026-10-20 06:39 UTC, the Ottoai Otto MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Otto AI hosted MCP: 16 pay-per-call market-intelligence tools, USDC via x402 on Base, no API keys.
Claude Code
claude mcp add --transport http ottoai-otto-mcp-server https://mcp.ottoai.services/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ottoai-otto-mcp-server": {
"type": "http",
"url": "https://mcp.ottoai.services/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
47 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
27 parameter(s) across 8 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~1,812 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 4 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
5 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/services.ottoai/otto"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/services.ottoai/otto"}) over MCP.
otto_prepare_bridge ~618 tokensotto_prepare_yield_deposit ~526 tokensotto_prepare_stock_buy ~511 tokensotto_prepare_swap ~500 tokensotto_prepare_polymarket_order ~447 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fservices.ottoai%2Fotto?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fservices.ottoai%2Fotto?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fservices.ottoai%2Fotto.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fservices.ottoai%2Fotto.svg :target: https://glimind.com/server/mcp-registry%2Fservices.ottoai%2Fotto?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1356bd205a3219e3…, first seen 2026-10-17, included at leaf 3024 of 31,281. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable knowledge servers · most reliable security servers · most reliable data servers · most reliable defi servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 06:39 UTC, the Ottoai Otto MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Ottoai Otto MCP server advertises 47 tools, including otto_base_season, otto_catalog, otto_crypto_news, otto_delegation_cap, otto_delegation_exit.
Point your MCP client at this streamable-http endpoint: https://mcp.ottoai.services/mcp
Glimind scanned all 47 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.