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

AgentBodega MCP

NPM · @AGENTBODEGA/MCP · SCANNED AUG 3

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

Available components

−15 this week 81 Trust /100
Trust breakdown (6 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 →

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 27 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @agentbodega/mcp

# add to Claude Code
claude mcp add agentbodegastore-agentbodega-mcp -- npx -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"]
// 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.

  • 2 Aug 26 +15
    • Malware scan: unverified → pass security
  • 31 Jul 26 −12
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 +37
    • Tool coverage: unverified → 100 functional
    • Schema quality: unverified → 100 functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
  • 26 Jul 26 59

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/@agentbodega/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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
Discovery method:
attestation_endpoint
Dependencies 0 packages

0 packages in the resolved dependency tree.

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.

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.