This MCP server exposes two families of tools for Colombian financial indicators: Inflation Data tools and TRM (exchange rate) tools. Inflation tools allow you to fetch paginated inflation data, retrieve data for a specific month and year, and query data over a date range. TRM tools let you obtain historical USD to COP exchange rates, query the TRM data within a date range, and fetch the TRM value for a specific date. The server is designed to work with MCP clients such as Claude Desktop, enabling secure remote access to these tools via the MCP protocol. To use it, connect from your MCP client to the remote server endpoint and browse the available tools, applying optional pagination and sorting as needed. The recommended integration path is to use the mcp-remote proxy (via npx) to connect Claude Desktop to the remote MCP server, so you can see and invoke the provided tools directly in your MCP client UI.

Prerequisites:

• Node.js and npm installed on your machine (npx is included with npm).

Installation steps:

1. Ensure Node.js and npm are installed. Verify with: node -v npm -v

2. No local server install is required for this setup since the server is accessed via npx mcp-remote. If you prefer a local copy, install the mcp-remote package globally or locally: npm install -g mcp-remote

   or locally in a project:

   npm install mcp-remote

3. Validate access to the MCP server by connecting through Claude Desktop or another MCP client using the provided mcp-remote endpoint: npx mcp-remote http://mcp.banrepco.kevyder.dev/sse

4. In Claude Desktop, configure the MCP server with the endpoint as shown in the example configuration: { "mcpServers": { "banrepco": { "command": "npx", "args": [ "mcp-remote", "http://mcp.banrepco.kevyder.dev/sse" ] } } }

Tips and considerations:

• The server exposes inflation and TRM tools; use pagination parameters where supported to manage large result sets.
• When connecting from Claude Desktop, ensure your network can reach the remote endpoint http://mcp.banrepco.kevyder.dev/sse. If you move to a different host, update the mcpServers configuration accordingly.
• The tools are designed to be easily extensible; if you need additional data sources or endpoints, you can extend the MCP server configuration or add new endpoints following the MCP protocol conventions.
• If you encounter authentication or access errors, verify that the remote MCP endpoint is reachable and that any required API keys or tokens are configured in your environment as needed by the remote service.
• For local testing, you can substitute the endpoint with a local mcp-remote proxy or a test server endpoint that echoes tool availability.