Remote MCP · Endpoint

MCP security checks — WARDEN and HISTOR MCP server

No. MCP security checks — WARDEN and HISTOR answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://modelmarket.dev/tools/mcp/security

The last check completed an MCP handshake.

Registry name
dev.modelmarket/mcp-security
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
95 ms
Tools exposed
4 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Scan MCP tool definitions for poisoning, look up server history, count tool-list tokens. Free.
Website
https://modelmarket.dev/tools/
Repository
https://github.com/alexar76/warden
Listing
From the official MCP registry (active).
Recent checks of MCP security checks — WARDEN and HISTOR
CheckedResultHandshake
34 minutes agoHandshake completed95 ms
9 days agoHandshake completed42 ms
10 days agoHandshake completed45 ms
11 days agoHandshake completed48 ms
12 days agoHandshake completed53 ms
14 days agoHandshake completed40 ms
14 days agoHandshake completed49 ms
15 days agoFailed - the request timed out—
17 days agoHandshake completed50 ms
19 days agoHandshake completed14 ms
21 days agoHandshake completed16 ms
24 days agoHandshake completed16 ms
26 days agoHandshake completed19 ms

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

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 MCP security checks — WARDEN and HISTOR and makes no claim about it beyond what these checks measured.