π― Honeypot Transaction Monitoring System
@Thinh-nguyen-03
About π― Honeypot Transaction Monitoring System
Enterprise-grade MCP server providing real-time transaction monitoring and fraud detection capabilities for honeypot virtual credit cards with Lithic.com. Features instant SSE alerts, comprehensive transaction intelligence, and sophisticated merchant analysis for advanced scammer
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"honeypot-mcp-server": {
"command": "node",
"args": [
"tests/unit/services/alert-service.test.js"
]
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is π― Honeypot Transaction Monitoring System?
The system is an enterprise-grade fraud detection platform that uses Lithic virtual cards as honeypots to detect and analyze fraudulent activities in real time. It integrates with AI agents via Server-Sent Events and the Model Context Protocol (MCP) to enable dynamic scammer verification during live conversations.
How to use π― Honeypot Transaction Monitoring System?
Clone the repository, run npm install, configure environment variables (Supabase URL, Lithic API key, etc.), ensure the required Supabase database tables exist, then start the server with npm run dev or npm start. AI agents can connect to the SSE alert stream at /api/alerts/stream/:cardToken using an Authorization Bearer token.
Key features of π― Honeypot Transaction Monitoring System
- Realβtime transaction alerts via ServerβSent Events
- Virtual card creation and management through Lithic API
- Merchant analysis with MCC categorization and pattern recognition
- Comprehensive transaction intelligence and risk assessment metrics
- Enterpriseβgrade validation, structured logging, and health monitoring
Use cases of π― Honeypot Transaction Monitoring System
- Detect and block fraudulent transactions as they occur using honeypot cards
- Verify scammer identity in real time during AIβled conversations
- Analyze merchant patterns and transaction history to identify fraud trends
- Monitor system health and connection metrics for operational oversight
- Simulate transactions via webhooks for testing and development
FAQ from π― Honeypot Transaction Monitoring System
What runtime and dependencies are required?
Node.js 18+, Express.js, a Supabase PostgreSQL instance, and Lithic API credentials with account access.
How does realβtime alert delivery work?
The system pushes transaction alerts to connected AI agents using ServerβSent Events (SSE), with connection health monitoring and autoβrecovery.
Where is transaction data stored?
All transaction records, merchant information, and card data are persisted in a Supabase PostgreSQL database with predefined tables (transactions, merchants, cards).
How are AI agents authenticated?
Agents authenticate to the SSE alert stream by providing a Bearer session token in the Authorization header.
What is the purpose of the MCP endpoints?
The MCP endpoints (/api/mcp/list_available_cards, /api/mcp/get_card_details, /api/mcp/get_card_info) let AI agents retrieve honeypot card details, including PAN numbers, for live scammer verification.
More Developer Tools MCP servers
Stakpak Agent CLI
stakpakShip your code, on autopilot. An open source agent that lives on your machines 24/7 and keeps your apps running. π¦
OpenSumi
opensumiA framework helps you quickly build AI Native IDE products. MCP Client, supports Model Context Protocol (MCP) tools via MCP server.
mcp-excalidraw
yctimlinMCP server and Claude Code skill for Excalidraw β programmatic canvas toolkit to create, edit, and export diagrams via AI agents with real-time canvas sync.
test
prysmaticlabsGo implementation of Ethereum proof of stake
JetBrains MCP Proxy Server
JetBrainsA model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio
Comments