Remote MCP · Endpoint

Fca Shorts MCP server

No. Fca Shorts answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/fca-shorts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
92 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
FCA UK short-position disclosures — the Financial Conduct Authority
Listing
From the official MCP registry (active).
Recent checks of Fca Shorts
CheckedResultHandshake
1 day agoHandshake completed92 ms
3 days agoHandshake completed88 ms
5 days agoHandshake completed50 ms
7 days agoHandshake completed58 ms
8 days agoHandshake completed57 ms
9 days agoHandshake completed2.12 s
11 days agoHandshake completed62 ms
14 days agoHandshake completed40 ms
15 days agoHandshake completed57 ms
17 days agoHandshake completed86 ms
18 days agoHandshake completed44 ms
19 days agoHandshake completed37 ms
20 days agoHandshake completed38 ms
21 days agoHandshake completed53 ms
22 days agoHandshake completed61 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 Fca Shorts and makes no claim about it beyond what these checks measured.