Home / MCP registry index / com.currencyguard/guard-pricing
CurrencyGuard Guard Pricing
com.currencyguard/guard-pricing in the official MCP registry.
Endpoint https://api.currencyguard.com/mcp. Source: gitlab.com/currencyguard/server.
The registry describes it as: FX protection for SMEs — price Guards, live spot/forward rates, settlement dates, and more.
We read its 11 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_spot_rate list_supported_currencies get_forward_rate price_guard compare_guard_with_forward resolve_settlement_date get_historic_best_worst price_guard_extension explain_guard_product net_exposure request_provider_availability
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-currencyguard-guard-pricing)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.