MCP servers observed by Lowdown
cl.tordo/mercado-publico MCP server: daily status and tool changes
No successful response on the last 4 consecutive daily checks (2026-11-15 to 2026-11-18). Checked from one network location. 4 of 30 observed days in the last 30 had this result. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-19; tool definitions last changed on 2026-10-23 after 2 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cl.tordo/mercado-publico
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cl.tordo/mercado-publico?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server did not respond.
- Observed days in the last 30: 30
- Answered initialize and tools/list: 26
- Required authentication: 0
- No response: 4
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 30 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 26 compared days.
- 2026-10-23: descriptions changed
- 2026-10-21: input or output schemas changed
What tools does it list?
4 tools on 2026-11-14:
buscar_productospanel_de_licitacionperfil_de_compradorprecio_de_producto
MCP Registry declaration
- Registry name:
cl.tordo/mercado-publico - Declared version: 1.1.0
- Status: active
- Declared hosts:
api.tordo.cl
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:cl.tordo/mercado-publico", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cl.tordo/mercado-publico?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).