Every tool call.
Visible.
Aperture wraps your MCP server in minutes — logging inputs, outputs, and silent failures so you stop flying blind.
How it works
Three steps to full visibility.
Wrap your server
Drop Aperture's proxy in front of any MCP server. One config change, no agent edits required.
# before
MCP_SERVER_URL=http://localhost:3001
# after — one line change
MCP_SERVER_URL=http://aperture.proxy/your-serverWatch every call
Every tool invocation is logged: inputs, outputs, latency, and whether it actually returned something real.
Ship with confidence
Flag silent failures before your users do. Know exactly what broke and when.
Why Aperture
Built for the server side.
Silent failures are the #1 MCP debugging problem.
Tool calls that return nothing, malformed outputs, unhandled errors — they fail without a trace. Your agents keep running, your users get broken experiences, and you have no idea. Aperture catches them all.
→ tool: search_index → response: { }
→ tool: run_query → response: null
→ tool: get_record → timeout: 5001ms
Read-only. No trust required.
In watch mode, Aperture never routes your traffic. It observes from the edge. Zero credential risk.
Built for the server side.
Your customer is the builder. Aperture shows them the revenue they're leaving on the table before asking them to flip billing on.
Pricing
Free while it matters most.
Full observability, no credit card.
Aperture Early Access
Get read-only MCP observability while it's free. Log every tool call, surface silent failures, and see your usage in real-time. Billing and auth switches come later — for now, just watch.
- Unlimited tool call logging
- Silent failure detection
- Real-time usage dashboard
- One-line proxy setup
No credit card required. Billing switches come later.