Remote MCP · Endpoint

PCFHub MCP server

No. PCFHub answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pcfhub.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.pcfhub/pcfhub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.03 s
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find Power Apps PCF controls, read their docs, and validate pcfhub.json manifests.
Listing
From the official MCP registry (active).
Recent checks of PCFHub
CheckedResultHandshake
1 hour agoHandshake completed1.03 s
2 days agoHandshake completed1.09 s
4 days agoHandshake completed1.12 s
5 days agoHandshake completed1.17 s
7 days agoHandshake completed273 ms
8 days agoHandshake completed1.20 s
9 days agoHandshake completed342 ms
12 days agoHandshake completed1.15 s
13 days agoHandshake completed1.24 s
15 days agoHandshake completed1.23 s
17 days agoHandshake completed1.68 s
18 days agoHandshake completed1.10 s
19 days agoHandshake completed525 ms
20 days agoHandshake completed157 ms
20 days agoHandshake completed266 ms
21 days agoHandshake completed1.05 s
23 days agoHandshake completed246 ms

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

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