X402 MCP Template
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETWORK | Yes | Network to use: base-sepolia (testnet) or base (mainnet) | |
| PRIVATE_KEY | No | Your wallet private key (66 characters starting with 0x). Leave empty or use placeholder for demo mode. | |
| RESOURCE_SERVER_URL | Yes | The URL of your X402-protected API endpoint |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| example_api_callC | Example tool for making X402-protected API calls. Replace with your actual API endpoints. |
| service_infoB | Get information about the X402 API service including available endpoints, pricing, and payment requirements |
| health_checkB | Check if the X402 API service is available and responding |
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 3 tools
The three tools have clearly distinct purposes: example_api_call is for making API calls, health_check is for service availability, and service_info is for retrieving service metadata. There is no overlap or ambiguity between these functions, making it easy for an agent to select the right tool for each task.
All tool names follow a consistent snake_case pattern with clear verb_noun structures: example_api_call, health_check, and service_info. This uniformity enhances readability and predictability, making the tool set easy to navigate and understand.
With only three tools, the set feels thin for a server labeled as an 'MCP Template' that might imply broader functionality. While the tools cover basic API interaction, health, and info needs, the count is borderline low for a template that could be expanded, suggesting it might be under-scoped for more complex use cases.
The tools provide foundational coverage for API calls, health checks, and service information, but there are notable gaps. For a template server, missing operations like authentication, error handling, or specific endpoint management could limit agent workflows, indicating an incomplete surface for robust API integration.