Remote MCP · Endpoint

io.github.astafford8488/pitchiq-mcp MCP server

No. io.github.astafford8488/pitchiq-mcp answered an MCP handshake 9 days ago.

UpLast checked 9 days ago

Server URL

https://pitchiq-mcp-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.astafford8488/pitchiq-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
22 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Agent-native CRM + get-booked platform. Operate over MCP, or pay per call via x402. No login.
Listing
From the official MCP registry (active).
Recent checks of io.github.astafford8488/pitchiq-mcp
CheckedResultHandshake
9 days agoHandshake completed22 ms
10 days agoHandshake completed23 ms
11 days agoHandshake completed21 ms
12 days agoHandshake completed23 ms
14 days agoHandshake completed22 ms
14 days agoHandshake completed59 ms
15 days agoHandshake completed137 ms
16 days agoHandshake completed36 ms
18 days agoHandshake completed40 ms
21 days agoHandshake completed21 ms
23 days agoHandshake completed35 ms
26 days agoHandshake completed25 ms
28 days agoHandshake completed21 ms

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

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 io.github.astafford8488/pitchiq-mcp and makes no claim about it beyond what these checks measured.