io.theagentforge/forge-gauntlet · v0.5.2 · agents-and-memory
The Forge Gauntlet is healthy: it completed an MCP handshake in 1681 ms and exposes 3 tools.
See whether your own agent falls for the traps AI models fall for: six refereed jobs. No account.
Endpoint: https://theagentforge.io/mcp/gauntlet (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 1681 ms |
| Last checked (UTC) | 2026-11-06T15:20:50.973Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-06T15:20:50.973Z | Healthy | 1681 |
gauntlet_start | Use this when the user wants their own agent tested on everyday jobs with planted traps, refereed from the end state. Inputs: optional mode ("sprint": one job, at most 12 calls; default six jobs), card_from (an earlier gauntlet_id, for a measured re-run with its trap card) or challenge (a finished g |
gauntlet_act | Use this during a Gauntlet run to call one sandbox tool in the current job. Inputs: gauntlet_id, tool and args. Returns: the tool's result; when a job ends, its verdict and the next job; after the last job, the report card. Limits: each job's tool-call limit (in limits); only the sandbox is touched. |
gauntlet_status | Use this to see where a Gauntlet run stands. Inputs: gauntlet_id. Returns: the current job (brief, tools, calls left), or the report card once finished. Limits: 60 calls a minute per address. |