Remote MCP · Endpoint

Esma Firds MCP server

No. Esma Firds answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/esma-firds/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/esma-firds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.30 s
Tools exposed
43 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
ESMA FIRDS + MiFID authorisation register — the EU's Financial Instruments
Listing
From the official MCP registry (active).
Recent checks of Esma Firds
CheckedResultHandshake
1 hour agoHandshake completed3.30 s
1 day agoHandshake completed324 ms
4 days agoHandshake completed1.12 s
6 days agoHandshake completed424 ms
7 days agoHandshake completed391 ms
9 days agoHandshake completed1.61 s
11 days agoHandshake completed1.09 s
11 days agoFailed - the request timed out—
13 days agoHandshake completed869 ms
15 days agoHandshake completed972 ms
17 days agoHandshake completed957 ms
19 days agoHandshake completed4.15 s
20 days agoHandshake completed836 ms
21 days agoHandshake completed842 ms
22 days agoHandshake completed1.75 s

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

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 Esma Firds and makes no claim about it beyond what these checks measured.