Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentBodega MCP

NPM · @AGENTBODEGA/MCP · SCANNED SEP 20

Discover AgentBodega paid data tools, contracts, and x402/L402 HTTP payment handoff metadata.

Available components

0 this week 95 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to agentbodegastore/agentbodega). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 75 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 844 tokens (~93/item across 9 items; 5 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the AgentBodega MCP server?

AgentBodega MCP runs locally as an npm package, launched with npx -y @agentbodega/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @agentbodega/mcp

# add to Claude Code
claude mcp add agentbodegastore-agentbodega-mcp -- npx -y @agentbodega/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "agentbodegastore-agentbodega-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentbodega/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "agentbodegastore-agentbodega-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentbodega/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add agentbodegastore-agentbodega-mcp -- npx -y @agentbodega/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agentbodegastore-agentbodega-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@agentbodega/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add agentbodegastore-agentbodega-mcp --command npx --arg -y --arg @agentbodega/mcp
# ~/.hermes/config.yaml
mcp_servers:
  agentbodegastore-agentbodega-mcp:
    command: "npx"
    args: ["-y", "@agentbodega/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "agentbodegastore-agentbodega-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@agentbodega/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add agentbodegastore-agentbodega-mcp -t stdio -c npx -a -y @agentbodega/mcp
// mcp.json
{
  "mcpServers": {
    "agentbodegastore-agentbodega-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentbodega/mcp"
      ]
    }
  }
}
Changelog

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.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
  • 14 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 13 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 20 Sept 2026 · Analysed npm/@agentbodega/mcp@0.1.7

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo agentbodegastore/agentbodega
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/agentbodegastore/agentbodega/.github/workflows/npm-publish.yml@refs/tags/mcp-v0.1.7
Rekor log index 2085143008
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:f7e8f2d2fa806b0e8a815530ae2e4a44441ae92fc045afe0070e2fe40ad325d4fb1d4b51bea5975b8fcec3b070812612a0622f1330f766e5574e1a609

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~740 tokens

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 →

Tool Tokens
agentbodega_call_snippet ~110

Use this after selecting an endpoint to prepare an HTTP request an agent or user can run outside MCP. It returns curl and JavaScript snippets with the example JSON body, an X-PAYMENT placeholder, and x402 verification notes. It does not fetch a live 402 challenge, spend funds, or execute the paid call.

NameTypeReqDescription
endpointstringyesEndpoint identifier from search_catalog or get_endpoint. Accepts the endpoint key, title, API path, or full AgentBodega URL.

No output schema declared.

No examples provided.

agentbodega_get_endpoint ~148

Use this after search_catalog when you know the endpoint key, title, path, or URL and need the complete contract before paying. It returns method, URL, price, category, tags, long description, required inputs, input/output schemas, example request, and output example when available. It does not call the paid endpoint.

NameTypeReqDescription
endpointstringyesEndpoint identifier from search_catalog. Accepts the endpoint key, title, API path such as /api/status/github, or full AgentBodega URL.
includeSchemasbooleanWhen true, return the full contract with schemas, examples, and long description. When false, return a compact summary suitable for ranking candidate endpoints.

No output schema declared.

No examples provided.

agentbodega_payment_guide ~107

Use this when an agent needs to understand how AgentBodega x402 and L402 payment discovery work before making paid HTTP calls. It explains the blockchain-settled per-call model, discovery URLs, balance source of truth, optional owner-approved savings offers, and an optional sample challenge request. It does not validate wallets, issue discounts, or perform payments.

NameTypeReqDescription
includeCurlbooleanWhen true, include a sample curl command for requesting a live 402 payment challenge.

No output schema declared.

No examples provided.

agentbodega_plan_task ~172

Use this before search_catalog when you have a plain-language task and want AgentBodega to choose the best matching paid route at the lowest useful cost. It calls the free /api/plan planner, returns a recommended endpoint, alternatives, required inputs, examples, and x402 handoff notes. It never executes paid endpoints or creates payments.

NameTypeReqDescription
budgetUsdnumberOptional maximum per-call spend for the recommended paid route. The planner itself remains free.
limitintegerMaximum number of recommendations to return.
preferstringRanking preference for route selection.
taskstringyesPlain-language task to solve with AgentBodega routes, for example: check whether my deploy failure is caused by GitHub, npm, Vercel, Supabase, or OpenAI.

No output schema declared.

No examples provided.

agentbodega_search_catalog ~203

Use this first when you need to choose an AgentBodega paid data endpoint. It fetches the live directory and returns matching endpoint summaries with key, path, price, category, tags, required inputs, and example request. It never executes paid endpoints or creates x402 payments.

NameTypeReqDescription
departmentstringOptional exact category or tag filter, for example public-data, cloud-status, x402-tools, billing, search, or utility. Leave empty when you do not know the department.
limitintegerMaximum number of matching endpoint summaries to return. Values are clamped to 1 through 50.
maxPriceUsdnumberOptional maximum per-call price in USD. Use this to find low-cost endpoints before preparing a paid request.
querystringOptional case-insensitive text search across endpoint key, title, path, descriptions, category, and tags. Use an empty string to list all endpoints before applying filters.

No output schema declared.

No examples provided.

Common questions

What is the AgentBodega MCP server?

AgentBodega MCP is listed in the public MCP registry as io.github.agentbodegastore/agentbodega-mcp. Discover AgentBodega paid data tools, contracts, and x402/L402 HTTP payment handoff metadata. This page covers its npm package (@agentbodega/mcp).

Is the AgentBodega MCP server safe to use?

AgentBodega MCP scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 AgentBodega MCP server expose?

AgentBodega MCP exposes 5 tools: agentbodega_plan_task, agentbodega_search_catalog, agentbodega_get_endpoint, agentbodega_call_snippet, agentbodega_payment_guide. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.

Is the AgentBodega MCP server still maintained?

AgentBodega MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the AgentBodega MCP server under?

AgentBodega MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.