A
license-
qualityC
maintenanceThe open marketplace for the agent economy — Buy any of 24,000+ live x402 services with USDC on Base.
Last updated
1
MIT
Fabler x402 Tools
Server Details
Free catalog and 2,048-character secret-scan preview for Fabler's x402 agent tools on Base.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- fablerlabs/x402-tools
- GitHub Stars
- 0
- Server Listing
- fabler-x402-tools
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
B3.4/5.0
Tool DescriptionsB
Average 3.7/5 across 2 of 2 tools scored. Lowest: 2.9/5.
Server CoherenceB
Disambiguation5/5
The two tools have entirely distinct purposes: one lists product catalog and prices, the other scans text for credential patterns. There is no overlap or potential for confusion.
Naming Consistency5/5
Both tools follow the consistent verb_noun pattern with the 'fabler_' prefix: 'list_products' and 'scan_secrets_preview', making them predictable and easy to understand.
Tool Count2/5
With only 2 tools, the server feels very thin for its intended domain, which includes multiple paid services (full scanning, audit, OG cards) not yet available via MCP. The descriptions reference many missing capabilities.
Completeness1/5
The tool set covers only free, limited previews. Essential paid functionalities like full secret scanning and agent audit are completely absent from the MCP surface, creating severe gaps that agents cannot work around.
Available Tools
2 toolsfabler_list_productsCInspect
List Fabler Labs' x402 products with their current per-call USDC price on Base. Free, no wallet or payment required. Note: this MCP endpoint (Streamable HTTP, mounted directly on the store at /mcp) exposes this catalog plus a free bounded secret-scan preview. The paid tools (full secret scanning, agent-config audit, OG card rendering) are not yet wired for payment over MCP — call them directly over HTTP with x402 (GET /openapi.json describes every priced route), or use the wallet-capable stdio MCP server from GitHub for automatic payment: npx -y github:fablerlabs/x402-tools.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
C2.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the tool is free and requires no payment or wallet, and notes that paid tools are not wired for MCP. However, it does not describe the output format, potential errors, rate limits, or other behavioral traits that would help an agent understand the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is verbose and includes extraneous information about paid tools, GitHub commands, and the MCP endpoint configuration that is not directly relevant to the tool's purpose. This detracts from conciseness and front-loading the essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there are no annotations and no output schema, the description lacks details about the return format, pagination, or response structure. It provides sufficient high-level context for a simple list tool but is incomplete for an agent to fully understand what to expect from the 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 has zero parameters with 100% coverage, so the description adds meaning by specifying what is listed (x402 products and their prices). This is baseline for a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the primary action: listing Fabler Labs' x402 products with per-call USDC prices on Base. It is specific and provides a verb-resource pair. However, it also mentions that this MCP endpoint exposes a free bounded secret-scan preview, which could be a different capability and muddies the clarity regarding the sibling tool 'fabler_scan_secrets_preview'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers some context about when to use this tool (free, no wallet required) and mentions alternatives (paid tools via HTTP). However, it does not clearly distinguish this tool from its sibling 'fabler_scan_secrets_preview' and provides no explicit guidance on when not to use it or when to prefer another tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
fabler_scan_secrets_previewAInspect
Scan up to 2,048 characters for common credential patterns and return only masked matches. Free, no wallet or account required. For larger inputs, use the $0.005 full scanner through the wallet-capable client: npx -y github:fablerlabs/x402-tools.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Text to inspect. Maximum 2,048 characters. |
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description carries full burden. It states 'return only masked matches' and 'Free, no wallet or account required,' which are useful behavioral traits. However, it does not specify what happens if no credentials are found or what patterns are scanned, missing some transparency. Still, for a preview tool, it's largely sufficient.
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: purpose, constraint/pricing, and alternative. No filler, front-loaded with key info. Every sentence adds value.
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 simple tool with one parameter, no output schema, and no annotations, the description covers purpose, input limit, cost, and how to handle larger inputs. Complete for intended use.
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% with one parameter 'text' described as 'Text to inspect. Maximum 2,048 characters.' The description repeats the length constraint but adds 'Free, no wallet...' which is not about parameter semantics. No new parameter-level meaning beyond schema.
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 clearly states 'Scan up to 2,048 characters for common credential patterns and return only masked matches.' This specifies the action (scan), resource (text), and outcome (masked matches). The sibling tool 'fabler_list_products' is unrelated, so no ambiguity.
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 explicitly says 'Free, no wallet or account required,' indicating when to use this tool, and provides an alternative: 'For larger inputs, use the $0.005 full scanner through the wallet-capable client: npx -y github:fablerlabs/x402-tools.' This gives 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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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 Servers
Cinderwrightofficial
AlicenseBqualityAmaintenancex402 Discovery Hub. Search engine for the agent economy with 1450+ services indexed. Search by keyword, browse by category, free service submission.Last updated12423MIT- Flicense-qualityBmaintenancePay-per-use AI security and research tools for autonomous agents on Base, enabling honeypot detection, risk assessment, wallet analysis, and yield optimization via the x402 protocol.Last updated
- AlicenseBqualityAmaintenancePay-per-call AI agent APIs on Base via x402. Multiple tools across patents, law, AI, geo, weather, crypto, and more. Always growing.Last updated1005MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.