Skip to main content
Glama
pagos-ai

Pagos Data MCP Server

Official
by pagos-ai

Pagos Data MCP Server

Capabilities

  • Get BIN data for a given BIN number.

Related MCP server: B2Bhint MCP Server

Configuration

Pagos API Key

Follow the instructions in the Pagos API Key documentation to create an API key.

Enhanced BIN Data

Set to "true" for enhanced BIN response attributes which will provide the richest insights on the BIN. Set to "false" for basic BIN data. Defaults to "false" if value is not provided. Check your contract for any additional costs associated with enhanced bin data calls before setting to "true".

Clone the repository locally and install uv

On MacOs, install uv with Homebrew:

brew install uv

Clone the repository:

git clone https://github.com/pagos-ai/pagos-mcp.git

Add the MCP Server to Desktop Claude

On MacOs, update config file ~/Library/Application\ Support/Claude/claude_desktop_config.json and update elements with your systems specific values.

{
    "mcpServers": {
        "bin-data": {
            "command": "uv",
            "args": [
                "--directory",
                "</path/to/pagos-mcp-server>",
                "run",
                "pagos-mcp-server.py"
            ],
            "env": {
                "PAGOS_API_KEY": "<your-pagos-api-key>",
                "ENHANCED_BIN_DATA": "true"
            }
        }
    }
}

Available Tools

1 tool
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).

ParametersJSON Schema
NameRequiredDescriptionDefault
binYes

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description discloses return format and config dependency (basic vs enhanced). However, no annotations are present, and the description does not cover error behavior, side effects, or permissions, which are important for a data retrieval tool.

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?

Extremely concise with two clear sections (Args, Returns). No wasteful words, highly structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter, no-output-schema tool, the description covers basic functionality and return type. Lacks error handling details, but overall sufficient for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema provides only parameter name and type (0% coverage). Description adds meaning by explaining 'bin' is the BIN number to query, which compensates for the lack of schema descriptions.

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?

Clear verb 'Get' and resource 'BIN data' stated explicitly. Distinguishes itself from potential siblings by specifying it operates on a BIN number.

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?

No guidance on when to use this tool or when alternatives might be better. Since no siblings exist, it still lacks contextual usage hints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedget_bin_data_tool

TDQS

A3.8/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness2/5

The server provides only a single read operation. Missing update, delete, or batch operations create significant gaps for a data-focused server.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Related MCP Connectors

Related MCP Servers

  • F
    license
    B
    quality
    D
    maintenance
    Enables Claude to retrieve BIN (Bank Identification Number) data for payment cards, with options for basic or enhanced insights through the Pagos API.
    1
    -
  • A
    license
    B
    quality
    D
    maintenance
    Enables access to B2Bhint API for searching and retrieving company and person information, including company details, financial reports, and contact data across multiple countries.
    5
    MIT
  • A
    license
    D
    quality
    D
    maintenance
    Enables bank identification number (BIN) lookups via the Bin Lookup Checker API. It allows users to retrieve information about card issuers, card types, and brands using a specific BIN.
    1
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables users to explore and manage banking card features including product discovery, comparison, eligibility checks, spend insights, merchant offers, travel notices, card controls, and digital wallet provisioning.
    -