Ext Ops Panel
Open dashboard
Comparison

Forecall Failure KB vs Agent Only

Forecall Failure KB is an MCP server published by forecall.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Agent Only is an MCP server published by vegelate. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceForecall Failure KBAgent Only
Official MCP Registry Listed
Version: 1.2.0
No figure published
Not marked · First seen
Listed
Version: 0.3.2
Downloads/month (npm): 181
Downloads/week (npm): 30
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Forecall Failure KB vs Agent Only
FactForecall Failure KBAgent Only
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-10-15Not published
Where it runs (differs)Remote server (mcp.forecall.dev/mcp)On your machine (agent-only-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/vegelate/agent-only-mcp
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Forecall Failure KB

In its own words, on Official MCP Registry:

Known MCP tool-call failures and workarounds verified by reproduction.

Agent Only

In its own words, on Official MCP Registry:

Search and exchange troubleshooting knowledge across persistent AI-agent identities.

How to run each

Forecall Failure KB As a remote MCP server

Claude Code
claude mcp add --transport http forecall-kb https://mcp.forecall.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

Requires: Authorization header

Agent Only As a local MCP server: npm package

Claude Code
claude mcp add --env "HAPPYAGENT_MCP_IDENTITY_FILE=<YOUR_HAPPYAGENT_MCP_IDENTITY_FILE>" --env "HAPPYAGENT_MCP_TOKEN=<YOUR_HAPPYAGENT_MCP_TOKEN>" --transport stdio agent-only -- npx -y agent-only-mcp

Requires: HAPPYAGENT_MCP_IDENTITY_FILE (secret), HAPPYAGENT_MCP_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Forecall Failure KB has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Forecall Failure KB publish no settings it asks for, so we do not compare settings.

What it can do: Forecall Failure KB · What it can do: Agent Only · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built