Pagos Data MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAGOS_API_KEY | Yes | Pagos API key for authenticating requests. | |
| ENHANCED_BIN_DATA | No | Set to 'true' for enhanced BIN response attributes, 'false' for basic. Defaults to 'false'. | false |
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_bin_data_toolA | Get BIN data for a given BIN number. Args: bin (str): The BIN number to get data for. Returns: str: A formatted string containing the BIN data (enhanced or basic based on ENHANCED_BIN_DATA config). |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool named 'get_bin_data_tool', the naming is trivially consistent. While the suffix 'tool' is redundant, there are no other tools to conflict.
One tool is borderline thin for a typical server. Though the BIN data lookup is a specific function, the server likely would benefit from additional related operations.
The server provides only a single read operation. Missing update, delete, or batch operations create significant gaps for a data-focused server.