Remote MCP · Endpoint

Prosp MCP server

No. Prosp answered an MCP handshake 19 hours ago.

UpLast checked 19 hours ago

Server URL

https://api.prosp.cc/mcp-rpc

The last check completed an MCP handshake.

Registry name
cc.prosp/prosp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
468 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find B2B companies that fit your buyer, with their contacts and register IDs, and write outreach.
Listing
From the official MCP registry (active).
Recent checks of Prosp
CheckedResultHandshake
19 hours agoHandshake completed468 ms
11 days agoCredentials required—
12 days agoCredentials required—
12 days agoCredentials required—
14 days agoCredentials required—
15 days agoCredentials required—
16 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
25 days agoCredentials required—
27 days agoCredentials required—
29 days agoCredentials required—

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

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