Home / MCP registry index / app.hedgr/hedgr
Hedgr FX Risk & Treasury
app.hedgr/hedgr in the official MCP registry.
Endpoint https://hedgr.app/mcp.
The registry describes it as: Read-only FX exposure, cash, hedge and P&L data from a Hedgr workspace, for SME finance teams.
We read its 27 tools on 2026-10-22. 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_platform_capabilities get_dashboard_context get_account_status list_entities get_fx_exposure get_cash_position get_hedge_portfolio simulate_scenario get_protection_candidates get_policy get_market_regime get_pnl_attribution get_limit_status get_transaction_log_summary get_overdue_drivers get_data_quality get_payment_patterns get_cashflow_timing get_cashflow_forecast get_funding_forecast get_protection_builder_snapshot get_policy_backtest_summary get_rate_assumptions get_export_manifest get_navigation_targets get_workspace_setup_state get_fx_guidance
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-hedgr-hedgr)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.