Remote MCP · Endpoint

SolvScore MCP server

No. SolvScore answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://solvscore.com/mcp

The last check completed an MCP handshake.

Registry name
com.solvscore/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
232 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Credit scores for AI agents. Underwrite an unknown counterparty before extending credit.
Listing
From the official MCP registry (active).
Recent checks of SolvScore
CheckedResultHandshake
1 hour agoHandshake completed232 ms
2 days agoHandshake completed224 ms
4 days agoHandshake completed235 ms
5 days agoHandshake completed273 ms
7 days agoHandshake completed236 ms
8 days agoHandshake completed268 ms
9 days agoHandshake completed223 ms
12 days agoHandshake completed230 ms
13 days agoHandshake completed224 ms
15 days agoHandshake completed227 ms
16 days agoHandshake completed244 ms
17 days agoHandshake completed222 ms
19 days agoHandshake completed231 ms
20 days agoHandshake completed221 ms
20 days agoHandshake completed233 ms
21 days agoHandshake completed239 ms
22 days agoHandshake completed227 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 SolvScore and makes no claim about it beyond what these checks measured.