io.github.francofuji/cemis-directorio
REMOTE · MCP.CEMIS.IO · SCANNED SEP 23
Directorio de empresas cubanas, oportunidades de negocio y reformas económicas 2026 (cemis.io)
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 Security46
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.francofuji/cemis-directorio MCP server?
io.github.francofuji/cemis-directorio is a hosted endpoint at https://mcp.cemis.io/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.cemis.io
claude mcp add --transport http francofuji-cemis-directorio 'https://mcp.cemis.io/mcp'
{
"mcpServers": {
"francofuji-cemis-directorio": {
"url": "https://mcp.cemis.io/mcp"
}
}
} {
"servers": {
"francofuji-cemis-directorio": {
"type": "http",
"url": "https://mcp.cemis.io/mcp"
}
}
} [mcp_servers.francofuji-cemis-directorio] url = "https://mcp.cemis.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"francofuji-cemis-directorio": {
"type": "remote",
"url": "https://mcp.cemis.io/mcp",
"enabled": true
}
}
} openclaw mcp add francofuji-cemis-directorio --url 'https://mcp.cemis.io/mcp' --transport streamable-http
mcp_servers:
francofuji-cemis-directorio:
url: "https://mcp.cemis.io/mcp" {
"McpServers": {
"francofuji-cemis-directorio": {
"Transport": "http",
"Url": "https://mcp.cemis.io/mcp"
}
}
} assistant mcp add francofuji-cemis-directorio -t streamable-http -u 'https://mcp.cemis.io/mcp'
{
"mcpServers": {
"francofuji-cemis-directorio": {
"type": "http",
"url": "https://mcp.cemis.io/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.
- 23 Sept 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 22 Sept 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 0
- Schema quality: 1219 → 1410 ▼ functional
- Schema quality: excellent → good functional
- New tool “empresas_tecnologicas” functional
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 23 Sept 2026 · Probed https://mcp.cemis.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cemis.io | CN=WE1,O=Google Trust Services,C=US | 25 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 30d6bf8027c709eb0e5e14f420cb35d8 |
| SANs: cemis.io, *.cemis.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cemis.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| cemis.io. | 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 | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cemis.io/mcp | HTTP error | 530 | |
| http (plaintext) | http://mcp.cemis.io/mcp | Inconclusive | 530 |
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_empresas Buscar empresas ~280
Busca empresas del directorio CEMIS combinando filtros con AND. Todos son opcionales. - sector: uno de los valores devueltos por listar_sectores(), o un sector de la taxonomía de matching de reformas (ver impacto_de_reforma()) que todavía no tiene ninguna empresa asignada — en ese caso el resultado es una lista vacía con una nota explicativa, no un error. - provincia: una de las 16 provincias cubanas (ver listar_provincias()). - objetivo: coincidencia parcial contra 'que_busca' de la empresa (ej. 'inversión', 'socio estratégico', 'distribuidor', 'exportar'). - verificada: True para empresas con datos de contacto verificados, False para no verificadas, None (default) para no filtrar. - limite: máximo de resultados a devolver (default 50); el total real de matches siempre se informa en 'total_encontrado' aunque exceda el límite. Devuelve una ficha resumida por empresa, no el perfil completo (usá ficha_empresa() para eso).
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | – |
| objetivo | – | – | – |
| provincia | – | – | – |
| sector | – | – | – |
| verificada | – | – | – |
No output schema declared.
No examples provided.
empresas_por_oportunidad Empresas por oportunidad ~95
Dado un id (ej. 'opp-001') o título (exacto o aproximado) de una oportunidad de negocio, devuelve las empresas del directorio CEMIS relacionadas: primero las curadas a mano dentro de la propia oportunidad, luego las encontradas automáticamente porque su sector matchea por palabra clave con el texto de la oportunidad.
| Name | Type | Req | Description |
|---|---|---|---|
| oportunidad | string | yes | – |
No output schema declared.
No examples provided.
empresas_tecnologicas Empresas tecnológicas ~191
Devuelve las empresas cubanas del sector 'TICs y economía digital' (desarrollo de software, soluciones informáticas, TI y telemática) — el mismo dataset que arma el hub público /empresas-tecnologicas-cuba/ de cemis.io. A diferencia de buscar_empresas(sector="TICs y economía digital"), esta tool también cruza el sector con las reformas del Eje 21 (ámbito digital, IA y economía del conocimiento) y las oportunidades de negocio asociadas a esas reformas — el mismo cruce regulatorio que distingue al hub de un directorio plano. limite: máximo de empresas a devolver en 'empresas' (default 50); el total real siempre está en 'total' aunque exceda el límite.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | – |
No output schema declared.
No examples provided.
ficha_empresa Ficha de empresa ~85
Devuelve el perfil estructurado completo de una empresa del directorio CEMIS, identificada por su slug (o por nombre exacto/aproximado si no sabés el slug), incluyendo sus oportunidades de negocio relacionadas y las transformaciones/reformas que la afectan. Si no se encuentra, devuelve sugerencias aproximadas.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
impacto_de_reforma Impacto de una reforma ~376
Herramienta principal: dado el número o título (exacto o aproximado) de una transformación/reforma de 2026, devuelve su impacto sobre el directorio CEMIS. El criterio de impacto varía según la naturaleza de la reforma (ver ambito_transformaciones.py, curado a mano transformación por transformación): - Reformas cuyo alcance real es un TIPO de empresa (estatal/no estatal/ inversión extranjera/cooperativa) matchean por tipo, no por sector, y el resultado lo indica con "criterio_de_impacto": "tipo_de_empresa". - Reformas TRANSVERSALES (fiscales/cambiarias/laborales de alcance nacional, o que explícitamente aplican a "todos los actores económicos") devuelven "alcance": "transversal" con la metadata de la reforma, sin enumerar las 252 empresas del directorio (no aporta valor). - Reformas que NO APLICAN a un actor económico del directorio (reforma de aparato de gobierno, política social para personas, deuda soberana) lo dicen explícitamente en vez de devolver un array vacío sin explicación. - El resto matchea por SECTOR de industria vía EMPRESA_SECTOR_KEYWORDS (mismo criterio que cemis.io, con el fix de normalización de acentos de 2026-08-23 — antes "turis" no matcheaba "turística"). En todos los casos incluye oportunidades_directas (vínculo curado transformacion_num) y el estado de implementación regulatoria si está disponible (ver monitor de reformas de cemis.io).
| Name | Type | Req | Description |
|---|---|---|---|
| transformacion | string | yes | – |
No output schema declared.
No examples provided.
listar_provincias Listar provincias ~49
Devuelve las provincias válidas para filtrar empresas, derivadas de los datos reales del directorio. Usalo antes de llamar a buscar_empresas() con un filtro de provincia.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
listar_sectores Listar sectores ~67
Devuelve los sectores válidos para filtrar empresas, derivados de los datos reales del directorio (no del formulario web, que puede estar desactualizado). Usalo antes de llamar a buscar_empresas() u oportunidades_por_sector() con un filtro de sector.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
oportunidades_por_sector Oportunidades por sector ~177
Dado un sector (ver listar_sectores(), o un sector de la taxonomía de matching de reformas que todavía no tiene empresas asignadas — ver impacto_de_reforma()), devuelve las oportunidades de negocio relevantes: primero las curadas a mano (vinculadas directamente a alguna empresa de ese sector), luego las encontradas automáticamente por coincidencia de palabras clave de sector (mismo criterio que usa cemis.io). Si el sector no tiene empresas asignadas hoy, 'oportunidades_curadas' sale vacía (no puede haber curadas sin empresas) pero las automáticas por keyword sí pueden aparecer, porque esas se buscan directamente en el texto de las oportunidades/transformaciones, no a través de las empresas.
| Name | Type | Req | Description |
|---|---|---|---|
| sector | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.francofuji/cemis-directorio MCP server?
io.github.francofuji/cemis-directorio is an MCP server listed in the public MCP registry as io.github.francofuji/cemis-directorio. Directorio de empresas cubanas, oportunidades de negocio y reformas económicas 2026 (cemis.io). This page covers its hosted endpoint (https://mcp.cemis.io/mcp).
Is the io.github.francofuji/cemis-directorio MCP server safe to use?
io.github.francofuji/cemis-directorio scores 18 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.francofuji/cemis-directorio MCP server expose?
io.github.francofuji/cemis-directorio exposes 8 tools: listar_sectores, listar_provincias, buscar_empresas, empresas_tecnologicas, ficha_empresa, and 3 more. Their descriptions and schemas cost roughly 1,320 tokens of context every time the server is loaded.
Does the io.github.francofuji/cemis-directorio MCP server require authentication?
No. We connected to io.github.francofuji/cemis-directorio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.francofuji/cemis-directorio MCP server still maintained?
io.github.francofuji/cemis-directorio is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.