Remote MCP · Endpoint

dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper MCP server

No. dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cf-worker.selbyventurecap.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
199 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Apollo->Salesforce Lead mapper. No LLM. Strict-fail required fields. PASS/REPAIR/FAIL verdict.
Listing
From the official MCP registry (active).
Recent checks of dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper
CheckedResultHandshake
1 hour agoHandshake completed199 ms
2 days agoHandshake completed215 ms
4 days agoHandshake completed143 ms
5 days agoHandshake completed162 ms
7 days agoHandshake completed134 ms
8 days agoHandshake completed273 ms
9 days agoHandshake completed163 ms
12 days agoHandshake completed132 ms
13 days agoHandshake completed167 ms
15 days agoHandshake completed140 ms
16 days agoHandshake completed1.03 s
18 days agoHandshake completed40 ms
19 days agoHandshake completed179 ms
20 days agoHandshake completed150 ms
20 days agoHandshake completed139 ms
21 days agoHandshake completed52 ms
22 days agoHandshake completed538 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 dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper and makes no claim about it beyond what these checks measured.