mcp-registry/dev.latamref/reference-data · v1.0.0
As of 2026-10-22 01:39 UTC, the Latamref Reference Data MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 128 outages in 90 days, with a median recovery of 4 minutes.
LatAm govt data, cited to source: rates, VAT, tax, wages, holidays, FX. 22 countries; Brazil free.
Point your MCP client at this streamable-http endpoint: https://latamref.dev/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Reachable 98.6% of the time over the last 30 days; median recovery 4 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~2,333 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 0 tool(s) removed and 14 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.latamref/reference-data"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.latamref/reference-data"}) over MCP.
compute_employment_cost ~581 tokenssettlement_date ~522 tokensinvoice_payable ~510 tokenscompute_statutory_interest ~505 tokenscost_hire ~484 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.latamref%2Freference-data?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.latamref%2Freference-data?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.latamref%2Freference-data.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.latamref%2Freference-data.svg :target: https://glimind.com/server/mcp-registry%2Fdev.latamref%2Freference-data?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f5968ca24ac731b1…, first seen 2026-10-19, included at leaf 27876 of 42,725. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable knowledge servers · most reliable productivity servers · most reliable calendar servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 01:39 UTC, the Latamref Reference Data MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 128 outages in 90 days, with a median recovery of 4 minutes.
Latamref Reference Data MCP server advertises 32 tools, including add_business_days, business_days_between, charge_sale, charge_sale_certified, check_minimum_wage.
Point your MCP client at this streamable-http endpoint: https://latamref.dev/mcp
Glimind scanned all 32 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.