Live MCP intelligence

Know which MCP servers actually work.

Protocol-aware monitoring, real uptime history, and transparent capability checks — without marketplace noise.

Try “docs” or “real estate”Browse the full directory →

40,297active Registry servers

22,558public remote endpoints

15with current aggregates

3 layersin every complete check

Fresh observations

Recently checked servers

Real protocol results, clearly separated from Registry metadata.

View all servers

AdWeave — Meta Ads MCP Serverai.adweave/meta-ads-mcp · streamable-http Auth required 341 msLatency —24h uptime AgentMeshai.agentmesh/mesh · streamable-http Auth required 546 msLatency —24h uptime AdAdvisor MCP Serverai.adadvisor/mcp-server · streamable-http Auth required 370 msLatency —24h uptime Propick Integration MCPae.propick/propick · streamable-http Auth required 227 msLatency —24h uptime adsideai.adside/adside · streamable-http Auth required 452 msLatency —24h uptime Projectoryae.projectory/mcp · streamable-http Operational 378 msLatency 100%24h uptime

What we test

More than an HTTP ping.

An endpoint is not called operational simply because it returned a web response.

01

Reachability

HTTPS, connection timing, timeout, and sanitized network errors.

02

MCP handshake

Modern discovery or legacy initialization with negotiated protocol version.

03

Capability check

Safe tools/list, tool count, and normalized schema hash. No tool execution.