- Who it helps
- Developers inspecting software that connects assistants to external tools.
- Availability
- Public measurement report dated October 31, checked November 1.
What was measured
The servers started without real credentials or an external network route. Seven requested hostnames absent from their package README. DNS pointed to loopback, so these observations do not show completed external connections.
MCP startup measurements: distinguish requests from completed connections ↗
What the comparison misses
The report lists 1,143 tools but invokes none. Its documentation check uses whole words in the package README, excluding linked references; ten READMEs are short. It explicitly disclaims a calibrated safety ranking. A server without a finding can still behave differently when tools run.
MCP startup measurements: distinguish requests from completed connections ↗
What you can do
- Read the measurement rules before interpreting an individual finding. Open reference ↗
Where the evidence stops
Report read; individual report link failed. Startup measurements were not reproduced and do not establish tool-call behavior.
Sources read. Primary sources checked November 1, 2026 UTC. No installation, model inference or end-to-end workflow executed.
Sources & further reading
Web · paper
MCP startup measurements: distinguish requests from completed connections ↗
Identifies the subject, documented capability or specific verification limit.
mcp.brydge-ai.com · page checked 2026-11-01
Coverage note: Independent attention and end-to-end execution remain unverified.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
Brydge records what 67 MCP servers request at startup, before any tool is called.