TORDO — Mercado Público de Chile
REMOTE · API.TORDO.CL
Licitaciones, precios históricos, competidores y compradores de Mercado Público (Chile). Sin clave.
Available components
Last scanned (23 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 24 Oct 2026.
Category E-commerce
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 Security57
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 476 tokens (~119/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
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 Oct 26 +1
- Tool “buscar_productos” rewrote its description, which is the text the model reads security
- Schema quality: 108 → 119 ▼ functional
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 60
First indexed and scored.
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 Oct 2026 · Probed https://api.tordo.cl/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.tordo.cl | CN=YE2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 69bfa7d8e71cb0724c00781a0323cce6f3b |
| SANs: api.tordo.cl | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.tordo.cl. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cl. | present | 21199 | 8 | Verified |
| tordo.cl. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.tordo.cl/mcp/ | Verified | 200 | |
| http (plaintext) | http://api.tordo.cl/mcp/ | HTTPS enforced | 301 | https://api.tordo.cl/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 →
buscar_productos Buscar productos por nombre ~130
Encuentra el código ONU de un producto a partir de su nombre. Es el paso previo a `precio_de_producto`: el catálogo usa códigos, y el usuario habla de «guantes» o «papel». Busca por palabras, en cualquier orden y con sus plurales y algunos sinónimos («lápiz» también trae «bolígrafo»; «pc», computadores): no hace falta probar variantes. Devuelve cuántas transacciones tiene cada uno, que es lo que indica si el precio será fiable.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | – |
| texto | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
panel_de_licitacion Panel de una licitación ~84
Todo lo que hace falta para decidir si postular a una licitación, en una sola llamada: perfil del comprador, si la ventana de preparación es holgada o apretada, los competidores habituales, y las bandas de precio de sus productos con su confianza. Úsala en vez de encadenar varias herramientas.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
perfil_de_comprador Perfil de un comprador ~65
Cómo se comporta un organismo público: qué tan transparente es su historial, cuánto de lo que llama termina adjudicando y sus señales de riesgo. Sirve para decidir si conviene trabajar con él antes de mirar el precio.
| Name | Type | Req | Description |
|---|---|---|---|
| organismo_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
precio_de_producto Precio de referencia de un producto ~81
Bandas de precio históricas de un producto (código ONU): percentiles 10 a 90, con el nivel de datos usado, la confianza y el tamaño de muestra. Si se indica organismo, usa sus datos y sólo cae al sector o al país cuando no tiene suficientes.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo_producto | string | yes | – |
| organismo_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the TORDO — Mercado Público de Chile MCP server?
TORDO — Mercado Público de Chile is a hosted endpoint at https://api.tordo.cl/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 · api.tordo.cl
claude mcp add --transport http cl-tordo-mercado-publico 'https://api.tordo.cl/mcp/'
What is the TORDO — Mercado Público de Chile MCP server?
TORDO — Mercado Público de Chile is an MCP server listed in the public MCP registry as cl.tordo/mercado-publico. Licitaciones, precios históricos, competidores y compradores de Mercado Público (Chile). Sin clave. This page covers its hosted endpoint (https://api.tordo.cl/mcp/).
Is the TORDO — Mercado Público de Chile MCP server safe to use?
TORDO — Mercado Público de Chile scores 64 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 TORDO — Mercado Público de Chile MCP server expose?
TORDO — Mercado Público de Chile exposes 4 tools: panel_de_licitacion, precio_de_producto, perfil_de_comprador, buscar_productos. Their descriptions and schemas cost roughly 360 tokens of context every time the server is loaded.
Does the TORDO — Mercado Público de Chile MCP server require authentication?
No. We connected to TORDO — Mercado Público de Chile without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TORDO — Mercado Público de Chile MCP server still maintained?
TORDO — Mercado Público de Chile is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.