Remote MCP · Endpoint

Procfy MCP server

No. Procfy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_procfy

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/procfy-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
182 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Financial management on Procfy — transactions (revenue/expense/transfers), bank accounts, contacts,
Listing
From the official MCP registry (active).
Recent checks of Procfy
CheckedResultHandshake
1 hour agoHandshake completed182 ms
2 days agoHandshake completed67 ms
4 days agoHandshake completed2.22 s
5 days agoHandshake completed109 ms
7 days agoHandshake completed44 ms
8 days agoHandshake completed338 ms
9 days agoHandshake completed213 ms
12 days agoHandshake completed34 ms
14 days agoHandshake completed811 ms
15 days agoHandshake completed853 ms
17 days agoHandshake completed83 ms
18 days agoHandshake completed38 ms
19 days agoHandshake completed56 ms
20 days agoHandshake completed108 ms
20 days agoHandshake completed77 ms
22 days agoHandshake completed968 ms
23 days agoHandshake completed132 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 Procfy and makes no claim about it beyond what these checks measured.