Remote MCP · Endpoint

Hedgr FX Risk & Treasury MCP server

No. Hedgr FX Risk & Treasury answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://hedgr.app/mcp

The last check completed an MCP handshake.

Registry name
app.hedgr/hedgr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
322 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only FX exposure, cash, hedge and P&L data from a Hedgr workspace, for SME finance teams.
Listing
From the official MCP registry (active).
Recent checks of Hedgr FX Risk & Treasury
CheckedResultHandshake
1 hour agoHandshake completed322 ms
1 day agoHandshake completed213 ms
4 days agoHandshake completed338 ms
6 days agoHandshake completed333 ms
9 days agoHandshake completed291 ms
11 days agoHandshake completed329 ms
13 days agoHandshake completed768 ms
15 days agoHandshake completed340 ms
17 days agoHandshake completed458 ms
19 days agoHandshake completed325 ms
21 days agoHandshake completed223 ms
22 days agoHandshake completed425 ms
23 days agoHandshake completed320 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Hedgr FX Risk & Treasury and makes no claim about it beyond what these checks measured.