Remote MCP · Endpoint

io.sentinelsignal/scoring MCP server

Yes, as of 1 hour ago: the hostname does not resolve.

DownLast checked 1 hour ago

Server URL

https://mcp.sentinelsignal.io/mcp

The last check failed: the hostname does not resolve.

Registry name
io.sentinelsignal/scoring
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
83.3% from 18 checks
Described by its publisher as
Hosted MCP for denial, prior auth, reimbursement, workflow validation, batch scoring, and feedback.
Listing
From the official MCP registry (active).
Recent checks of io.sentinelsignal/scoring
CheckedResultHandshake
1 hour agoFailed - the hostname does not resolve—
2 days agoFailed - the hostname does not resolve—
4 days agoFailed - the hostname does not resolve—
6 days agoHandshake completed46 ms
7 days agoHandshake completed42 ms
9 days agoHandshake completed49 ms
10 days agoHandshake completed43 ms
11 days agoHandshake completed42 ms
14 days agoHandshake completed45 ms
15 days agoHandshake completed43 ms
17 days agoHandshake completed50 ms
19 days agoHandshake completed51 ms
20 days agoHandshake completed51 ms
21 days agoHandshake completed57 ms
22 days agoHandshake completed44 ms
22 days agoHandshake completed48 ms
23 days agoHandshake completed45 ms
25 days agoHandshake completed48 ms

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

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