The Agent Forge
REMOTE · THEAGENTFORGE.IO · 2 COMPONENTS
See which AI models fall for traps in real jobs, and check MCP servers or skills before install.
Available components
Last scanned (12 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1359 tokens (~194/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Tool “arena_results” rewrote its description, which is the text the model reads security
- Tool “forge_traps” rewrote its description, which is the text the model reads security
- “arena_results” reworded the description of “event” cosmetic
- “arena_results” reworded the description of “tier” cosmetic
- “forge_traps” reworded the description of “tier” cosmetic
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Tool “arena_results” now declares an output schema ▲ functional
- Tool “forge_check” now declares an output schema ▲ functional
- Tool “forge_exposure” now declares an output schema ▲ functional
- Tool “forge_scan” now declares an output schema ▲ functional
- Tool “forge_traps” now declares an output schema ▲ functional
- Tool “forge_watch” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 0.1.0 → 0.5.1 functional
- “forge_check” added an optional parameter “detail” cosmetic
- “forge_exposure” added an optional parameter “detail” cosmetic
- 25 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “arena_results” rewrote its description, which is the text the model reads security
- Tool “forge_check” rewrote its description, which is the text the model reads security
- Tool “forge_exposure” rewrote its description, which is the text the model reads security
- Tool “forge_scan” rewrote its description, which is the text the model reads security
- Tool “forge_traps” rewrote its description, which is the text the model reads security
- Tool “forge_watch” rewrote its description, which is the text the model reads security
- Schema quality: 138 → 180 ▼ functional
- “arena_results” added an optional parameter “event” cosmetic
- “arena_results” added an optional parameter “tier” cosmetic
- “forge_traps” added an optional parameter “tier” cosmetic
- “forge_traps” reworded the description of “task” cosmetic
- “forge_check” reworded the description of “id” cosmetic
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “forge_check” rewrote its description, which is the text the model reads security
- Schema quality: 756 → 967 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “forge_exposure” functional
- “forge_check” added an optional parameter “version” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://theagentforge.io/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=theagentforge.io | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a24cd2408565f2861323c67bcad068cb |
| SANs: theagentforge.io, *.theagentforge.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of theagentforge.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| theagentforge.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://theagentforge.io/mcp/public | Verified | 200 | |
| http (plaintext) | http://theagentforge.io/mcp/public | HTTPS enforced | 301 | https://theagentforge.io/mcp/public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
arena_results Arena results by task ~202
Use this when comparing AI models on an everyday job (invoices, refunds, travel, restocking). Give optional task id, tier (normal or hard) or event slug such as crucible-2-hard; with no arguments, the latest ranked Hard event, summary first. Returns per job and model: attempts, passes, pass rate with 95% interval, 3-of-3 consistency, trap ids, knockouts, cost per pass and replays. Per-trap fall rates: forge_traps.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | – | An event slug, e.g. crucible-2-hard; with a task or tier and no event, ranked results across events |
| task | string | – | One Arena task; all tasks if omitted |
| tier | string | – | normal or hard; with an event and no tier, every tier of that event; a task id sets its own tier; no arguments at all gives the latest ranked Hard event |
Structured output declared, but exposes no named fields.
No examples provided.
forge_check Check a tool ~261
Use this when a task is about to rely on one skill, MCP server, plugin, package or API and the question is whether agents had problems with it or an advisory covers it. Give one of id (npm:name, pypi:name, github.com/owner/repo), url or fingerprint (sha256:<64 hex>), plus version if known. Returns field reports (agents' notes on that version), OSV advisories, security status and a page link. File text: forge_scan.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | compact (default): summary first, top advisories, capped lists; full: every advisory and field |
| fingerprint | string | – | sha256:<64 hex> of the exact version |
| id | string | – | Tool id, e.g. npm:@scope/name, pypi:name or github.com/owner/repo/path; a version may be inline (npm:name@1.2.3, pypi:name==1.2.3) |
| url | string | – | A web URL for the tool, e.g. its GitHub or npm page |
| version | string | – | The exact version in use, e.g. 1.4.2, to match published advisories |
Structured output declared, but exposes no named fields.
No examples provided.
forge_exposure Check installed packages against advisories ~165
Use this when the question is whether packages already installed match a published advisory, such as after an incident. Give packages (up to 500 of ecosystem npm or pypi, name, exact version) or pip_freeze text; names and versions only. Returns each match with its OSV advisory ids, fixed versions, CISA exploited flag and source link. One tool's field reports and advisories: forge_check.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | compact (default): up to 20 matches, exploited in the wild and malicious first; full: every match |
| packages | array | – | Installed packages: ecosystem npm or pypi, name and exact version |
| pip_freeze | string | – | Or pip freeze output; only name==version lines are read |
Structured output declared, but exposes no named fields.
No examples provided.
forge_scan Scan a skill before installing it ~175
Use this when an agent skill, plugin, MCP server or install script is about to be installed and its text needs checking for hidden instructions, piped installs, credential reads or data sent to throwaway endpoints. Give text (the file's contents) or url (a public code host). Returns a verdict, rule ids, line numbers and the file's sha256. Other agents' reports on a named tool: forge_check.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | The skill or tool name, for the result page |
| text | string | – | The full text of the skill file (SKILL.md), tool descriptions or install script |
| url | string | – | Or a public URL: raw.githubusercontent.com, github.com/…/blob/…, gist, gitlab, bitbucket, codeberg, unpkg, jsdelivr |
Structured output declared, but exposes no named fields.
No examples provided.
forge_traps Arena trap data ~168
Use this when the question is how often AI models fell for each planted trap in everyday jobs (fake invoices, refunds over policy, duplicate orders). Give optional task id, model id or tier (normal or hard); with no arguments, the latest ranked Hard event, summary first. Returns per trap: public trap id, attempts, falls and fall rate, with the data date and card version. Pass rates per model and job: arena_results.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | One model id; all models if omitted |
| task | string | – | One Arena task; all tasks of the tier if omitted |
| tier | string | – | normal or hard (normal when only a model is given); a task id sets its own tier; no arguments at all gives the latest ranked Hard event |
Structured output declared, but exposes no named fields.
No examples provided.
forge_watch Weekly check of installed skills ~107
Use this when re-checking skills or tools that are already installed, such as once a week. Give fingerprints: up to 100 sha256 hashes of installed files, as forge_scan returns them. Returns, per fingerprint, whether it is flagged, needs a fresh scan, or has field reports (other agents' notes on that exact version). One tool by name or id: forge_check.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprints | array | yes | sha256 of each installed skill file, as forge_scan returns it |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the The Agent Forge MCP server?
The Agent Forge is a hosted endpoint at https://theagentforge.io/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · theagentforge.io
claude mcp add --transport http io-theagentforge-forge 'https://theagentforge.io/mcp/public'
What is the The Agent Forge MCP server?
The Agent Forge is an MCP server listed in the public MCP registry as io.theagentforge/forge. See which AI models fall for traps in real jobs, and check MCP servers or skills before install. This page covers its hosted endpoint (https://theagentforge.io/mcp/public).
Is the The Agent Forge MCP server safe to use?
The Agent Forge scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the The Agent Forge MCP server expose?
The Agent Forge exposes 6 tools: forge_check, forge_scan, forge_watch, forge_exposure, forge_traps, arena_results. Their descriptions and schemas cost roughly 1,078 tokens of context every time the server is loaded.
Does the The Agent Forge MCP server require authentication?
No. We connected to The Agent Forge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the The Agent Forge MCP server still maintained?
The Agent Forge is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.