Ext Ops Panel
Open dashboard
Comparison

focxle — what your AI agents cost vs IBM Granite via x402

focxle — what your AI agents cost is an MCP server published by focxle.com. Marketplaces we read that list it: 1 (Official MCP Registry). IBM Granite via x402 is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplacefocxle — what your AI agents costIBM Granite via x402
Official MCP Registry Listed, marked deprecated
Version: 0.1.7
Downloads/month (PyPI): 122
Downloads/week (PyPI): 25
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.1.4
Downloads/month (npm): 152
Downloads/week (npm): 36
Forks (GitHub): 74
Stars (GitHub): 271
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

focxle — what your AI agents cost vs IBM Granite via x402
Factfocxle — what your AI agents costIBM Granite via x402
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)271 (better)
Forks (GitHub) (differs)0 (worse)74 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (focxle)On your machine (@three-ws/ibm-x402-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 09, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/focxle/focxle-pythongithub.com/nirholas/three.ws
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

focxle — what your AI agents cost

In its own words, on Official MCP Registry:

Ask what your AI agents cost. Per agent, across every vendor, from your editor.

IBM Granite via x402

In its own words, on Official MCP Registry:

x402 pay-per-use IBM Granite AI: chat, code, embeddings, analysis, forecasting. Pay USDC per call.

How to run each

focxle — what your AI agents cost As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio spend -- uvx focxle

IBM Granite via x402 As a local MCP server: npm package

Claude Code
claude mcp add --env "MCP_SVM_PAYMENT_ADDRESS=<YOUR_MCP_SVM_PAYMENT_ADDRESS>" --env "WATSONX_API_KEY=<YOUR_WATSONX_API_KEY>" --transport stdio ibm-x402-mcp -- npx -y @three-ws/ibm-x402-mcp

Requires: MCP_SVM_PAYMENT_ADDRESS, WATSONX_API_KEY (secret)

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

Tools each declares

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

Settings each asks for

Only focxle — what your AI agents cost asks for

  • FOCXLE_NO_HISTORY

Only IBM Granite via x402 asks for

  • MCP_SVM_PAYMENT_ADDRESS
  • WATSONX_API_KEY (secret)
  • WATSONX_EMBED_MODEL_ID
  • WATSONX_MODEL_ID
  • WATSONX_PROJECT_ID
  • WATSONX_SPACE_ID
  • WATSONX_URL
  • X402_FACILITATOR_URL
  • X402_FEE_PAYER_SOLANA

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: focxle — what your AI agents cost · What it can do: IBM Granite via x402 · 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