Remote MCP · Endpoint

Tetrees MCP MCP server

No. Tetrees MCP answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://ex.tetrees.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.tetrees.ex/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
207 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Own, grow and trade portable agent intelligence via TAIP/1 Packs and MCP.
Listing
From the official MCP registry (active).
Recent checks of Tetrees MCP
CheckedResultHandshake
7 hours agoHandshake completed207 ms
2 days agoHandshake completed569 ms
4 days agoHandshake completed552 ms
5 days agoHandshake completed571 ms
7 days agoHandshake completed570 ms
8 days agoHandshake completed651 ms
9 days agoHandshake completed553 ms
12 days agoHandshake completed201 ms
13 days agoHandshake completed555 ms
15 days agoHandshake completed769 ms
16 days agoHandshake completed674 ms
17 days agoHandshake completed220 ms
19 days agoHandshake completed576 ms
19 days agoHandshake completed538 ms
20 days agoHandshake completed588 ms
21 days agoHandshake completed576 ms
22 days agoHandshake completed202 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 Tetrees MCP and makes no claim about it beyond what these checks measured.