Public Gateway MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Axcient API key |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_billable_usageA | Get billable usage report for specified date range If not provided, it'll return current month's usage data It returns list of client usage in the children field |
| get_client_infoD | Get billable usage report for specified date range If not provided, it'll return current month's usage data |
| addC | Add two numbers Axcient way |
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
Two tools (get_billable_usage and get_client_info) have identical descriptions, making them indistinguishable. The add tool is unrelated, but the overlap between the other two is severe.
Naming pattern is inconsistent: 'add' does not follow the 'get_' prefix of the other tools. Additionally, get_client_info has a misleading name given its description duplicates get_billable_usage.
3 tools is borderline low but could be acceptable for a very narrow domain. However, the duplication reduces effective count to 2, making the set feel incomplete.
The server's purpose is unclear, but the limited scope (addition and two identical usage reports) suggests significant gaps. No update, delete, or list operations for clients or usage data.