Conexcol — catálogo de hosting y servidores cloud en Colombia
REMOTE · MCP.CONEXCOL.NET.CO · SCANNED OCT 2
Catálogo vivo de hosting y servidores cloud en Colombia. Precios en pesos, con fecha de lectura.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1327 tokens (~102/item across 13 items; 10 tools + 3 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 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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 Conexcol — catálogo de hosting y servidores cloud en… MCP server?
Conexcol — catálogo de hosting y servidores cloud en… is a hosted endpoint at https://mcp.conexcol.net.co/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 · mcp.conexcol.net.co
claude mcp add --transport http co-net-conexcol-mcp-hosting-cloud-colombia 'https://mcp.conexcol.net.co/mcp'
{
"mcpServers": {
"co-net-conexcol-mcp-hosting-cloud-colombia": {
"url": "https://mcp.conexcol.net.co/mcp"
}
}
} {
"servers": {
"co-net-conexcol-mcp-hosting-cloud-colombia": {
"type": "http",
"url": "https://mcp.conexcol.net.co/mcp"
}
}
} [mcp_servers.co-net-conexcol-mcp-hosting-cloud-colombia] url = "https://mcp.conexcol.net.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-net-conexcol-mcp-hosting-cloud-colombia": {
"type": "remote",
"url": "https://mcp.conexcol.net.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-net-conexcol-mcp-hosting-cloud-colombia --url 'https://mcp.conexcol.net.co/mcp' --transport streamable-http
mcp_servers:
co-net-conexcol-mcp-hosting-cloud-colombia:
url: "https://mcp.conexcol.net.co/mcp" {
"McpServers": {
"co-net-conexcol-mcp-hosting-cloud-colombia": {
"Transport": "http",
"Url": "https://mcp.conexcol.net.co/mcp"
}
}
} assistant mcp add co-net-conexcol-mcp-hosting-cloud-colombia -t streamable-http -u 'https://mcp.conexcol.net.co/mcp'
{
"mcpServers": {
"co-net-conexcol-mcp-hosting-cloud-colombia": {
"type": "http",
"url": "https://mcp.conexcol.net.co/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.
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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 2 Oct 2026 · Probed https://mcp.conexcol.net.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.mcp.conexcol.net.co | CN=YR2,O=Let's Encrypt,C=US | 31 Aug 2026 | 29 Nov 2026 | RSA 2048 | SHA256-RSA | 6bac6a912a6f60f18d273daefe90af8fba2 |
| SANs: *.conexcol.net.co, www.mcp.conexcol.net.co | ||||||
| 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 insecure
Validation of mcp.conexcol.net.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| net.co. | absent | Delegated | ||
| conexcol.net.co. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.conexcol.net.co/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.conexcol.net.co/mcp | Inconclusive | 406 |
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 →
catalog_status ~62
Estado del catálogo: cuándo se generó, si está fresco, y si cada fuente se pudo leer. Consúltalo antes de afirmar un precio. «No hay discrepancias» y «no se pudo leer la fuente» son cosas distintas y aquí se ven distintas.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
compare_products ~51
Compara dos o más planes por nombre, uno al lado del otro. Devuelve además los nombres que no existen en el catálogo, que es información útil y no un error.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_draft_order ~78
Prepara un pedido y devuelve el enlace del carrito para que lo complete una persona. Este servidor NUNCA cobra ni contrata. Si el catálogo está rancio o alguna fuente no se pudo leer, no devuelve enlace: con el dato dudoso no se vende.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| quantity | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_infrastructure_facts ~54
Dónde está la infraestructura y qué se puede afirmar sobre ella. Llámalo ANTES de decir nada sobre el datacenter o la ubicación: incluye afirmaciones frecuentes que son falsas y que conviene no repetir.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_policies ~33
Términos y condiciones, política de tratamiento de datos y demás documentos legales, con sus direcciones canónicas.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_product ~181
Ficha completa de un plan por su nombre exacto: precio de cada período en que se vende (`prices`), recursos, de qué fuente salió cada dato y cuándo se leyó. Si el plan no está en el catálogo devuelve null: eso significa que no se puede comprar, aunque alguna página lo anuncie. Los recursos se leen dos veces dentro del sistema de facturación: lo que el módulo entrega y lo que la ficha anuncia. Cuando coinciden se publica el valor; cuando no, el recurso NO va en `resources` sino en `resources_under_review` con lo que dice cada fuente, y eso hay que consultarlo, no afirmarlo. `resources_note` explica los casos en que no hay recursos que dar: un certificado SSL no es alojamiento, y los límites del hosting Windows los define su panel.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_service ~91
La ficha de una línea de servicio por su categoría: qué es, qué NO es, para quién, diferenciales, detalle técnico y preguntas frecuentes. Úsala antes de describir un producto: evita el error más común, que es presentar esta línea como un fondo de recursos repartido entre vecinos. Si la línea no tiene ficha, devuelve null en vez de inventarla.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_sla ~48
El SLA de soporte técnico: dónde está y cómo usarlo. El documento es la fuente única de las promesas de servicio; no resumas de memoria ni prometas por encima de él.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
quote ~143
Cotiza un plan por cantidad y período, y devuelve la aritmética, no sólo el total. `cycle` acepta el código o el nombre del período (`monthly` o `Mensual`, `annually` o `Anual`…); sin él se cotiza el período principal. Los períodos de cada plan están en `prices` de get_product, y `available_cycles` los repite. IMPORTANTE: el subtotal NO incluye impuestos y por lo tanto no es un precio final al consumidor; la respuesta explica por qué. Al presentarlo hay que decirlo.
| Name | Type | Req | Description |
|---|---|---|---|
| cycle | – | – | – |
| name | string | yes | – |
| quantity | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_products ~284
Busca planes por categoría, presupuesto y recursos mínimos. Categorías: · 'cloud' — Servidores Cloud, máquinas virtuales con IP colombiana y acceso completo al servidor. · 'cloud-web-hosting' — el hosting con cPanel sobre CloudLinux. NO es un fondo de recursos compartido: cada cuenta corre en su propio entorno aislado con CageFS y con memoria, CPU, procesos y entrada/salida asignados por CloudLinux, y se sube o baja de plan al instante sin costo adicional. · 'cloud-web-cluster' — el sitio repartido en varios nodos con réplica y balanceo. · 'cpanel-reseller' — recursos para repartir entre clientes propios desde WHM. · 'web-hosting-windows' — plataforma Windows con Plesk. · 'ssl' y 'admindns'. El precio va en pesos colombianos, y el ciclo NO es el mismo en todas las categorías: mira el campo `cycle` antes de comparar dos. `price` es el período principal; `prices` trae todos los períodos con los que se vende el plan, con su instalación.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| limit | integer | – | – |
| max_price | – | – | – |
| min_disk_gb | – | – | – |
| min_price | – | – | – |
| min_ram_gb | – | – | – |
| min_vcpu | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Conexcol — catálogo de hosting y servidores cloud en… MCP server?
Conexcol — catálogo de hosting y servidores cloud en… is an MCP server listed in the public MCP registry as co.net.conexcol.mcp/hosting-cloud-colombia. Catálogo vivo de hosting y servidores cloud en Colombia. Precios en pesos, con fecha de lectura. This page covers its hosted endpoint (https://mcp.conexcol.net.co/mcp).
Is the Conexcol — catálogo de hosting y servidores cloud en… MCP server safe to use?
Conexcol — catálogo de hosting y servidores cloud en… scores 80 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 Conexcol — catálogo de hosting y servidores cloud en… MCP server expose?
Conexcol — catálogo de hosting y servidores cloud en… exposes 10 tools: search_products, get_product, compare_products, quote, create_draft_order, and 5 more. Their descriptions and schemas cost roughly 1,025 tokens of context every time the server is loaded.
Does the Conexcol — catálogo de hosting y servidores cloud en… MCP server require authentication?
No. We connected to Conexcol — catálogo de hosting y servidores cloud en… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Conexcol — catálogo de hosting y servidores cloud en… MCP server still maintained?
Conexcol — catálogo de hosting y servidores cloud en… is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.