Remote MCP · Endpoint

Fca Register MCP server

No. Fca Register answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://gateway.pipeworx.io/fca-register/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/fca-register
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
372 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
FCA Financial Services Register MCP — the UK Financial Conduct Authority's public register of…
Listing
From the official MCP registry (active).
Recent checks of Fca Register
CheckedResultHandshake
43 minutes agoHandshake completed372 ms
3 days agoHandshake completed584 ms
13 days agoHandshake completed82 ms
13 days agoHandshake completed102 ms
15 days agoHandshake completed1.38 s
15 days agoHandshake completed91 ms
17 days agoHandshake completed113 ms
18 days agoHandshake completed246 ms
18 days agoHandshake completed73 ms
20 days agoHandshake completed260 ms
23 days agoHandshake completed474 ms
25 days agoHandshake completed379 ms
28 days agoHandshake completed74 ms

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

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