mcp-l402-directory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_l402_servicesA | Search the L402/x402 service directory for paywalled APIs. Returns services matching a query string — use this to find Lightning-gated or stablecoin-gated APIs for data, AI/ML, finance, identity, search, and more. |
| list_l402_services_by_categoryA | List all available L402/x402 paywalled API services in a category. Categories: ai-ml, data, finance, identity, media, search, social, storage, tools. |
| get_l402_serviceA | Get full details for a specific L402/x402 service by its slug identifier, including endpoint URL, pricing, protocol, payment address, and verification status. |
| get_recently_added_servicesA | Get the most recently added L402/x402 services in the directory — useful for discovering new paywalled APIs as they launch. |
| get_verified_servicesA | Get only domain-verified L402/x402 services — these have proven ownership of their domain and are more trustworthy for agent payments. |
| get_service_descriptorA | Fetch the machine-readable service descriptor for an L402/x402 service. Returns the full descriptor including endpoints, billing details, request/response schemas, stale times, error codes, refund policies, and test endpoints. Use this when you need structured metadata about how to call and pay for an API — billing units, pricing, failure semantics, and preflight verification. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: search, category listing, recent additions, verified services, and descriptor retrieval. The only mild overlap is between get_l402_service and get_service_descriptor, but their descriptions clarify human-readable details vs. machine-readable metadata.
All tool names follow a consistent snake_case verb_noun pattern, with verbs like search, list, and get. The naming style is uniform and predictable across the entire set.
Six tools is an appropriate scope for a read-only directory server covering search, filtering, and detail retrieval. Each tool serves a clear purpose without redundancy or bloat.
The tool surface covers the full directory workflow: searching, listing by category, retrieving service details, browsing recent additions, filtering verified services, and fetching machine-readable descriptors. No obvious gaps exist for this read-only directory use case.