Remote MCP · Endpoint

dev.turva/turva-mcp MCP server

No. dev.turva/turva-mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.turva.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.turva/turva-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
213 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only MCP server for turva.dev, an agent-readiness audit and advisory service.
Listing
From the official MCP registry (active).
Recent checks of dev.turva/turva-mcp
CheckedResultHandshake
1 hour agoHandshake completed213 ms
2 days agoHandshake completed168 ms
4 days agoHandshake completed162 ms
5 days agoHandshake completed178 ms
7 days agoHandshake completed139 ms
8 days agoHandshake completed310 ms
9 days agoHandshake completed156 ms
12 days agoHandshake completed183 ms
13 days agoHandshake completed162 ms
15 days agoHandshake completed130 ms
16 days agoHandshake completed137 ms
18 days agoHandshake completed286 ms
19 days agoHandshake completed138 ms
20 days agoHandshake completed144 ms
20 days agoHandshake completed154 ms
21 days agoHandshake completed143 ms
22 days agoHandshake completed156 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with dev.turva/turva-mcp and makes no claim about it beyond what these checks measured.