CIGAM vs MCP AEMPS — CIMA
CIGAM is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). MCP AEMPS — CIMA is an MCP server published by romanpert. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  CIGAM |   MCP AEMPS — CIMA |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.5.0 Downloads/month (PyPI): 203 Downloads/week (PyPI): 47 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | CIGAM | MCP AEMPS — CIMA |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.mcp.ai/p_cigam) | On your machine (mcp-aemps) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mcp-dir/cigam-mcp | github.com/romanpert/mcp-aemps |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 33 h ago returned HTTP 406 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
CIGAM
CIGAM ERP (management for industry, retail and franchises) via session capture with your authorizati
MCP AEMPS — CIMA
MCP server for the Spanish AEMPS CIMA pharmaceutical registry (20,000+ authorised medicines).
How to run each
CIGAM As a remote MCP server
claude mcp add --transport http cigam-mcp https://api.mcp.ai/p_cigamMCP AEMPS — CIMA
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only CIGAM has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of MCP AEMPS — CIMA nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of CIGAM publish no settings it asks for, so we do not compare settings.
What it can do: CIGAM · What it can do: MCP AEMPS — CIMA · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.