Remote MCP · Endpoint
Trooth MCP server
No. Trooth answered an MCP handshake 2 days ago.
UpLast checked 2 days 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
- 364 ms
- Tools exposed
- 28 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Machine-Readable Company Profiles: find, search and read any company's Trust Profile, fact by fact.
- Website
- https://trooth.co/
- Repository
- https://github.com/troothllc/trooth-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 days ago | Handshake completed | 364 ms |
| 3 days ago | Handshake completed | 641 ms |
| 3 days ago | Handshake completed | 324 ms |
| 5 days ago | Handshake completed | 37 ms |
| 6 days ago | Handshake completed | 54 ms |
| 7 days ago | Handshake completed | 423 ms |
| 8 days ago | Handshake completed | 279 ms |
| 9 days ago | Handshake completed | 469 ms |
| 11 days ago | Handshake completed | 407 ms |
| 14 days ago | Handshake completed | 312 ms |
| 16 days ago | Handshake completed | 420 ms |
| 18 days ago | Handshake completed | 488 ms |
| 21 days ago | Handshake completed | 483 ms |
| 22 days ago | Handshake completed | 229 ms |
| 25 days ago | Handshake completed | 362 ms |
| 27 days ago | Handshake completed | 296 ms |
| 29 days ago | Handshake completed | 241 ms |
| 30 days ago | Handshake completed | 41 ms |
| 32 days ago | Handshake completed | 317 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 27.
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.