Skip to main content
Glama
agentbodegastore

AgentBodega MCP

Official
by agentbodegastore
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

AgentBodega MCP

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.

Related MCP server: x402-mcp

Install

npx @agentbodega/mcp

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

https://agentbodega.store/mcp

SSE endpoint:

https://agentbodega.store/mcp/sse

Optional environment:

AGENTBODEGA_BASE_URL=https://agentbodega.store

Standalone agent skill:

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

{
  "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

npm install
npm test

Available Tools

4 tools
agentbodega_call_snippetGenerate AgentBodega Call SnippetA

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
endpointYesEndpoint identifier from search_catalog or get_endpoint. Accepts the endpoint key, title, API path, or full AgentBodega URL.

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses what the tool returns (curl/JavaScript snippets with JSON body, X-PAYMENT placeholder, x402 notes) and what it does not do (no live challenge, no execution). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-load the purpose and context. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple single-parameter tool with full schema description and no output schema, the description adequately explains output and limitations. No missing information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'endpoint' is well-described in the input schema (accepts various formats). The description adds no extra meaning beyond the schema, and schema coverage is 100%, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it generates curl and JavaScript snippets for preparing an HTTP request after selecting an endpoint. It distinguishes itself from sibling tools like search_catalog, get_endpoint, and payment_guide by focusing on snippet generation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use after selecting an endpoint and lists exclusions: does not fetch live 402 challenge, spend funds, or execute the paid call. Provides clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

agentbodega_get_endpointGet AgentBodega EndpointA

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.

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

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description carries the full burden. It transparently explains that the tool does not call the paid endpoint and returns specific fields. No contradictions or omissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with four sentences: purpose, return content, and a disclaimer. No redundant information, well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple input schema and no output schema, the description covers all essential aspects: when to use, what it returns, and limitations. It does not describe error handling, but that is acceptable for this level of detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions, but the description adds value by clarifying the acceptable formats for the endpoint parameter (key, title, path, URL) and the effect of includeSchemas on the response verbosity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states the tool's purpose: to retrieve the complete contract of an endpoint known from search_catalog before paying. It lists what it returns and distinguishes from sibling tools by specifying it is used after search_catalog and does not call the paid endpoint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly states when to use the tool: after search_catalog, when you know the endpoint identifier and need the full contract. It implies not to use it for searching or calling. It could benefit from explicitly stating when not to use, but the context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

agentbodega_payment_guideAgentBodega Payment GuideA

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

ParametersJSON Schema
NameRequiredDescriptionDefault
includeCurlNoWhen true, include a sample curl command for requesting a live 402 payment challenge.

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description carries full burden. It is fully transparent about being an informational guide, listing exactly what it explains (discovery, settlement, model, sample) and what it does not do, with no destructive or mutative behavior implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with front-loaded usage instruction. Every sentence adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

As an informational guide with no output schema, the description sufficiently covers the tool's scope, content, and limitations for an agent to decide when to invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter (includeCurl). The tool description does not add extra meaning beyond the schema, but the schema itself is clear, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to explain AgentBodega x402 payment discovery and settlement before making paid HTTP calls. It distinguishes itself from sibling tools like agentbodega_call_snippet which actually make calls, and agentbodega_search_catalog which searches endpoints.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('before making paid HTTP calls') and what it does not do ('does not validate wallets, create discounts, or perform payments'), providing clear guidance on appropriate contexts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

agentbodega_search_catalogSearch AgentBodega CatalogA

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of matching endpoint summaries to return. Values are clamped to 1 through 50.
queryNoOptional case-insensitive text search across endpoint key, title, path, descriptions, category, and tags. Use an empty string to list all endpoints before applying filters.
departmentNoOptional 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.
maxPriceUsdNoOptional maximum per-call price in USD. Use this to find low-cost endpoints before preparing a paid request.

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses the key behavioral trait: the tool is read-only and has no side effects ('never executes paid endpoints or creates x402 payments'). This is essential for an agent to use it safely. However, it does not mention rate limits, authentication needs, or error behavior, which would be beneficial for completeness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. The first sentence states the primary use case, and the second explains what the tool does and its safety. Every word earns its place, making it highly concise and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description covers the essential context: what the tool does, when to use it, and its read-only nature. The sibling tools list helps with differentiation. However, it could mention what to do after receiving results (e.g., use other tools for details or execution), but the core use case is well handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters have descriptions in the input schema (100% coverage), so the description adds little beyond the schema. The description contextualizes the parameters by stating the tool fetches a live directory and returns summaries, but it does not provide additional semantic details for individual parameters. Baseline 3 is appropriate when schema already documents parameters well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Use this first when you need to choose an AgentBodega paid data endpoint.' It specifies the action (search/fetch directory), the resource (AgentBodega catalog), and what it returns (summaries with key, path, price, etc.). It differentiates from siblings by noting it never executes endpoints, which is a key distinction from agentbodega_call_snippet.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: 'Use this first when you need to choose an AgentBodega paid data endpoint.' It also states when not to use it: 'It never executes paid endpoints or creates x402 payments,' implying a different tool for execution. This gives clear context for when to invoke this tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updatesv0.1.1
    • Changedagentbodega_call_snippet1 field changed
      • changedInput schema / properties / endpoint / description
        Before
        "Endpoint key, title, path, or full URL."
        After
        "Endpoint identifier from search_catalog or get_endpoint. Accepts the endpoint key, title, API path, or full AgentBodega URL."
    • Changedagentbodega_get_endpoint2 fields changed
      • changedInput schema / properties / endpoint / description
        Before
        "Endpoint key, title, path, or full URL."
        After
        "Endpoint identifier from search_catalog. Accepts the endpoint key, title, API path such as /api/status/github, or full AgentBodega URL."
      • addedInput schema / properties / includeSchemas / description
        "When true, return the full contract with schemas, examples, and long description. When false, return a compact summary suitable for ranking candidate endpoints."
    • Changedagentbodega_payment_guide1 field changed
      • addedInput schema / properties / includeCurl / description
        "When true, include a sample curl command for requesting a live 402 payment challenge."
    • Changedagentbodega_search_catalog4 fields changed
      • changedInput schema / properties / department / description
        Before
        "Optional category/tag filter such as public-data, cloud-status, x402-tools, or billing."
        After
        "Optional 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."
      • addedInput schema / properties / limit / description
        "Maximum number of matching endpoint summaries to return. Values are clamped to 1 through 50."
      • changedInput schema / properties / maxPriceUsd / description
        Before
        "Optional maximum USD price."
        After
        "Optional maximum per-call price in USD. Use this to find low-cost endpoints before preparing a paid request."
      • changedInput schema / properties / query / description
        Before
        "Text to search across names, descriptions, tags, and URLs."
        After
        "Optional case-insensitive text search across endpoint key, title, path, descriptions, category, and tags. Use an empty string to list all endpoints before applying filters."
  2. 4 tool updatesv0.1.0
    • First observedagentbodega_call_snippet
    • First observedagentbodega_get_endpoint
    • First observedagentbodega_payment_guide
    • First observedagentbodega_search_catalog
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose in the workflow: search catalog, get endpoint details, payment guidance, and code snippet generation. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent 'agentbodega_verb_noun' pattern using snake_case, making them predictable and easy to understand.

Tool Count5/5

With 4 tools, the set is well-scoped for the server's goal of guiding users through paid endpoint discovery and preparation. No tool feels extraneous or missing.

Completeness5/5

The tools cover the entire workflow from search to snippet generation, along with payment guidance. No obvious gaps given the server's stated purpose of not executing paid calls.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentbodegastore/agentbodega'

If you have feedback or need assistance with the MCP directory API, please join our Discord server