Remote MCP · Endpoint

Italian B2B Lead List Scoring, Ranking & JSON Decisions MCP server

No. Italian B2B Lead List Scoring, Ranking & JSON Decisions answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.machinesignal.it/mcp

The last check completed an MCP handshake.

Registry name
it.machinesignal/discovery
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
325 ms
Tools exposed
6 tools
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Prioritize an existing Italian B2B lead list into up to 250 explained JSON decisions.
Listing
From the official MCP registry (active).
Recent checks of Italian B2B Lead List Scoring, Ranking & JSON Decisions
CheckedResultHandshake
2 hours agoHandshake completed325 ms
15 hours agoHandshake completed395 ms
1 day agoHandshake completed298 ms
2 days agoHandshake completed278 ms

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

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 Italian B2B Lead List Scoring, Ranking & JSON Decisions and makes no claim about it beyond what these checks measured.