How do I use bach-bin_ip_checker?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@bach-bin_ip_checker check credit card bin 448590 and ip 2.56.188.79" 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 Ip Checker MCP Server

English | 简体中文 | 繁體中文

用于访问 Bin Ip Checker API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-bin_ip_checker）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用

EMCP 平台优势：

✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: fraud-prevention-mcp-server

简介

这是一个 MCP 服务器，用于访问 Bin Ip Checker API。

PyPI 包名: bach-bin_ip_checker
版本: 1.0.0
传输协议: stdio

安装

从 PyPI 安装:

pip install bach-bin_ip_checker

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-bin_ip_checker bach_bin_ip_checker

# 或指定版本
uvx --from bach-bin_ip_checker@latest bach_bin_ip_checker

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-bin_ip_checker

# 运行（命令名使用下划线）
bach_bin_ip_checker

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名	说明	必需
`API_KEY`	API 密钥	是
`PORT`	不适用	否
`HOST`	不适用	否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-bin_ip_checker": {
      "command": "uvx",
      "args": ["--from", "bach-bin_ip_checker", "bach_bin_ip_checker"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-bin_ip_checker": {
      "command": "uvx",
      "args": ["--from", "bach-bin_ip_checker", "bach_bin_ip_checker"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

`bin_checker`

Shield your business from fraud effortlessly with our powerful, free BIN lookup API. Prevent fraudulent credit card transactions with ease by verifying, validating, and scrutinizing card details using BIN numbers. Our extensive database, boasting millions of BINs, ensures unparalleled accuracy, giving you peace of mind in every transaction. Harness the power of our BIN lookup solution to safeguard your revenue and maintain security for your business. --(Just Updated) Designed with online mer...

端点: GET /

参数:

bin (number) 必需: Example value: 448590

`binip_checker`

Shield your business from fraud effortlessly with our powerful, free BIN lookup API. Prevent fraudulent credit card transactions with ease by verifying, validating, and scrutinizing card details using BIN numbers. Our extensive database, boasting millions of BINs, ensures unparalleled accuracy, giving you peace of mind in every transaction. Harness the power of our BIN lookup solution to safeguard your revenue and maintain security for your business. --(Just Updated) Designed with online mer...

端点: POST /

参数:

bin (number) 必需: Example value: 448590
ip (string): Example value: 2.56.188.79

`ip_lookup`

IP Address Lookup

端点: GET /ip-lookup

参数:

ip (string) 必需: Example value: 2.56.188.79

技术栈

传输协议: stdio
HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

3 tools

bin_checkerC

Shield your business from fraud effortlessly with our powerful, free BIN lookup API. Prevent fraudulent credit card transactions with ease by verifying, validating, and scrutinizing card details using BIN numbers. Our extensive database, boasting millions of BINs, ensures unparalleled accuracy, giving you peace of mind in every transaction. Harness the power of our BIN lookup solution to safeguard your revenue and maintain security for your business. --(Just Updated) Designed with online mer...

ParametersJSON Schema

Name	Required	Description	Default
`bin`	Yes	Example value: 448590	448590

TDQS

C2.1/5.0

Behavior1/5

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

With no annotations, the description should disclose behavioral traits. It mentions fraud prevention but does not explain what happens on invalid BIN, return format, rate limits, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose marketing language ('Shield your business', 'unparalleled accuracy') and cuts off mid-sentence. It wastes words without providing useful technical information.

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

Completeness1/5

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

No output schema is provided, and the description fails to specify what data the tool returns (e.g., card brand, bank info). For a single-parameter tool, this is insufficient.

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

Parameters2/5

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

The input schema has 100% coverage but the description adds no meaning beyond 'BIN numbers'. The parameter description only gives an example value, and the tool description doesn't clarify the BIN length or format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it's a BIN lookup tool for fraud prevention, verifying and validating card details. However, it does not distinguish from the sibling tool 'binip_checker' and the description cuts off.

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 versus alternatives like 'binip_checker' or 'ip_lookup'. The description is purely promotional with no contextual usage advice.

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

binip_checkerD

Shield your business from fraud effortlessly with our powerful, free BIN lookup API. Prevent fraudulent credit card transactions with ease by verifying, validating, and scrutinizing card details using BIN numbers. Our extensive database, boasting millions of BINs, ensures unparalleled accuracy, giving you peace of mind in every transaction. Harness the power of our BIN lookup solution to safeguard your revenue and maintain security for your business. --(Just Updated) Designed with online mer...

ParametersJSON Schema

Name	Required	Description	Default
`bin`	Yes	Example value: 448590	448590
`ip`	No	Example value: 2.56.188.79

TDQS

D1.8/5.0

Behavior2/5

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

Lacks annotations. The description provides no behavioral details: no mention of read-only nature, output format, rate limits, or side effects. It is purely promotional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Excessively verbose marketing text not suitable for an API description. Critical information is buried or absent.

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

Completeness1/5

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

Given 2 parameters and no output schema, the description should explain return value and usage. It does not, leaving the agent completely uninformed about tool behavior.

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

Parameters2/5

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

Schema coverage is 100% but parameter descriptions are only example values. The description adds no semantic meaning beyond 'BIN lookup' and does not explain the ip parameter's role or expected format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses marketing language ('Shield your business from fraud') rather than clearly stating it performs a BIN/IP lookup. It does not explicitly state the tool combines BIN and IP data, and does not distinguish from sibling tools bin_checker and ip_lookup.

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 vs bin_checker or ip_lookup. No mention of prerequisites, limitations, or typical scenarios.

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

ip_lookupD

IP Address Lookup

ParametersJSON Schema

Name	Required	Description	Default
`ip`	Yes	Example value: 2.56.188.79

TDQS

D1.7/5.0

Behavior1/5

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 (e.g., read-only, rate limits, data source). The description fails to carry the full burden of transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but does not earn its place as it is tautological and under-specified. It is not appropriately sized for providing minimal useful information.

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

Completeness2/5

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

For a simple tool with one parameter and no output schema, the description is incomplete. It does not explain what the lookup returns or any context about the data.

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

Parameters3/5

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

Schema coverage is 100% with a parameter description example, so the baseline is 3. The description adds no additional semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'IP Address Lookup' is a tautology that merely restates the tool name 'ip_lookup', adding no new information about what the tool does.

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 is provided on when to use this tool vs. alternatives (e.g., bin_checker or binip_checker), nor are there any exclusions or prerequisites mentioned.

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.

3 tool updatesv1.0.0Apr 25, 2026
- First observedbin_checker
- First observedbinip_checker
- First observedip_lookup

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.1/5.0

Scored 2026-04-25 03:25 across 3 tools

Disambiguation2/5

bin_checker and binip_checker have identical descriptions, making them indistinguishable. ip_lookup is distinct, but the overlap between the other two is severe.

Naming Consistency2/5

Inconsistent verb choice: 'checker' vs 'lookup'. Also, 'binip_checker' appears to combine BIN and IP, but its description is only about BIN. No clear pattern.

Tool Count4/5

Three tools is a reasonable number for a focused utility like BIN and IP checking, though the duplication of BIN tools is unnecessary.

Completeness3/5

Covers BIN lookup and IP lookup, but lacks additional operations like history, validation details, or batch processing. Somewhat incomplete for a full fraud-checking service.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

finance-validation-mcp
io.github.sercanmetalore
Finans/kimlik doğrulama MCP sunucusu: IBAN, BIC/SWIFT, ABD ABA/ACH yönlendirme no, kart (Luhn/BIN…
Finance Payments & Billing
1
bin-lookup-mcp
io.github.sercanmetalore
BIN/IIN sorgulama MCP sunucusu: kart markası, tür, ihraç eden banka ve ülke bilgisi. Üç katmanlı…
Finance Payments & Billing
1
maxmind-minfraud A
io.usefulapi
MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.
Security Finance
42
broker-safety A
com.brokerchooser
MCP server offering regulator-sourced legitimacy checks on investment entities by name or URL.
Finance Search Government Data
12

Related MCP Servers

Mastercard BIN Table MCP
Search Finance
ag2-mcp-servers
F
license
Not graded
quality
D
maintenance
An MCP server that provides access to Mastercard's BIN Table Resource API, allowing users to look up and interact with Bank Identification Number data through natural language queries.
Updated a year ago (2025-07-16 14:14 UTC)
-
fraud-prevention-mcp-server
Security AI & Machine Learning
AiAgentKarl
A
license
A
quality
D
maintenance
An open-source MCP server for AI-powered fraud prevention that detects fraudulent IPs, emails, URLs, and phone numbers using free APIs and provides actionable risk scores.
Updated 5 months ago (2026-04-03 16:05 UTC)
7
MIT
yaml-ai-mcpofficial
Finance Legal & Compliance
CSOAI-ORG
F
license
A
quality
B
maintenance
An MCP server for anti-money laundering (AML) compliance, including customer due diligence, transaction monitoring, and SAR filing, compliant with 6AMLD, UK MLR 2017, and FinCEN.
Updated 13 days ago (2026-09-04 12:45 UTC)
4
48 PyPI
-
ip-doctor
Networking & Infrastructure Security
Baneado98
A
license
A
quality
B
maintenance
MCP server for live IP and domain reputation checks via DNS lookups, providing abuse scores and network type without requiring an API key.
Updated 3 months ago (2026-06-23 14:29 UTC)
2
MIT

Bin Ip Checker MCP Server

🚀 使用 EMCP 平台快速体验

快速开始：

EMCP 平台优势：

简介

安装

从 PyPI 安装:

从源码安装:

运行

方式 1: 使用 uvx（推荐，无需安装）

方式 2: 直接运行（开发模式）

方式 3: 安装后作为命令运行

配置

API 认证

环境变量

在 Cursor 中使用

在 Claude Desktop 中使用

可用工具

bin_checker

binip_checker

ip_lookup

技术栈

许可证

开发

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Mastercard BIN Table MCP

fraud-prevention-mcp-server

yaml-ai-mcpofficial

ip-doctor

`bin_checker`

`binip_checker`

`ip_lookup`