Bin Lookup Checker API MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Bin Lookup Checker API MCP ServerLook up the bank and card details for BIN 411111"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bin Lookup Checker Api MCP Server
用于访问 Bin Lookup Checker Api API 的 MCP 服务器。
🚀 使用 EMCP 平台快速体验
EMCP 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!
快速开始:
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场,浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器(
bach-bin_lookup_checker_api)🎉 点击 "安装 MCP" 按钮
✅ 完成!即可在您的应用中使用
EMCP 平台优势:
✨ 零配置:无需手动编辑配置文件
🎨 可视化管理:图形界面轻松管理所有 MCP 服务器
🔐 安全可靠:统一管理 API 密钥和认证信息
🚀 一键安装:MCP 广场提供丰富的服务器选择
📊 使用统计:实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅!
Related MCP server: Pan Card Verification At Lowest Price MCP Server
简介
这是一个 MCP 服务器,用于访问 Bin Lookup Checker Api API。
PyPI 包名:
bach-bin_lookup_checker_api版本: 1.0.0
传输协议: stdio
安装
从 PyPI 安装:
pip install bach-bin_lookup_checker_api从源码安装:
pip install -e .运行
方式 1: 使用 uvx(推荐,无需安装)
# 运行(uvx 会自动安装并运行)
uvx --from bach-bin_lookup_checker_api bach_bin_lookup_checker_api
# 或指定版本
uvx --from bach-bin_lookup_checker_api@latest bach_bin_lookup_checker_api方式 2: 直接运行(开发模式)
python server.py方式 3: 安装后作为命令运行
# 安装
pip install bach-bin_lookup_checker_api
# 运行(命令名使用下划线)
bach_bin_lookup_checker_api配置
API 认证
此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"环境变量
变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
在 Cursor 中使用
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-bin_lookup_checker_api": {
"command": "uvx",
"args": ["--from", "bach-bin_lookup_checker_api", "bach_bin_lookup_checker_api"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}在 Claude Desktop 中使用
编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-bin_lookup_checker_api": {
"command": "uvx",
"args": ["--from", "bach-bin_lookup_checker_api", "bach_bin_lookup_checker_api"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}可用工具
此服务器提供以下工具:
bin_lookup_api
Required 'bin' parameter
端点: GET /bincheck
参数:
bin(number) 必需: Example value: 411111
技术栈
传输协议: stdio
HTTP 客户端: httpx
许可证
MIT License - 详见 LICENSE 文件。
开发
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
Available Tools
1 toolbin_lookup_apiD
Required 'bin' parameter
| Name | Required | Description | Default |
|---|---|---|---|
| bin | Yes | Example value: 411111 | 411111 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description does not disclose any behavioral traits such as return values, side effects, or authorization needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short but under-specified, failing to convey the tool's purpose. Conciseness without substance is not effective.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having no siblings and only one parameter, the description is completely inadequate. The agent cannot determine what the tool does or what response to expect.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds no meaning beyond the input schema. The schema already indicates the 'bin' parameter is required, and the description merely repeats this. Baseline for high schema coverage is 3, but the description provides zero additional value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description only states 'Required bin parameter', which is a tautology restating the required parameter without indicating what the tool does. No verb or resource is mentioned.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 any alternatives is provided. The description lacks context for usage.
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 tool update
v1.0.0- First observed
bin_lookup_api
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or overlap with other tools.
The single tool name 'bin_lookup_api' is descriptive but follows a noun_noun pattern rather than a standard verb_noun convention, making it less predictable.
With only one tool, the server feels minimal. While a single lookup tool may be adequate for a simple BIN checker, it borders on too few for general utility.
The tool covers the core BIN lookup operation, but lacks additional expected functionality such as validation, formatting, or historical data, leaving minor gaps.
Maintenance
Related MCP Connectors
Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.
Validates Luhn, IBAN, ISBN, EAN/UPC, SWIFT/BIC, and EU VAT checksums and formats.
IBAN validation, extraction, format specs and BIC/SWIFT lookup tools for AI assistants.
140+ data APIs for agents: finance, banking validation, geo, weather, text. One API key.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables Claude to retrieve BIN (Bank Identification Number) data for payment cards, with options for basic or enhanced insights through the Pagos API.1-
- AlicenseCqualityDmaintenanceEnables access to the Pan Card Verification API for validating Indian PAN card details. It provides a dedicated tool for performing PAN verification through a standardized MCP interface.1MIT
- AlicenseAqualityAmaintenanceIBAN validation across 89 countries, BIC/SWIFT and Swiss clearing lookup, batch validation, payment-reference, postal-address and Swiss QR-bill checks for AI agents. Connect via MCP or the REST API. Includes free quotas, paid credits and a Pro subscription. SEPA and country-risk indicators support payment-data checks; they do not confirm account ownership or replace beneficiary AML/KYC screening.13123 npm3MIT

Pagos Data MCP Serverofficial
FlicenseAqualityFmaintenanceEnables users to retrieve BIN data for a given BIN number, with optional enhanced attributes for richer insights.11-