Treasury Exchange Rates MCP for AI. Benchmark official rates for global financial reporting.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
U.S. Treasury Exchange Rates — Official Foreign Currency Data gives you access to rates sourced directly from the U.S. Department of the Treasury.
It provides current official exchange rates for over 170 foreign currencies against the USD, as well as deep historical and fiscal datasets.
Use it when your workflow requires government-certified financial benchmarks for accounting or analysis.
What your AI can do
Get treasury exchange rates
Returns official exchange rates covering 170+ currencies against USD, suitable for bulk financial reporting.
Get exchange rate for currency
Retrieves the latest Treasury rate for a single specified foreign currency or country pair, updated quarterly.
Query treasury dataset
Allows querying any specific fiscal dataset on treasury.gov by providing the exact API endpoint path.
Get the latest official rate for 170+ foreign currencies against the U.S. dollar.
Find the specific, current Treasury-backed exchange rate for any named currency pair.
Pull time-series data to track how a specified currency's rate has changed over years or months.
Run targeted queries against the entire spectrum of Treasury accounting and debt reporting data using known API endpoints.
Ask an AI about this
Waiting for input…
U.S. Treasury Exchange Rates: 3 Tools for Global Finance
These tools let you retrieve official, benchmark foreign exchange rates and access detailed financial reporting data directly from the U.S. Department of the Treasury.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using U.S. Treasury Exchange Rates — Official Foreign Currency Data on VinkiusGet Treasury Exchange Rates
Returns official exchange rates covering 170+ currencies against USD, suitable for bulk financial reporting.
Get Exchange Rate For Currency
Retrieves the latest Treasury rate for a single specified foreign currency or...
Query Treasury Dataset
Allows querying any specific fiscal dataset on treasury.gov by providing the exact...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with U.S. Treasury Exchange Rates — Official Foreign Currency Data, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by U.S. Department of the Treasury. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Compiling financial reports used to feel like a spreadsheet nightmare.
Before this server, generating a cross-border report meant navigating dozens of tabs: one for the Euro rate from Source A, another for the Japanese Yen from Source B, and then spending hours manually verifying that all those rates aligned with official government reporting standards. You’d spend half your time copy-pasting data just to prove it was consistent.
Now, you ask your agent to pull the required benchmarks using `get_treasury_exchange_rates`. The agent runs the query and gives you a single, structured dataset containing all 170+ official rates. You get clean, authoritative figures in seconds.
U.S. Treasury Exchange Rates MCP Server: Official Foreign Currency Data
The biggest time sink used to be the gap between rate availability and data granularity. You could get a current currency rate, but if you needed supporting context—say, the underlying debt metrics for that country—you were stuck going back to another API or database entirely.
With this MCP Server, you synthesize everything. You can use `get_exchange_rate_for_currency` for the quick check, and then immediately pivot to using `query_treasury_dataset` to pull supporting financial context from the same reliable source. It’s all connected.
What your AI can actually do with this
You wanna run numbers that matter? This server pulls rates straight from the U.S. Department of the Treasury—that means you're working with government-certified financial benchmarks, not some sketchy private bank feed. When your workflow needs official hard data for accounting or deep analysis, this is what you use.
get_treasury_exchange_rates: This tool lets you grab all the benchmark rates at once. It returns official exchange rates covering over 170 foreign currencies against the U.S. dollar. You run this when you're doing bulk financial reporting because it gives you a massive snapshot of the current market, using the exact rates federal agencies use for their own reports.
get_exchange_rate_for_currency: Need just one pair? This tool retrieves the latest Treasury rate for any single foreign currency or country pairing you specify. It updates quarterly and is perfect when you only need to check that specific current official exchange rate—say, finding out the exact USD rate for the Japanese Yen or Canadian Dollar without having to process a whole list of currencies.
query_treasury_dataset: This is where you go deep into the books. If rates aren't enough, this tool lets you query any specific fiscal dataset available on treasury.gov. You provide the exact API endpoint path for what you want—it could be debt metrics, specific accounting records, or time-series data tracking how a particular currency’s rate has shifted over months or years.
This mechanism means you're not limited to just the current rates; you can target virtually any documented dataset the Treasury tracks.
Think about it: If your job requires knowing how many times a specific metric—like bond yield changes or historical debt reporting—has changed, you use this endpoint path. It’s designed for targeted data extraction, giving you access to the full spectrum of Treasury accounting and debt information through direct querying. You specify the resource path, and it pulls the raw data history you need.
It's all about precision. Whether you're tracking annual trends across multiple years or just needing that single rate update for a quarterly filing, these tools keep you tethered to the official source. You get bulk rates with get_treasury_exchange_rates for your main report; you check specific pairs quickly using get_exchange_rate_for_currency; and when you need to dive into historical context or complex fiscal records—like running a time-series analysis of a currency's rate shift over five years—you hit up the raw endpoint paths with query_treasury_dataset.
You won’t waste time compiling data from multiple, unrelated sources. You use your AI client to call these tools directly, pulling the exact numbers you need for everything from corporate treasury management to academic financial research. It's clean, it's official, and it's built around three distinct functions that cover every angle: current bulk benchmarks, specific pair lookups, and deep, targeted data history.
019d7615-70db-711c-8b93-1bdc3ca1ce3f Here's how it actually works
The bottom line is that you get direct, verifiable numbers from the U.S. Department of the Treasury for your analysis.
Specify the required rate or dataset. For rates, input a currency name (e.g., 'Euro') or use get_treasury_exchange_rates for bulk data. If querying deep records, provide the exact endpoint path to the desired fiscal dataset.
The server calls the U.S. Treasury API, retrieving the official rate or structured JSON data based on your parameters (e.g., date range, currency code).
Your agent receives a clean, formatted result containing the government-verified exchange rates or the requested financial record.
Who is this actually for?
This tool is for quantitative analysts and financial auditors who deal with cross-border capital or government reporting. You use it when you can't trust secondary market data, and you need a rate that stands up to federal scrutiny. It’s perfect for the treasury analyst tired of manually compiling exchange rates from three different sources.
Uses get_treasury_exchange_rates to get a full benchmark list when preparing quarterly financial statements, ensuring all foreign currency figures match official government records.
Employs query_treasury_dataset to pull specific historical debt metrics (like the debt-to-penny ratio) required for compliance reporting on a project basis.
Uses both get_exchange_rate_for_currency and historical functions to model currency volatility, cross-referencing official rates against internal trading models.
What Changes When You Connect
Cross-Validate Data: Use get_treasury_exchange_rates to pull a bulk list of 170+ currency benchmarks, allowing you to compare multiple foreign exchange values against a single, reliable source instantly.
Pinpoint Rates Fast: Need one specific rate? get_exchange_rate_for_currency lets your agent grab the official Treasury rate for 'Brazil-Real' or any other pair without needing complex parameters.
Deep Fiscal Analysis: Go beyond rates. query_treasury_dataset provides access to specific accounting information, like debt metrics, letting you analyze underlying financial health indicators not available through standard currency lookups.
Historical Context: Track how a rate has moved over time using the historical functions. This context is crucial for modeling risk and comparing current market positions against past federal standards.
Eliminate Rate Drift Risk: By sourcing rates directly from the U.S. Department of the Treasury, your reports minimize the chance of relying on secondary or less authoritative exchange data.
See it in action
Comparing Foreign Debt Obligations
An auditor needs to calculate the USD value of a foreign bond portfolio. Instead of manually searching, they ask their agent to use query_treasury_dataset with the relevant endpoint path. The agent returns the required dataset alongside the necessary exchange rates from get_treasury_exchange_rates, completing the calculation in one step.
Preparing a Multi-Currency Report
A finance manager needs to list current official conversion benchmarks for 20 different countries. They trigger get_treasury_exchange_rates. The agent immediately returns all rates against the USD, saving hours of manual lookups and ensuring consistency across the entire report.
Checking a Single Target Market Rate
A trader needs to confirm the official rate for the Japanese Yen before executing a large transfer. They ask their agent to use get_exchange_rate_for_currency with 'Japan-Yen'. The result is immediate, providing the single, verifiable Treasury benchmark.
Analyzing Historical Trends
A quantitative analyst wants to see how a currency's rate behaved over the last year. They prompt their agent for historical rates using the specified country/currency tool. The agent provides a time-series list, letting them plot and analyze trends instantly.
The honest tradeoffs
Assuming real-time data
A user asks for 'the live exchange rate right now' and gets frustrated when the tool shows quarterly rates.
Remember these are official benchmarks, not minute-by-minute interbank feeds. Use get_treasury_exchange_rates or get_exchange_rate_for_currency to get the latest official rate available (updated quarterly).
Mixing data sources randomly
Copying a currency list from Google and then trying to manually cross-check each against a different vendor's API.
Always start with get_treasury_exchange_rates. It gives you the full, authoritative list of 170+ currencies in one go. Don't waste time on multiple single lookups.
Asking for general financial data
A user asks 'What is the current debt status?' without knowing the specific dataset path.
Don't guess the endpoint. You must use query_treasury_dataset and provide the exact API endpoint path (e.g., /v2/accounting/od/debt_to_penny). Check the treasury.gov documentation first.
When It Fits, When It Doesn't
Use this server if your financial model requires rates or data points that are explicitly backed by U.S. Department of the Treasury records. Don't use it if you need volatile, second-by-second interbank market pricing (you'd need a dedicated FX feed).
* Use get_treasury_exchange_rates: When preparing reports that cover many currencies and require bulk benchmark rates against the USD.
* Use get_exchange_rate_for_currency: For simple, quick checks on one specific rate pair (e.g., checking only the Euro).
* Use query_treasury_dataset: When your goal is to analyze a non-rate dataset—like debt ratios or specific fiscal accounts—and you know the exact API path.
If you are unsure of the data source, default to cross-validating critical rates using all three tools. If the discrepancy persists, it's likely an issue with market timing versus official benchmark reporting.
Questions you might have
What is the difference between 'historical' rates and current rates when using get_treasury_exchange_rates? +
The tool provides both. You can query historical data to see how a rate changed over time, or you can request the latest official rate for benchmarking against today's figures. They serve different purposes in financial modeling.
Can I use get_exchange_rate_for_currency if the currency is not listed? +
If the currency isn't recognized by the U.S. Treasury system, the tool won't return a rate. You must confirm the country code or name against the source documentation to ensure accuracy.
How do I query non-currency data using query_treasury_dataset? +
You need the specific API endpoint path for that dataset, like a debt ratio. You pass this exact string into query_treasury_dataset so the agent knows exactly which information to pull from the treasury database.
Are these rates real-time market rates? +
No. These are official benchmark rates provided by the U.S. Department of the Treasury, and they are updated quarterly. They represent established federal accounting figures, not volatile interbank trading data.
When calling `get_treasury_exchange_rates`, do I need an API key or any form of authentication? +
No, you don't. The server operates with zero authorization requirements. This means your agent can access the official rate data without needing to manage credentials.
What should I do if my input for `get_exchange_rate_for_currency` uses an incorrect format? +
The function requires specific formats, such as 'Country-Currency' (e.g., 'Japan-Yen'). If the input fails validation, it sends a detailed error message that explains exactly what structure is missing.
How do I find all the API endpoints and fields supported by `query_treasury_dataset`? +
You must consult the official Treasury fiscaldata.treasury.gov documentation. This source provides a comprehensive list of every available dataset path, field, and required parameter for accurate querying.
Are there rate limits or usage caps when I use `query_treasury_dataset`? +
The service does not publicly document specific call quotas. For high-volume data streams or repeated queries, always check the official Treasury API guidelines for best practice implementation.
How many countries are supported? +
Over 170 currencies and countries are supported.
Can we use this for FOREX trading? +
It is not recommended for algorithmic trading as these are accounting rates, not real-time spot market rates.
We've already built the connector for Treasury Exchange Rates. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 3 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.