Remote MCP · Endpoint

Porch MCP server

No. Porch answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://porch.okibi.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.okibi/porch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
23 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public URLs for AI agents to catch webhooks, OAuth redirects, job callbacks and approval clicks.
Website
https://porch.okibi.ai/
Listing
From the official MCP registry (active).
Recent checks of Porch
CheckedResultHandshake
34 minutes agoHandshake completed23 ms
9 days agoHandshake completed27 ms
10 days agoHandshake completed92 ms
11 days agoHandshake completed51 ms
12 days agoHandshake completed29 ms
14 days agoHandshake completed29 ms
14 days agoHandshake completed21 ms
15 days agoHandshake completed36 ms
17 days agoHandshake completed20 ms
19 days agoHandshake completed22 ms
21 days agoHandshake completed31 ms
24 days agoHandshake completed29 ms
26 days agoHandshake completed30 ms
28 days agoHandshake completed82 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Porch and makes no claim about it beyond what these checks measured.