Remote MCP · Endpoint

Trooth MCP server

No. Trooth answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.trooth.co/public/mcp

The last check completed an MCP handshake.

Registry name
io.github.troothllc/trooth-network
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
483 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Machine-Readable Company Profiles: find, search and read any company's Trust Profile, fact by fact.
Listing
From the official MCP registry (active).
Recent checks of Trooth
CheckedResultHandshake
1 hour agoHandshake completed483 ms
1 day agoHandshake completed229 ms
3 days agoHandshake completed362 ms
6 days agoHandshake completed296 ms
7 days agoHandshake completed241 ms
9 days agoHandshake completed41 ms
10 days agoHandshake completed317 ms
11 days agoHandshake completed34 ms
13 days agoHandshake completed349 ms
15 days agoHandshake completed203 ms
17 days agoHandshake completed49 ms
19 days agoHandshake completed109 ms
20 days agoHandshake completed49 ms
21 days agoHandshake completed33 ms
22 days agoHandshake completed112 ms

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

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