Conexcol — catálogo de hosting y servidores cloud en Colombia
co.net.conexcol.mcp/hosting-cloud-colombia · 0.1.0
Catálogo vivo de hosting y servidores cloud en Colombia. Precios en pesos, con fecha de lectura.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.conexcol.net.co/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 10 tools.
- Protocol
- 2025-06-18
- Calls itself
- conexcol 0.1.0
- Handshake time
- 327 ms
- HTTP status
- 200
The tools it lists (10, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_productsBusca 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 clie
get_productFicha 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` ex
compare_productsCompara 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.
quoteCotiza 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.
create_draft_order
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
co.net.conexcol.mcp/hosting-cloud-colombia, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 36 days ago. The registry entry · conexcol.net.co