01
Create a project
You get a proxy URL and an upstream field. Point it at the MCP server you already run.
MCP · APIs · function calls
Monitor every MCP tool call in 60 seconds — paste one URL, no SDK.
Put the agentstools proxy in front of your remote MCP server. We record each tool call — name, latency, status or error, optional token cost — and surface loops, error spikes, and cost blowups. Auth headers, including OAuth, pass through.
Free tier: 10,000 tool calls / month, 7-day retention.
How it works
Three steps. No instrumentation sprint.
Built for teams that already have a remote MCP server and do not want to wrap every client in an SDK first.
02
Paste the proxy URL
In Cursor, Claude, or your agent runtime, replace the remote MCP URL with the agentstools URL. Keep your existing auth headers.
03
Watch the stream
Tool name, latency, and errors land on the dashboard. Alerts fire when something loops or the bill jumps.
Features
What we store, what we watch.
Hosted MCP proxy
No-code path: one URL in front of a remote MCP server. Streaming passthrough, including OAuth and Authorization headers.
Call log that stays small
Default is metadata only — tool name, latency, status, error class, optional token cost. Payloads are opt-in.
Loop and error alerts
Catch the agent that retries the same tool 40 times, or a sudden 5xx spike, before it becomes a support thread.
Cost blowup watch
When a tool reports token cost, we sum it. Set a threshold; get email or Slack instead of a surprise invoice.
SDK and OTel later
Same ingest for npm i agentstools and OpenTelemetry.
Start with the proxy; add an SDK only if you want it.
Cloudflare-native
Workers, D1, Queues, Turnstile. Paddle is the merchant of record. Resend sends transactional mail.
Comparison
Proxy first, SDK optional.
SDK-based monitors are a good fit when you already own the agent process. They are a slower start when the MCP server is a URL you do not want to wrap.
| agentstools hosted proxy | SDK-only monitoring | |
|---|---|---|
| Time to first signal | About a minute: paste a URL | Requires a code change in every agent |
| Remote MCP servers | Works in front of an existing HTTP/SSE MCP | Only sees calls the SDK is compiled into |
| Auth | Passthrough, including OAuth headers | Depends on how the app was instrumented |
| Local stdio MCP | CLI wrapper planned | Usually covered if the host process has the SDK |
| Default data stored | Metadata only | Often full payloads unless you configure redaction |
Paste one URL. Watch every tool call.
Free tier is live. Questions: support@agentstools.com