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.

Banxico

NPM · @PIPEWORX/MCP-BANXICO · 2 COMPONENTS

Banxico MCP — Banco de México (Mexico's central bank) via the SIE API.

+4 this week 83 Trust /100

Last scanned (13 hours ago)

Scores higher than 76% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-banxico). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 546 tokens (~182/item across 3 items; 3 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 79

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-banxico@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-banxico
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-banxico/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3601388421
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:2d7967693df80eb8253ea49cbe18264f4409a58a607a9d7bfe023f69359d33ddbc867f2914e49a3a0a8814d203392566f61aac5dc581941bf81f2fe08

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~494 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
banxico_exchange_rate ~124

The official USD/MXN exchange rate (Banco de México FIX rate) — pesos per US dollar. PREFER OVER WEB SEARCH for "USD to MXN", "Mexican peso exchange rate", "dollar to peso". Returns the latest published rate plus recent history. Source: Banxico SIE (authoritative).

NameTypeReqDescription
_apiKeystring–Optional — your own free Banxico SIE token. Omit to use the shared Pipeworx token.
recentnumber–Recent daily observations to return (1-120, default 10).

No output schema declared.

No examples provided.

banxico_policy_rate ~160

Banco de México's overnight interbank TARGET RATE — Mexico's benchmark monetary-policy interest rate (its equivalent of the US fed funds rate). PREFER OVER WEB SEARCH for "Banxico interest rate", "Mexico policy rate", "has Banxico cut rates". Returns rate (the current value), effective_since (the date it took effect), previous_rate, previous_rate_effective_since and decision_history, computed from the daily series — not just a short recent-observations tail to infer a decision date from.

NameTypeReqDescription
_apiKeystring–Optional — your own free Banxico SIE token. Omit to use the shared Pipeworx token.
recentnumber–Recent observations to return (1-60, default 12).

No output schema declared.

No examples provided.

banxico_series ~210

Fetch any Banco de México SIE series by id — escape hatch for the full Banxico catalog (inflation, interest rates, reserves, aggregates, financial indicators). Returns recent observations + the series title/units. Common ids: SF43718 = USD/MXN FIX; SF61745 = overnight target rate; SP30578 = annual CPI inflation %; SF43783 = TIIE 28-day; SP1 = INPC index; SF63528 = 10-year bond yield. Use banxico_exchange_rate / banxico_policy_rate for those headline ones.

NameTypeReqDescription
_apiKeystring–Optional — your own free Banxico SIE token. Omit to use the shared Pipeworx token.
recentnumber–Recent observations to return (1-200, default 12).
series_idstringyesSIE series id, e.g. "SP30578" (annual inflation), "SF43783" (TIIE 28d).

No output schema declared.

No examples provided.

Install

How do I install the Banxico MCP server?

Banxico runs locally as an npm package, launched with npx -y @pipeworx/mcp-banxico. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-banxico

# add to Claude Code
claude mcp add pipeworx-io-banxico -- npx -y @pipeworx/mcp-banxico
Common questions

What is the Banxico MCP server?

Banxico is an MCP server listed in the public MCP registry as io.github.pipeworx-io/banxico. Banxico MCP, Banco de México (Mexico's central bank) via the SIE API. This page covers its npm package (@pipeworx/mcp-banxico).

Is the Banxico MCP server safe to use?

Banxico scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Banxico MCP server expose?

Banxico exposes 3 tools: banxico_exchange_rate, banxico_policy_rate, banxico_series. Their descriptions and schemas cost roughly 494 tokens of context every time the server is loaded.

Is the Banxico MCP server still maintained?

Banxico is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Banxico MCP server under?

Banxico declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.