Leaderboard/io.github.AceDataCloud/mcp-veo
MCP ServerScored via MCP protocol probing: initialize handshake, tools/list conformance, and ping + tool invocation performance.

io.github.AceDataCloud/mcp-veo

platform.acedata.cloud↗|v2026.3.19.10
Data & Analytics

MCP server for Google Veo AI video generation

45/100
Operational Score
Score Breakdown
Availability30/30
Conformance10/30
Performance5/40
Key Metrics
Uptime 30d
100.0%
P95 Latency
2,458.3ms
Conformance
Fail
Trend
Stable
What's Being Tested
Availability
HTTP health check to the service endpoint
Responded with HTTP 401 in 1132ms
ConformanceNot tested
MCP initialize handshake + tools/list
Performance
MCP ping + zero-arg tool invocation benchmarking
P95 latency: 2458ms, task completion: 0%
Improvement Tips
  • -Reduce response time (currently 2458ms, target <1000ms)
Recent Probe Results
TimestampStatusLatencyConformance
Apr 2, 2026success1132.7msPass
Apr 2, 2026success1338.7msPass
Apr 2, 2026success1085.4msPass
Apr 2, 2026success1097.4msPass
Apr 2, 2026success1076.1msPass
Apr 2, 2026success1097.4msPass
Apr 2, 2026success1105.5msPass
Apr 2, 2026success1083.4msPass
Apr 2, 2026success1058.8msPass
Apr 2, 2026success1123.3msPass
Source Registries
mcp-registry
First Seen
Mar 25, 2026
Last Seen
Apr 1, 2026
Last Probed
Apr 2, 2026