dev.latamref/reference-data
REMOTE · LATAMREF.DEV · SCANNED SEP 22
LatAm govt data, cited to source: rates, VAT, tax, wages, holidays, FX. 22 countries; Brazil free.
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 Security66
- 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 call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1882 tokens (~171/item across 11 items; 11 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the dev.latamref/reference-data MCP server?
dev.latamref/reference-data is a hosted endpoint at https://latamref.dev/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 · latamref.dev
claude mcp add --transport http dev-latamref-reference-data 'https://latamref.dev/mcp'
{
"mcpServers": {
"dev-latamref-reference-data": {
"url": "https://latamref.dev/mcp"
}
}
} {
"servers": {
"dev-latamref-reference-data": {
"type": "http",
"url": "https://latamref.dev/mcp"
}
}
} [mcp_servers.dev-latamref-reference-data] url = "https://latamref.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-latamref-reference-data": {
"type": "remote",
"url": "https://latamref.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-latamref-reference-data --url 'https://latamref.dev/mcp' --transport streamable-http
mcp_servers:
dev-latamref-reference-data:
url: "https://latamref.dev/mcp" {
"McpServers": {
"dev-latamref-reference-data": {
"Transport": "http",
"Url": "https://latamref.dev/mcp"
}
}
} assistant mcp add dev-latamref-reference-data -t streamable-http -u 'https://latamref.dev/mcp'
{
"mcpServers": {
"dev-latamref-reference-data": {
"type": "http",
"url": "https://latamref.dev/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.
- 9 Sept 26 0
- Schema quality: 1601 → 1882 ▼ functional
- New tool “compute_employment_cost” functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 5 Aug 26 0
- Tool “get_series” rewrote its description, which is the text the model reads security
- Tool “get_series_history” rewrote its description, which is the text the model reads security
- 31 Jul 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
- 30 Jul 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
- 29 Jul 26 0
- Tool “get_public_holidays” rewrote its description, which is the text the model reads security
- Schema quality: 143 → 160 ▼ functional
- “count_working_days” added an optional parameter “subdivision” cosmetic
- “get_public_holidays” added an optional parameter “subdivision” cosmetic
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 22 Sept 2026 · Probed https://latamref.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=latamref.dev | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | dea7aea9113b758d0e26548466b2694c |
| SANs: latamref.dev, *.latamref.dev | ||||||
| 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 secure
Validation of latamref.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| latamref.dev. | present | 2371 | 13 | Verified |
| latamref.dev. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'sha256-0a4k/mJay1Co+D+vZyb5cMckFOjwRMRtlIMeCpvYTJs=' 'sha256-YKIIFQ+OmjnSJ//KnYATbJ3E791wXyOSxVW+lCuGoY0=' https://cdn.paddle.com https://*.paddle.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.paddle.com; connect-src 'self' https://*.paddle.com; frame-src https://*.paddle.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self' https://*.paddle.com; report-uri /csp-report; report-to csp |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self "https://buy.paddle.com"), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://latamref.dev/mcp | Verified | 200 | |
| http (plaintext) | http://latamref.dev/mcp | HTTPS enforced | 301 | https://latamref.dev:443/mcp |
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 →
check_minimum_wage ~162
PAID ($0.05). Compliance verdict: is a salary at, above or below the country's statutory minimum wage? Returns verdict, margin, the statutory floor and the legal instrument it rests on. Honest statuses when no enforceable floor exists or the period doesn't match the floor's period (cross-period conversion is never guessed). Pass api_key if you have one; otherwise the response explains how to pay via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Wage to check, in the country's own currency |
| api_key | string | – | API key (bypasses x402; metered for invoicing) |
| country | string | yes | ISO country code |
| period | string | yes | Period the amount covers — must match the statutory floor's period |
No output schema declared.
No examples provided.
compute_employment_cost ~281
PAID ($0.10). Cost to employ: prices every statutory contribution on both the employee and employer sides for a gross salary, returning line-by-line amounts with instrument citations and an explicit refused list for schemes that could not be priced (unknown, not zero). Does NOT compute income tax — use compute_payroll for gross-to-net take-home where supported. Pass api_key if you have one; otherwise the response explains how to pay via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (bypasses x402; metered for invoicing) |
| childless_over_23 | boolean | – | Germany care surcharge |
| children_under_25 | number | – | Germany per-child care reduction |
| contract | string | – | Contract type where rates differ |
| country | string | yes | ISO country code with a costed contribution schedule |
| gross | number | yes | Gross pay in local currency |
| nationality | string | – | Gulf nationality for pension reach |
| period | string | – | Period the gross covers (default month) |
| subdivision | string | – | Optional ISO 3166-2 regional schedule (e.g. CA-QC, DE-SN) |
| workplace_pension | boolean | – | Auto-enrolment / PPK participation (default true) |
| zusatzbeitrag_rate | number | – | Germany sickness-fund supplement |
No output schema declared.
No examples provided.
compute_income_tax ~210
PAID ($0.05). Statutory income tax on a TAXABLE-income figure using the country's verified marginal bracket schedule, with full per-bracket workings, effective rate and marginal rate. Handles inflation-indexed tax units (Colombia UVT, Chile UTA, Peru UIT, Uruguay BPC) — you pass local currency. IMPORTANT: this is tax on taxable income, NOT net take-home pay — reliefs/allowances and social-security contributions are the caller's concern and are not applied (see the response scope_note). Pass api_key if you have one; otherwise the response explains how to pay via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (bypasses x402; metered for invoicing) |
| country | string | yes | ISO country code |
| taxable_income | number | yes | Taxable income in the country's local currency, in the schedule's own period basis (annual for most; monthly for Côte d'Ivoire, Uganda, Ethiopia, Costa Rica) |
No output schema declared.
No examples provided.
compute_vat ~150
PAID ($0.02). VAT breakdown for an amount: net, tax and gross using the country's current statutory rate, including per-levy components where the rate is composite (e.g. Ghana VAT + NHIL + GETFund). mode=add treats the amount as net; mode=extract backs VAT out of a gross amount. Pass api_key if you have one; otherwise the response explains how to pay via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in the country's own currency |
| api_key | string | – | API key |
| country | string | yes | ISO country code |
| mode | string | – | add = amount is net (default); extract = amount is gross |
No output schema declared.
No examples provided.
count_working_days ~194
PAID ($0.02). Working days in a date range for a country: weekends (Egypt's Fri–Sat handled) and statutory public holidays applied, with the holidays hit by name and the next working day after the range. Range max 366 days. Pass api_key if you have one; otherwise the response explains how to pay via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key |
| country | string | yes | ISO country code |
| from | string | yes | Range start, YYYY-MM-DD, inclusive |
| subdivision | string | – | Optional ISO 3166-2 region code (e.g. 'DE-BY') to apply that region's statutory holidays on top of the national calendar. Regions are listed under `subdivisions` by get_public_holidays. Unknown code… |
| to | string | yes | Range end, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
get_public_holidays ~151
FREE. Official public-holiday calendar for a supported country, including gazetted movable holidays, with the official government source cited. Some countries also carry sub-national calendars (e.g. the German Laender): the `subdivisions` field lists them, and passing `subdivision` (ISO 3166-2, e.g. 'DE-BY') returns the national calendar merged with that region's statutory days.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code |
| subdivision | string | – | Optional ISO 3166-2 region code (e.g. 'DE-BY'). Returns national + that region's statutory holidays, each tagged national/regional. Omit for the national calendar. |
No output schema declared.
No examples provided.
get_series ~129
PAID ($0.005). Current value of a reference series — e.g. series=policy-rate, vat, minimum-wage. Every value carries its official source citation, effective date, last-confirmed date and staleness flag. Pass api_key if you have one; otherwise the response explains how to pay via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (bypasses x402; metered for invoicing) |
| country | string | yes | ISO country code |
| series | string | yes | Series id, e.g. policy-rate, vat, minimum-wage |
No output schema declared.
No examples provided.
get_series_history ~114
PAID ($0.005). Historical values of a reference series with effective date ranges, optionally filtered by from/to (YYYY-MM-DD). Pass api_key if you have one; otherwise the response explains how to pay via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key |
| country | string | yes | ISO country code |
| from | string | – | Earliest effective date, YYYY-MM-DD |
| series | string | yes | Series id |
| to | string | – | Latest effective date, YYYY-MM-DD |
No output schema declared.
No examples provided.
get_snapshot ~55
PAID ($0.02). Snapshot of every series for every country in one call. Pass api_key if you have one; otherwise the response explains how to pay via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key |
No output schema declared.
No examples provided.
list_series ~44
FREE. Catalog of all latamref reference-data series: supported countries, series ids, descriptions, freshness metadata and per-series URLs. Call this first to discover what data exists.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
settlement_date ~392
PAID ($0.05). Settlement/value date: the date n business days after a trade date, computed on the INTERSECTION of the calendars you name, with a per-day trail showing every skipped day and why, on which calendar. Supply business_days for a cycle you are trading under, or market + instrument_class to have a settlement cycle applied that we cite to its primary source (e.g. US equities T+1 under 17 CFR 240.15c6-1(a); UK gilts T+1 by DMO convention, which is NOT the T+2 equity cycle; Japan equities T+2 but JGBs T+1). Calendars are NATIONAL statutory holiday calendars with researched statutory weekend rules (Israel Saturday-only, Gulf Friday+Saturday, India Sundays plus the 2nd and 4th Saturday), NOT CSD or exchange calendars — each response states the basis and any known divergence. Use 'eu.t2' for the euro cash leg. We refuse FREE rather than guess: beyond published calendar coverage, no cited cycle for the instrument (government bonds never inherit an equity cycle), a cycle not in force on the trade date, or FX spot value dates. Free companion: GET /settlement-conventions.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key (bypasses x402; metered for invoicing) |
| business_days | integer | – | The offset you are trading under (T+n) |
| calendars | array | yes | Calendar ids to intersect: two-letter ISO country codes, plus 'eu.t2' for the euro cash leg |
| instrument_class | string | – | Instrument class — a government bond never inherits an equity cycle |
| market | string | – | ISO country of the market whose cited cycle should apply (with instrument_class) |
| trade_date | string | yes | Trade/reference date, YYYY-MM-DD. Day 0: never counted, never rolled. |
No output schema declared.
No examples provided.
What is the dev.latamref/reference-data MCP server?
dev.latamref/reference-data is an MCP server listed in the public MCP registry as dev.latamref/reference-data. LatAm govt data, cited to source: rates, VAT, tax, wages, holidays, FX. 22 countries; Brazil free. This page covers its hosted endpoint (https://latamref.dev/mcp).
Is the dev.latamref/reference-data MCP server safe to use?
dev.latamref/reference-data scores 81 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 dev.latamref/reference-data MCP server expose?
dev.latamref/reference-data exposes 11 tools: list_series, get_public_holidays, get_series, get_series_history, check_minimum_wage, and 6 more. Their descriptions and schemas cost roughly 1,882 tokens of context every time the server is loaded.
Does the dev.latamref/reference-data MCP server require authentication?
No. We connected to dev.latamref/reference-data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.latamref/reference-data MCP server still maintained?
dev.latamref/reference-data is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.