io.github.devlollc/torneo
REMOTE · TORNEO.AI · SCANNED SEP 24
Observatory operated and funded by devlo: real tools on frozen tasks; intervals, cost, limits.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 530 tokens (~132/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.devlollc/torneo MCP server?
io.github.devlollc/torneo is a hosted endpoint at https://torneo.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · torneo.ai
claude mcp add --transport http devlollc-torneo 'https://torneo.ai/api/mcp'
{
"mcpServers": {
"devlollc-torneo": {
"url": "https://torneo.ai/api/mcp"
}
}
} {
"servers": {
"devlollc-torneo": {
"type": "http",
"url": "https://torneo.ai/api/mcp"
}
}
} [mcp_servers.devlollc-torneo] url = "https://torneo.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"devlollc-torneo": {
"type": "remote",
"url": "https://torneo.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add devlollc-torneo --url 'https://torneo.ai/api/mcp' --transport streamable-http
mcp_servers:
devlollc-torneo:
url: "https://torneo.ai/api/mcp" {
"McpServers": {
"devlollc-torneo": {
"Transport": "http",
"Url": "https://torneo.ai/api/mcp"
}
}
} assistant mcp add devlollc-torneo -t streamable-http -u 'https://torneo.ai/api/mcp'
{
"mcpServers": {
"devlollc-torneo": {
"type": "http",
"url": "https://torneo.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 0
- Tool “get_results” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://torneo.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=torneo.ai | CN=YR2,O=Let's Encrypt,C=US | 2 Sept 2026 | 1 Dec 2026 | RSA 2048 | SHA256-RSA | 69e6f12475758d41e5082458cdacf11e792 |
| SANs: torneo.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of torneo.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| torneo.ai. | present | 46360 | 13 | Verified |
| torneo.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://torneo.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://torneo.ai/api/mcp | HTTPS enforced | 308 | https://torneo.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_limits Explain the limits of a result ~100
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, published errata (each chained to the served result hash), the legal preflight verdict per tool including tools not run, and the answer rule every consumer must follow.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category id |
| run_id | string | – | Run id (alternative to category) |
No output schema declared.
No examples provided.
get_results Query the evidence for a category ~114
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. On a STALE, SUPERSEDED or INDETERMINATE result the answer is INSUFFICIENT_EVIDENCE and carries no rank. Identical to `torneo query <category>` on the CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category id, e.g. 'transcription' (see list_categories) |
No output schema declared.
No examples provided.
get_run Get a run bundle ~113
Returns the canonical result bundle of one run (schema result.v1): protocol lock hash, provenance, reproduce command, per-participant outcomes with intervals. A PRE-REGISTERED run, whose protocol is frozen and timestamped but which has not been executed, returns state PRE_REGISTERED with measured false, its lock and its frozen files, and no result: nothing has been measured yet.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | Run id, e.g. 'TRANSCRIPTION-001' (see list_categories, field run_id) |
No output schema declared.
No examples provided.
list_categories List categories ~72
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. Categories prefixed 'fixture-' are synthetic demo data validating the machinery, never evidence about real tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.devlollc/torneo MCP server?
io.github.devlollc/torneo is an MCP server listed in the public MCP registry as io.github.devlollc/torneo. Observatory operated and funded by devlo: real tools on frozen tasks; intervals, cost, limits. This page covers its hosted endpoint (https://torneo.ai/api/mcp).
Is the io.github.devlollc/torneo MCP server safe to use?
io.github.devlollc/torneo scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.devlollc/torneo MCP server expose?
io.github.devlollc/torneo exposes 4 tools: list_categories, get_results, get_run, explain_limits. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.
Does the io.github.devlollc/torneo MCP server require authentication?
No. We connected to io.github.devlollc/torneo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.devlollc/torneo MCP server still maintained?
io.github.devlollc/torneo is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.