AgentBodega MCPofficial
A
licenseA
qualityD
maintenanceEnables agents to search and inspect live service offerings, generate x402 payment snippets, and understand blockchain-only balance policies.
4
80
3
MIT
agent-exec
Server Details
Accountless pay-per-use code execution for agents. Read-only search and pricing; pay via x402.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
2 toolssearch_listingsSearch the agent-exec directoryARead-onlyInspect
Free, unauthenticated search over agent-exec's directory of paid agent-facing services (same data as GET https://agent-exec.45.67.221.128.sslip.io/listings). Returns a page of listings and an opaque cursor for the next page.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter to listings carrying this tag. | |
| limit | No | Max listings to return (server-bounded regardless). | |
| cursor | No | Opaque pagination cursor from a previous call's nextCursor. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| error | No | |
| listings | No | |
| nextCursor | No |
TDQS
A4.5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavioral context beyond that: the operation is free and unauthenticated, and it returns a page of listings plus an opaque cursor for subsequent pages. This gives the agent a precise model of access requirements and pagination behavior.
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 zero waste. The first front-loads the core purpose and constraints (free, unauthenticated, directory of paid services), and the second conveys the return shape and pagination. Every sentence earns its place.
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?
For a simple, zero-required-parameter search tool with a full output schema and read-only annotations, the description is complete. It covers authentication, pagination, and data-source equivalence, while return-value details are left to the output schema as intended. No critical information is missing for correct invocation.
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 input schema already documents all three optional parameters with descriptions at 100% coverage, so the description adds no new parameter-level semantics. Per the calibration baseline, 3 is appropriate when the schema carries the full burden and the description merely references the cursor without elaborating further.
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 states a specific verb ('search') applied to a specific resource ('agent-exec's directory of paid agent-facing services') and explicitly equates the data to a named GET endpoint. This leaves no ambiguity about what the tool does and naturally distinguishes it from the sibling service_card, which appears to target a single listing.
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?
It provides clear context: use this for a free, unauthenticated search over the directory, and it notes the data is identical to a specific HTTP endpoint. It doesn't explicitly contrast this with service_card or state when not to use it, so it stops short of a 5, but the context is strong enough for an agent to make a sensible routing decision.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
service_cardagent-exec service cardARead-onlyInspect
What agent-exec sells, what it costs, and exactly where to send a plain-HTTP x402 payment to buy it. This tool call itself is free and moves no money -- MCP cannot carry an x402 402, so buying happens over plain HTTP at the URLs this returns, not through this MCP connection.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| quote | Yes | |
| execute | Yes | |
| llmsTxt | Yes | |
| network | Yes | |
| openapi | Yes | |
| payment | Yes | |
| service | Yes | |
| directory | Yes | |
| description | Yes |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations' readOnlyHint=true, the description explicitly discloses that the call itself is free, moves no money, and cannot carry an x402 402 over MCP. This is valuable behavioral context that prevents an agent from incorrectly attempting to complete a purchase through this tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences cover purpose, cost, payment channel, and the key limitation of MCP. The description is efficient and front-loaded, though the second sentence slightly restates the plain-HTTP point already implied in the first.
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?
For a zero-parameter, read-only informational tool with an output schema available, the description provides all critical context: what the tool returns, the fact that it is free, and the essential warning that payment must occur over plain HTTP rather than via MCP. Nothing needed for correct invocation is missing.
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?
The tool has zero parameters, so there is nothing for the description to explain. The baseline for a parameterless tool is 4, and no additional semantic burden falls on the description.
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: it returns what agent-exec sells, what it costs, and the exact URL for paying via x402. This distinguishes it from the sibling search_listings, which presumably discovers listings rather than providing purchase/payment details.
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 provides clear context: use this tool to get pricing and payment routing, and explicitly warns that actual purchase must happen over plain HTTP, not through MCP. It does not explicitly name search_listings as the alternative for browsing/finding listings, but the purpose is clear enough for correct tool selection.
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 tool update
- Changed
search_listings5 fields changed- added
Output schema / properties / listings / items / properties / consecutiveFailuresAdded value: +{ + "type": "number" +} - added
Output schema / properties / listings / items / properties / deadSinceAdded value: +{ + "type": [ + "number", + "null" + ] +} - added
Output schema / properties / listings / items / properties / evictsAtAdded value: +{ + "type": [ + "number", + "null" + ] +} - added
Output schema / properties / listings / items / properties / remedyAdded value: +{ + "type": [ + "string", + "null" + ] +} - changed
Output schema / properties / listings / items / requiredPrevious value: -[ - "url", - "name", - "description", - "tags", - "tier", - "lastSeenAlive", - "paidUntil", - "dead", - "lastProbeCode", - "operator" -]New value: +[ + "url", + "name", + "description", + "tags", + "tier", + "lastSeenAlive", + "paidUntil", + "dead", + "lastProbeCode", + "operator", + "consecutiveFailures", + "deadSince", + "evictsAt", + "remedy" +]
1 tool update
- Changed
search_listings2 fields changed- added
Output schema / properties / errorAdded value: +{ + "additionalProperties": false, + "properties": { + "code": { + "const": "LISTINGS_QUERY_INVALID", + "type": "string" + }, + "details": { + "additionalProperties": {}, + "type": "object" + }, + "message": { + "type": "string" + } + }, + "required": [ + "code", + "message", + "details" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "listings", - "nextCursor" -]
2 tool updates
- Changed
search_listings1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "listings": { + "items": { + "additionalProperties": false, + "properties": { + "dead": { + "type": "boolean" + }, + "description": { + "type": "string" + }, + "lastProbeCode": { + "type": [ + "string", + "null" + ] + }, + "lastSeenAlive": { + "type": [ + "number", + "null" + ] + }, + "name": { + "type": "string" + }, + "operator": { + "type": "boolean" + }, + "paidUntil": { + "type": [ + "number", + "null" + ] + }, + "tags": { + "items": { + "type": "string" + }, + "type": "array" + }, + "tier": { + "enum": [ + "free", + "paid" + ], + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "url", + "name", + "description", + "tags", + "tier", + "lastSeenAlive", + "paidUntil", + "dead", + "lastProbeCode", + "operator" + ], + "type": "object" + }, + "type": "array" + }, + "nextCursor": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "listings", + "nextCursor" + ], + "type": "object" +}
- Changed
service_card1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "description": { + "type": "string" + }, + "directory": { + "additionalProperties": false, + "properties": { + "listEndpoint": { + "type": "string" + }, + "listingIsFree": { + "type": "boolean" + }, + "paidPlacement": { + "items": { + "additionalProperties": false, + "properties": { + "duration": { + "type": "string" + }, + "priceUsd": { + "type": "number" + } + }, + "required": [ + "duration", + "priceUsd" + ], + "type": "object" + }, + "type": "array" + }, + "promoteEndpoint": { + "type": "string" + } + }, + "required": [ + "listEndpoint", + "listingIsFree", + "paidPlacement", + "promoteEndpoint" + ], + "type": "object" + }, + "execute": { + "additionalProperties": false, + "properties": { + "endpoint": { + "type": "string" + }, + "method": { + "type": "string" + }, + "note": { + "type": "string" + }, + "priceUsd": { + "type": "number" + } + }, + "required": [ + "endpoint", + "method", + "priceUsd", + "note" + ], + "type": "object" + }, + "llmsTxt": { + "type": "string" + }, + "network": { + "type": "string" + }, + "openapi": { + "type": "string" + }, + "payment": { + "additionalProperties": false, + "properties": { + "howToPay": { + "type": "string" + }, + "identity": { + "type": "string" + }, + "manifest": { + "type": "string" + }, + "protocol": { + "type": "string" + }, + "transport": { + "type": "string" + } + }, + "required": [ + "protocol", + "transport", + "manifest", + "howToPay", + "identity" + ], + "type": "object" + }, + "quote": { + "additionalProperties": false, + "properties": { + "endpoint": { + "type": "string" + }, + "free": { + "type": "boolean" + }, + "method": { + "type": "string" + } + }, + "required": [ + "endpoint", + "method", + "free" + ], + "type": "object" + }, + "service": { + "type": "string" + } + }, + "required": [ + "service", + "description", + "network", + "execute", + "quote", + "directory", + "payment", + "openapi", + "llmsTxt" + ], + "type": "object" +}
2 tool updates
- First observed
search_listings - First observed
service_card
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Deterministic company, entity and location lookups for agents - per call, x402 or API key.
Agent-native CRM + get-booked platform. Operate over MCP, or pay per call via x402. No login.
x402-paid agent tools: 18 over HTTP, 14 over stdio. USDC per call, no API key.
Pay-per-call agent tools via x402 (USDC on Base): chat, prices, funding, RNG. No account or keys.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to call 40 paid API tools—including OCR, PDF, image, tabular, and web utilities—by paying per request via x402 micropayments on Base, with no API key, subscription, or signup required.MIT
- AlicenseAqualityAmaintenanceProvides a catalog of paid micro-work tools for text processing, speech, and image generation with fixed USDC pricing via x402. Enables agents to discover capabilities, get quotes, and prepare calls without handling wallet keys.3MIT
- AlicenseNot gradedqualityBmaintenanceProvides 25 pay-per-call tools from agents.oromi.co.uk (business, property, verification, web, crypto) into MCP-capable models, with quote mode for browsing and paid mode using x402.52MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
The two tools have clear, non-overlapping roles: search_listings handles discovery and pagination over the catalog, while service_card provides purchase details and payment instructions. There is no realistic scenario where an agent would confuse which tool to use.
Naming Consistency3/5
search_listings follows a verb_noun pattern, but service_card is a bare noun phrase and lacks an action verb like get_ or fetch_. The names are readable and distinguishable, but the conventions are mixed.
Tool Count3/5
Two tools is on the thin side for a directory-oriented server, but each tool serves a distinct step in the discover-then-purchase flow. It is a borderline count rather than well-scoped or excessive.
Completeness4/5
For the apparent consumer-facing purpose, the core loop is covered: search listings to find a service, then get the service card for pricing and payment URL. A few extras like filtering, categories, or a dedicated listing-detail tool would round it out, but there are no major dead ends.