# Banxico (npm · @pipeworx/mcp-banxico)

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

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-banxico/banxico-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-banxico/banxico-mcp)
- npm · `@pipeworx/mcp-banxico`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-banxico/pipeworx-mcp-banxico.md), [page](https://verifymcp.io/servers/pipeworx-io-banxico/pipeworx-mcp-banxico)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-banxico`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-banxico).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add pipeworx-io-banxico -- npx -y @pipeworx/mcp-banxico
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-banxico": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-banxico"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-banxico": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-banxico"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-banxico -- npx -y @pipeworx/mcp-banxico
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-banxico": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-banxico"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-banxico --command npx --arg -y --arg @pipeworx/mcp-banxico
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-banxico:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-banxico"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-banxico": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-banxico"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-banxico -t stdio -c npx -a -y @pipeworx/mcp-banxico
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-banxico": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-banxico"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +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.

### 2026-11-03 (score 82, +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.

### 2026-11-01 (score 81, +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.

### 2026-10-31 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 65, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `banxico_exchange_rate` (~124 tokens)

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).

Input parameters:

- `_apiKey` (string): Optional — your own free Banxico SIE token. Omit to use the shared Pipeworx token.
- `recent` (number): Recent daily observations to return (1-120, default 10).

### `banxico_policy_rate` (~160 tokens)

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.

Input parameters:

- `_apiKey` (string): Optional — your own free Banxico SIE token. Omit to use the shared Pipeworx token.
- `recent` (number): Recent observations to return (1-60, default 12).

### `banxico_series` (~210 tokens)

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.

Input parameters:

- `_apiKey` (string): Optional — your own free Banxico SIE token. Omit to use the shared Pipeworx token.
- `recent` (number): Recent observations to return (1-200, default 12).
- `series_id` (string, required): SIE series id, e.g. "SP30578" (annual inflation), "SF43783" (TIIE 28d).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-banxico/pipeworx-mcp-banxico#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 65
- 2026-10-29: 79

## 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.

### What did VerifyMCP test on the Banxico MCP server?

VerifyMCP ran 16 checks on Banxico, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-banxico
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-banxico
- Repository: https://github.com/pipeworx-io/mcp-banxico
- Website: https://pipeworx.io/packs/banxico
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-banxico/pipeworx-mcp-banxico.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-banxico/pipeworx-mcp-banxico/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-banxico/pipeworx-mcp-banxico.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-banxico/pipeworx-mcp-banxico