Chat assistants know exchange rates only from training data, so quoted rates can be weeks or months old. An MCP currency server fetches a current rate at call time, and the assistant uses it for the arithmetic and the explanation.
https://mcp.zovo.one/mcp/currency/t/<token>:{
"mcpServers": {
"currency": {
"url": "https://mcp.zovo.one/mcp/currency/t/<token>"
}
}
}
initialize answers 200 regardless, so verify with an actual conversion call.The currency MCP server is hosted free at mcp.zovo.one (anonymous tier; Pro $19 single, $39 bundle). Pair it with invoice, expense-tracker or amortization servers whenever documents mix currencies.
Before blaming the assistant, confirm the server answers a real call. Discovery alone is not proof — initialize and tools/list answer 200 even with a bad token, but this is the exact request shape to start from:
curl -s https://mcp.zovo.one/mcp/currency/t/<token> \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
If this returns a tool list, the token and URL are good and any remaining problem is in the client’s connector settings.
A currency server returns a rate for a pair at call time. Rates move, so a document generated today and one generated tomorrow can differ without either being wrong. For any figure that appears in a legal or tax document, print the rate used into the document itself.
Decide rounding once and state it in the request: convert first, then round the document total to two decimals, and never round intermediate line items. If the assistant rounds each line before summing, totals drift by cents, which bank reconciliation then flags; the fix is one sentence in the request.
The server that does this: Currency — 8 tools, free locally (MIT), $19 one-time for the hosted endpoint. Read the server page · Buy the licence.