🍯 Honeypot Transaction Monitoring System
@Thinh-nguyen-03
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
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.
