Skip to main content
Glama
banrep-co

banrep-co

by pipeworx-io

@pipeworx/banrep-co

Banco de la República (Colombia) rates: the intervention rate (the policy rate) with every change since 1998, and the representative market exchange rate (TRM, Colombian pesos per US dollar), by date or range.

Part of Pipeworx — an MCP gateway connecting AI agents to 1957+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

  • banrep_co_series_list() — the two series served and the latest date each reaches.

  • banrep_co_policy_rate({ start_date?, end_date? }) — the intervention rate in force with the date it took effect, plus changes newest first (default the 10 most recent in the last few years, or a date window; history back to 1998). Percent per annum.

  • banrep_co_exchange_rates({ currency?, date? | start_date?, end_date? }) — the TRM, pesos per US dollar. Latest by default, or one date, or a range up to 366 days. Only USD is served; any other currency is an error naming it. A date or range with no TRM returns count: 0 with an empty_reason.

Related MCP server: mcp-trm-colombia

Auth

Keyless.

Data sources

  • Banco de la República, intervention rate (daily).

  • Banco de la República, representative market exchange rate (TRM, daily). Each call reads live from the bank; nothing is stored.

Things worth knowing:

  • The TRM is set ahead: each date carries the rate in force on it, and the latest value can run a few days past today (a note says so).

  • The bank's service has no policy-rate history for a single date; the pack derives changes from the daily series, so an effective date is the first day the new rate appears.

  • For a very long quiet spell the default look-back may hold no change: the response then says the rate has not changed since at least the start of the span and current_effective_from is null. Pass an earlier start_date to find it.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "banrep-co": {
      "url": "https://gateway.pipeworx.io/banrep-co/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/banrep-co/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1957+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/banrep_co_series_list \
  -H 'Content-Type: application/json' \
  -d '{}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/banrep_co_series_list. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-banrep-co is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/banrep-co/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "banrep-co": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-banrep-co"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Banrep Co data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A template for deploying MCP servers on Cloudflare Workers without authentication. Enables easy creation and deployment of custom MCP tools that can be accessed remotely via Claude Desktop or Cloudflare AI Playground.
      9
      Mozilla Public 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to retrieve the official Colombian TRM (USD/COP exchange rate) with its validity window, perform currency conversions, and analyze rate series, all with auditable provenance.
      4
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables querying Mexico's central bank macroeconomic indicators — policy rate, TIIE 28/91, Cetes 28, and UDIS values — plus UDI-to-peso conversion and inflation variation calculations over date ranges. Use-case-oriented tools batch series requests, cache results, and tolerate asynchronous publication quirks to stay within official API quotas.
      17
      MIT