Remote MCP · Endpoint

Intesta MCP server

No. Intesta answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://intesta.io/mcp

The last check completed an MCP handshake.

Registry name
io.intesta/registry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Trust registry for agents: check_trust verdict A0-A4, signed fact passports, honest refusals.
Listing
From the official MCP registry (active).
Recent checks of Intesta
CheckedResultHandshake
5 hours agoHandshake completed290 ms
2 days agoHandshake completed321 ms
4 days agoHandshake completed402 ms
5 days agoHandshake completed299 ms
7 days agoHandshake completed317 ms
8 days agoHandshake completed302 ms
9 days agoHandshake completed315 ms
12 days agoHandshake completed311 ms
13 days agoHandshake completed295 ms
15 days agoHandshake completed400 ms
16 days agoHandshake completed288 ms
17 days agoHandshake completed292 ms
18 days agoHandshake completed292 ms
19 days agoHandshake completed307 ms
20 days agoHandshake completed290 ms
21 days agoHandshake completed300 ms
22 days agoHandshake completed340 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 Intesta and makes no claim about it beyond what these checks measured.