Remote MCP · Endpoint

TrueScrape MCP server

No. TrueScrape answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://api.truescrape.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.TrueScrape/truescrape
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
315 ms
Tools exposed
271 tools
Uptime, last 30 days
100% from 10 checks
Described by its publisher as
Live context for your agent: competitors, mentions and markets, from public data.
Listing
From the official MCP registry (active).
Recent checks of TrueScrape
CheckedResultHandshake
2 days agoHandshake completed315 ms
6 days agoHandshake completed303 ms
16 days agoHandshake completed294 ms
17 days agoHandshake completed309 ms
17 days agoHandshake completed290 ms
19 days agoHandshake completed291 ms
21 days agoHandshake completed298 ms
21 days agoHandshake completed318 ms
22 days agoHandshake completed292 ms
23 days agoHandshake completed482 ms

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

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