dev.latamref/reference-data vs MéxicoAPI
dev.latamref/reference-data is an MCP server published by latamref.dev. Marketplaces we read that list it: 1 (Official MCP Registry). MéxicoAPI is an MCP server published by Dagel4k. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  MéxicoAPI | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.5.0 No figure published Not marked · First seen |
Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | dev.latamref/reference-data | MéxicoAPI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (latamref.dev/mcp) | On your machine (mexicoapi-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/dagel4k/mexicoapi |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
| Endpoint at the last check (differs) | Not responding since 2026-10-26 | 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
dev.latamref/reference-data
LatAm govt data, cited to source: rates, VAT, tax, wages, holidays, FX. 22 countries; Brazil free.
MéxicoAPI
Datos oficiales de México: FIX, UDIS, días hábiles, UMA, ISR, municipios, CLABE, RFC, CURP y NSS.
How to run each
dev.latamref/reference-data As a remote MCP server
claude mcp add --transport http reference-data https://latamref.dev/mcpMéxicoAPI As a local MCP server: npm package
claude mcp add --transport stdio mexicoapi-mcp -- npx -y mexicoapi-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only dev.latamref/reference-data has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of dev.latamref/reference-data publish no settings it asks for, so we do not compare settings.
What it can do: dev.latamref/reference-data · What it can do: MéxicoAPI · 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.