INDIVIDUAL MCP TOOL

explain_limits

Returns what a category's (or run's) result can and cannot tell you: status and its meaning, fixture flag, freshness, expiry, explicit limits, conflicts, funding, and the answer rule every consumer must follow.

torneo.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://torneo.ai/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for explain_limits and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

torneo.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.torneo]
url = "https://torneo.ai/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "torneo": {
      "type": "http",
      "url": "https://torneo.ai/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: torneo
Remote MCP URL: https://torneo.ai/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "torneo": {
      "url": "https://torneo.ai/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "torneo": {
      "type": "http",
      "url": "https://torneo.ai/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "torneo",
  "transport": "streamable-http",
  "url": "https://torneo.ai/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

list_categories — Lists every category with its status (OK: replicated ranking; LOCAL_VALIDITY: single block, no current rank claim; INDETERMINATE: precision insufficient, no rank), observation date, freshness and source run.
get_results — Answers for one category with the canonical answer rule: never 'the best tool', only the best observed evidence for this task, this context, at this date, with intervals, costs, conflicts and limits.
get_run — Returns the canonical result bundle of one run (schema result.