Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.francofuji/cemis-directorio

REMOTE · MCP.CEMIS.IO

Directorio de empresas cubanas, oportunidades de negocio y reformas económicas 2026 (cemis.io)

Available components

0 this week 76 Trust /100

Last scanned (14 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1410 tokens (~176/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage67
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +58
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 18 Nov 26 −58
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 24 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 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 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA256 111f1eaa1babf62e0ee82d0395e6c60a
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. DS published 38690 8 Verified
cemis.io. No DS 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.cemis.io/mcp Verified 200
http (plaintext) http://mcp.cemis.io/mcp Inconclusive 406
MCP tools · 8 exposed · ~1,320 tokens

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 →

Tool Tokens
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).

NameTypeReqDescription
limiteinteger––
objetivo–––
provincia–––
sector–––
verificada–––

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
oportunidadstringyes–

No output schema declared.

No examples provided.

empresas_tecnologicas ~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.

NameTypeReqDescription
limiteinteger––

No output schema declared.

No examples provided.

ficha_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.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

impacto_de_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).

NameTypeReqDescription
transformacionstringyes–

No output schema declared.

No examples provided.

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 ~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 ~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.

NameTypeReqDescription
sectorstringyes–

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http francofuji-cemis-directorio 'https://mcp.cemis.io/mcp'
Common questions

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 76 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.francofuji/cemis-directorio MCP server?

VerifyMCP ran 12 checks on io.github.francofuji/cemis-directorio, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.francofuji/cemis-directorio: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.