Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.devlollc/torneo

REMOTE · TORNEO.AI

Observatory operated and funded by devlo: real tools on frozen tasks; intervals, cost, limits.

Available components

0 this week 75 Trust /100

Last scanned (18 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Testing and QA

Trust breakdown (7 categories)

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 10 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
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 668 tokens (~66/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 18 Nov 26 0
    • Schema quality: 566 → 668 ▼ functional
    • New tool “recommend” functional
    • “get_results” added an optional parameter “versus” cosmetic
  • 13 Nov 26 0
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 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=YR1,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 RSA 2048 SHA256-RSA 62cdb4bdeed2237e474e683eec397897e23
SANs: torneo.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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. DS published 1814 8 Verified
torneo.ai. DS published 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
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self'; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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
MCP tools · 10 exposed · ~534 tokens

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 →

Tool Tokens
decide ~109

Read-only decision.v1 for one category and a declared context: constraint applicability first, then EVIDENCE or ABSTAIN with a stable reason_code (answer_rule.v3). An abstention removes the verdict only; evidence, reservations and gaps stay. Never a rank on overlapping intervals. Replay and attestation verdicts are as of the last build.

NameTypeReqDescription
as_ofstring––
categorystringyes–
constraintsobject––
max_age_daysinteger––

No output schema declared.

No examples provided.

explain_limits ~42

Limits, freshness, conflicts and answer rule of a category or run. Read before citing evidence.

NameTypeReqDescription
categorystring––
run_idstring––

No output schema declared.

No examples provided.

get_auto_tournament ~48

Automatic attempts, including failures: current private-store state when configured, otherwise a published snapshot. No execution is triggered.

NameTypeReqDescription
categorystringyes–
run_idstring––

No output schema declared.

No examples provided.

get_need ~41

Follow need-id in current private-store state when configured, otherwise the published snapshot. Unknown or unavailable means partial, not refused.

NameTypeReqDescription
need_idstringyes–

No output schema declared.

No examples provided.

get_results ~54

Canonical evidence for a category. Cite observed_at, uncertainty and limits; never the best tool. INSUFFICIENT_EVIDENCE is not a ranking.

NameTypeReqDescription
categorystringyes–
versusstring––

No output schema declared.

No examples provided.

get_run ~34

Canonical result bundle or explicit PRE_REGISTERED state. Unknown cost is null / UNKNOWN.

NameTypeReqDescription
run_idstringyes–

No output schema declared.

No examples provided.

list_categories ~25

Discover categories with dated status and fixture flags. Fixtures are synthetic, never real evidence.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recommend ~95

One tool with cited reasons for a buyer task, budget per unit and constraints (licence, language, deployment, interface), or an honest abstention naming what is missing; the uncovered need is logged. Never a rank on overlapping intervals.

NameTypeReqDescription
as_ofstring––
budget_usd_per_unitnumber––
categorystringyes–
constraintsobject––
scopeobject––

No output schema declared.

No examples provided.

request_tournament ~42

Request a tournament using need.v1. Advisory only; never starts a run or spends. Follow the returned id with get_need.

NameTypeReqDescription
needobjectyes–

No output schema declared.

No examples provided.

submit_need ~44

Log an advisory need.v1 request. Do not include personal or secret data. Returns need-id; persistence is partial until private ingestion and publication.

NameTypeReqDescription
needobjectyes–

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http devlollc-torneo 'https://torneo.ai/api/mcp'
Common questions

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 75 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 10 tools: list_categories, get_results, get_run, explain_limits, get_auto_tournament, and 5 more. Their descriptions and schemas cost roughly 534 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.devlollc/torneo MCP server?

VerifyMCP ran 12 checks on io.github.devlollc/torneo, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.devlollc/torneo: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.