
Razorpay MCP Server Integration
Integrate Razorpay payment processing directly into your FlowHunt workflows with the Razorpay MCP Server. Enable AI-powered automation for payment capture, tran...
Pagos MCP Server gives your FlowHunt workflows secure, real-time payment card intelligence with easy BIN data access for fraud detection, compliance, and analytics.
The Pagos MCP (Model Context Protocol) Server acts as a bridge between AI assistants and the Pagos API, empowering AI-driven workflows with access to real-time BIN (Bank Identification Number) data. By serving as an intermediary, it allows AI tools and agents to query Pagos for detailed information about payment cards using BIN numbers. This integration enables tasks such as verifying card types, issuers, and other relevant BIN-related information, enhancing development workflows that require payment data intelligence. The Pagos MCP Server is especially useful for developers and businesses needing accurate and timely card data for fraud prevention, compliance, or analytics within their AI ecosystems.
No prompt templates are explicitly documented or mentioned in the repository.
No explicit MCP resource primitives are documented or mentioned in the repository.
No setup instructions for Windsurf are provided in the repository.
uv
using Homebrew:brew install uv
git clone https://github.com/pagos-ai/pagos-mcp.git
~/Library/Application Support/Claude/claude_desktop_config.json
with your 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>"
}
}
}
}
Securing API Keys:
Store PAGOS_API_KEY
in the environment variable section of the configuration as shown above.
No setup instructions for Cursor are provided in the repository.
No setup instructions for Cline are provided in the repository.
Using MCP in FlowHunt
To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:
Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:
{
"pagos": {
"transport": "streamable_http",
"url": "https://yourmcpserver.example/pathtothemcp/url"
}
}
Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “pagos” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.
Section | Availability | Details/Notes |
---|---|---|
Overview | ✅ | Pagos MCP provides BIN data lookups via Pagos API |
List of Prompts | ⛔ | No prompt templates documented |
List of Resources | ⛔ | No explicit MCP resources documented |
List of Tools | ✅ | get_bin_data tool in pagos-mcp-server.py |
Securing API Keys | ✅ | Uses env variable PAGOS_API_KEY in config |
Sampling Support (less important in evaluation) | ⛔ | Not documented |
The Pagos MCP Server is focused and straightforward, offering a single, clear tool for BIN data lookups. While it is well-suited for payment-related workflows, its documentation is minimal, lacking detailed resources, prompt templates, or broader integration guides beyond Claude Desktop. Given the limited scope but precise utility, we’d rate this MCP a 4/10 for general-purpose MCP needs, but higher for payment-specific tasks.
Has a LICENSE | ⛔ |
---|---|
Has at least one tool | ✅ |
Number of Forks | 2 |
Number of Stars | 0 |
Pagos MCP Server connects AI assistants to the Pagos API, providing real-time BIN data for payment cards. This enables workflows like card verification, fraud prevention, compliance checks, and analytics within AI-driven environments.
It provides the 'get_bin_data' tool, which fetches metadata about a payment card using its BIN, such as issuer, card type, and more.
Common use cases include payment card verification, fraud detection and prevention, compliance and regulatory checks (KYC/AML), and analytics/reporting on payment methods.
Store your API key as an environment variable (PAGOS_API_KEY) in your MCP server configuration to keep it secure and separate from source code.
While Pagos MCP is highly effective for payment-specific workflows, its scope is narrow and documentation is minimal, making it less suitable for broader MCP requirements.
Enhance your payment workflows with instant BIN data lookups using the Pagos MCP Server. Start preventing fraud and automating compliance today.
Integrate Razorpay payment processing directly into your FlowHunt workflows with the Razorpay MCP Server. Enable AI-powered automation for payment capture, tran...
The DodoPayments MCP Server enables AI assistants to seamlessly interact with external payment systems, allowing for automated payment processing, status checks...
The Model Context Protocol (MCP) Server bridges AI assistants with external data sources, APIs, and services, enabling streamlined integration of complex workfl...