Remote MCP · Endpoint

Scoutee MCP server

No. Scoutee answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://scoutee.org/api/mcp/public

The last check completed an MCP handshake.

Registry name
org.scoutee/scoutee
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
319 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Tender search + AI CPV finder. Register free: 1 daily email alert, up to 20 results/search.
Listing
From the official MCP registry (active).
Recent checks of Scoutee
CheckedResultHandshake
1 hour agoHandshake completed319 ms
2 days agoHandshake completed194 ms
4 days agoHandshake completed689 ms
5 days agoHandshake completed183 ms
7 days agoHandshake completed198 ms
8 days agoHandshake completed230 ms
9 days agoHandshake completed435 ms
12 days agoHandshake completed201 ms
13 days agoHandshake completed386 ms
15 days agoHandshake completed138 ms
17 days agoHandshake completed184 ms
18 days agoHandshake completed139 ms
19 days agoHandshake completed158 ms
20 days agoHandshake completed330 ms
21 days agoHandshake completed198 ms
21 days agoHandshake completed374 ms
23 days agoHandshake completed326 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 Scoutee and makes no claim about it beyond what these checks measured.