AgentBodega MCP

io.github.agentbodegastorePublished by GitHub account agentbodegastorev0.1.7Updated Nov 10, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant browse AgentBodega's catalog of paid data endpoints and get ready-to-run x402 payment handoff details without executing paid calls.

What you can do
The server exposes tools for searching a live directory of paid AgentBodega endpoints by text, category, or maximum USD price, and for retrieving a full endpoint contract including method, URL, price, required inputs, schemas, and examples. A planner tool recommends the cheapest useful route for a plain-language task, and a snippet tool generates curl and JavaScript requests with an X-PAYMENT placeholder. A payment guide explains the x402 and L402 discovery and settlement model. It also exposes catalog, x402, L402, and OpenAPI documents as resources.
When to use it
Use it when an assistant needs to find and compare paid data or research endpoints, understand their input and output contracts, or prepare x402 HTTP calls for a human or agent to run. It is a discovery and planning layer, not an execution layer.
Requirements
Runs locally over stdio, typically via npx @agentbodega/mcp, or can be reached as a remote Streamable HTTP or SSE endpoint. It needs outbound HTTPS access to the AgentBodega service; the optional AGENTBODEGA_BASE_URL environment variable overrides the default base URL. No authentication is declared.
Before you install
The server itself does not execute paid calls, but the endpoints it describes are paid and the generated snippets contain an X-PAYMENT placeholder, so any actual call spends money and should be reviewed first. It sends outbound HTTPS requests to AgentBodega at runtime to read live catalog and discovery documents, and the README notes L402 should be treated as discovery-only unless the live document reports a configured issuer.

Installation

In SourceWeft

  1. Open AgentBodega MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

AgentBodega MCP

[smithery badge]

Give agents a live menu of paid, x402-ready tools from AgentBodega.

This MCP server lets agents discover AgentBodega endpoints, compare prices, plan the cheapest useful route for a task, inspect required inputs and response formats, and generate ready-to-run x402 HTTP calls. Agents get the buying instructions for each resource without guessing schemas or scraping docs.

This public repository contains only the AgentBodega MCP package. The hosted AgentBodega API runs separately at agentbodega.store.

What Agents Can Find

  • Social media lookups and research tools.
  • Real-estate listing search.
  • Service status and cloud status checks.
  • Domain, launch-readiness, and agent-discoverability audits.
  • x402 inspection, directory packaging, and hosted artifact utilities.

The MCP server does not execute paid calls. It returns the endpoint contract, example request, payment requirements, and snippets an agent can run against the hosted API. L402 is exposed as an additional discovery and payment-handoff surface; agents should treat it as discovery-only unless the live L402 document reports a configured issuer.

Install

bash
npx @agentbodega/mcp

Remote MCP clients that support Streamable HTTP can connect directly to:

text
https://agentbodega.store/mcp

SSE endpoint:

text
https://agentbodega.store/mcp/sse

Optional environment:

bash
AGENTBODEGA_BASE_URL=https://agentbodega.store

Standalone agent skill:

bash
curl -sS https://raw.githubusercontent.com/agentbodegastore/agentbodega/main/agent-skills/agentbodega/SKILL.md

Network access

This package intentionally uses outbound HTTPS requests at runtime to read AgentBodega's live catalog, x402 discovery document, L402 discovery document, and OpenAPI contract. It does not run install scripts, spawn shells, bundle dependencies, or execute paid calls. By default it connects to https://agentbodega.store.

Claude Desktop

json
{  "mcpServers": {    "agentbodega": {      "command": "npx",      "args": ["-y", "@agentbodega/mcp"]    }  }}

Tools

  • agentbodega_plan_task - use first when an agent has a plain-language task and wants AgentBodega to choose the cheapest useful route. It calls the free /api/plan planner and returns a recommended endpoint, alternatives, required inputs, examples, and x402 handoff notes. It never executes paid calls.
  • agentbodega_search_catalog - use first to find the right paid endpoint. It searches the live directory by text, department/category/tag, and maximum USD price, then returns endpoint summaries with required inputs and example requests. It never executes paid calls.
  • agentbodega_get_endpoint - use after search when you know an endpoint key, path, title, or full URL. It returns the full contract: method, URL, price, required inputs, schemas, example request, output example, and long description. It does not call the endpoint.
  • agentbodega_call_snippet - use after selecting an endpoint to generate ready-to-edit curl and JavaScript requests with an X-PAYMENT placeholder and x402 verification notes. It does not fetch a challenge, pay, or execute.
  • agentbodega_payment_guide - use when an agent needs the AgentBodega payment model before making paid HTTP calls. It explains x402 discovery, L402 handoff status, settlement, blockchain-only balance policy, and optional challenge curl.

Resources

  • agentbodega://catalog - compact live catalog.
  • agentbodega://x402 - live x402 discovery document.
  • agentbodega://l402 - live L402 discovery document.
  • agentbodega://openapi - live OpenAPI document.

Development

bash
npm installnpm test

Source: README.md at commit 04e7bbb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.7LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts