Remote MCP · Endpoint

SalesMap MCP server

No. SalesMap answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.salesmap.site/mcp

The last check completed an MCP handshake.

Registry name
site.salesmap/signals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
5.43 s
Tools exposed
8 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Checked buying signals and ranked lead lists for your agent. Never contacts anyone.
Listing
From the official MCP registry (active).
Recent checks of SalesMap
CheckedResultHandshake
2 hours agoHandshake completed5.43 s
3 days agoHandshake completed127 ms
12 days agoHandshake completed110 ms
13 days agoHandshake completed108 ms
14 days agoHandshake completed115 ms
15 days agoHandshake completed108 ms
16 days agoHandshake completed190 ms
17 days agoHandshake completed121 ms
18 days agoHandshake completed125 ms
20 days agoHandshake completed107 ms
22 days agoHandshake completed106 ms
25 days agoHandshake completed205 ms
27 days agoFailed - the request timed out—

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

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