Skip to main content
Glama
ampcome-mcps

Pagos Data MCP Server

by ampcome-mcps
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Pagos Data MCP Server

Capabilities

  • Get BIN data for a given BIN number.

Related MCP server: Bin Lookup Checker API 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 update
    • First observedget_bin_data_tool
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose of retrieving BIN data, so an agent cannot misselect between multiple options.

Naming Consistency5/5

The tool name 'get_bin_data_tool' follows a consistent verb_noun pattern with a clear action ('get') and object ('bin_data'), and the naming is straightforward. Since there is only one tool, consistency is inherently perfect.

Tool Count2/5

A single tool is too few for a server with the name 'Pagos Data MCP Server', which suggests a broader data-related domain. This minimal toolset limits functionality and may not cover expected operations like searching, listing, or updating data, making it feel incomplete and under-scoped.

Completeness2/5

The tool surface is severely incomplete for a data server. It only provides a 'get' operation for BIN data, with no support for other CRUD operations (create, update, delete), search, or listing capabilities. This creates significant gaps that will likely cause agent failures when trying to perform common data tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Qlik MCP Server

    jwaxman19
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables Claude to interact with Qlik Cloud applications and extract data from visualizations through the Qlik Cloud API.
    11
    MIT

  • Bin Lookup Checker API MCP

    BACH-AI-Tools
    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
  • BlockRun MCP by BlockRunAI

    BlockRun MCPofficial

    BlockRunAI
    A
    license
    A
    quality
    A
    maintenance
    Provides Claude with real-time access to markets, research, X/Twitter, and crypto data via a unified pay-per-call system with no API keys.
    19
    1,419
    395
    MIT