MCP ACTIVATION LAB / BROWSER-LOCAL
Your MCP server was discovered.
Why was no tool called?
Inspect the static handoff from initialize to the first useful action. The result identifies friction; it does not predict conversion or execute a tool.
LOCAL
Source stays in this browser
No account · no upload · deterministic rules
OBSERVED H/M TRAFFIC / 30 DAYS
Discovery-to-use gap
Loading aggregate production evidence...
01 / INPUT
Inspect the activation handoff
Paste JSON-RPC results or plain result objects. Analysis runs locally.
02 / RESULT
Static activation path
Static friction--
FIRST GAP
--
- First-value tool
- --
- Tools observed
- --
- Payment boundary
- --
NEXT ACTIONS
Fix in this order
03 / CATALOG
Tool activation facts
Annotations are untrusted client hints, not enforcement.
| Tool | Required inputs | Structured result | Read-only / closed | Payment-like |
|---|
04 / REMEDIATION
Deterministic implementation kit
Generated from observed metadata, not from a model.
Initialize instructions
First-value tool
Server card checklist
Payment boundary
PORTABLE RESULT
Export without raw input or descriptionsEVIDENCE BOUNDARY
What this result does not prove
- No tool was executed and no successful outcome was observed.
- This is not a security, compliance or identity verdict.
- Static friction is not a conversion probability.
- The benchmark describes H/M traffic, not the global MCP ecosystem.