π― Honeypot Transaction Monitoring System
LocalAbout π― Honeypot Transaction Monitoring System
Honeypot MCP Server provides transaction intelligence for monitoring virtual honeypot cards and investigating fraudulent transactions. It is designed for AI agents and workflows that gather information about scammer activity, with card controls and real-time feeds.
Key features
- 01Manage honeypot cards through Lithic
- 02Search and inspect transactions
- 03Analyze transactions by merchant
- 04Subscribe to transaction alerts
- 05Monitor a live transaction feed
Use cases
- 01Track transactions on honeypot cards
- 02Investigate activity associated with a merchant
- 03Receive alerts as transactions occur
- 04Manage card limits and activation state
MCP support
Exposes 13 tools to MCP clients for health checks, card management, transaction analysis, alerts, and live feeds. It supports HTTP and Stdio transports.
Configuration
Local server config is the same for every client. Copy it into your clientβs MCP config file.
We havenβt collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEHoneypot MCP Server
Overview
The Honeypot MCP Server is a transaction intelligence system built on the Model Context Protocol (MCP). It enables AI agents acting as vulnerable elderly personas to provide card details to scammers, then monitors and analyzes the resulting fraudulent transactions to gather intelligence about scammer operations and methods.
Features
- 13 MCP Tools: Comprehensive set of tools for transaction monitoring and card management
- Transaction Intelligence: Advanced transaction search and analysis capabilities
- Card Management: Create and manage honeypot cards via Lithic API
- Real-time Monitoring: Live transaction feeds and alert subscriptions
- MCP Protocol: Native support for Model Context Protocol with HTTP and Stdio transports
Quick Start
Prerequisites
- Node.js 18.0.0+
- Supabase account and database
- Lithic API access
Installation
git clone <repository-url>
cd honeypot-mcp-server
npm ci
Configuration
Create a .env file with the following variables:
# Core Configuration
NODE_ENV=production
PORT=3000
# Database
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_SERVICE_KEY=your_service_key
# Financial API
LITHIC_API_KEY=your_lithic_api_key
LITHIC_ENV=production
# Optional Features
LITHIC_WEBHOOK_SECRET=your_webhook_secret
ENABLE_POLLING=true
POLLING_INTERVAL_MS=5000
MCP_TRANSPORT=http
Testing
# Run test suite
npm test
# Run security tests
npm run test:security
# Run performance tests
npm run test:performance
Running
# Start the server
npm start
# Check health
curl http://localhost:3000/health
MCP Tools
The server provides 13 tools organized by category:
System Operations (1 tool)
health_check- System health monitoring
Card Management (5 tools)
list_available_cards- List available honeypot cardsget_card_details- Get detailed card informationcreate_honeypot_card- Create new honeypot cardsupdate_card_limits- Update card spending limitstoggle_card_state- Activate/deactivate cards
Transaction Intelligence (5 tools)
get_transaction- Get single transaction detailssearch_transactions- Search transactions with filtersget_recent_transactions- Get recent transactions for a cardget_transactions_by_merchant- Get transactions by merchantget_transaction_details- Get comprehensive transaction information
Real-Time Intelligence (2 tools)
subscribe_to_alerts- Set up transaction alertsget_live_transaction_feed- Monitor real-time transactions
Transaction Intelligence
The system provides comprehensive transaction monitoring and analysis including:
- Advanced transaction search and filtering
- Real-time transaction monitoring
- Merchant-specific transaction analysis
- Card-based transaction tracking
- Live transaction feed capabilities
Core Focus: Streamlined transaction intelligence for monitoring and investigation workflows.
Technology Stack
- Runtime: Node.js with ES Modules
- Database: Supabase (PostgreSQL)
- Financial API: Lithic Virtual Card Platform
- Protocol: Model Context Protocol (MCP)
- Testing: Vitest framework
API Integration
MCP Client Example
import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/stdio.js';
const transport = new StdioClientTransport({
command: 'node',
args: ['src/mcp-server.js']
});
const client = new Client({
name: 'fraud-detection-agent',
version: '1.0.0'
}, {
capabilities: { tools: {} }
});
await client.connect(transport);
const tools = await client.listTools();
Health Check
const health = await client.callTool({
name: 'health_check',
arguments: { includeDetails: true }
});
Development
Project Structure
src/
βββ config/ # Configuration and client setup
βββ handlers/ # MCP tool implementations
βββ schemas/ # Tool input/output schemas
βββ services/ # Business logic services
βββ utils/ # Utilities and helpers
tests/
βββ unit/ # Unit tests
βββ integration/ # Integration tests
βββ security/ # Security tests
βββ performance/ # Performance tests
Testing
The project includes comprehensive test coverage:
- Unit tests for all handlers and services
- Integration tests for MCP protocol compliance
- Security tests for authentication and data handling
- Performance tests for response times
Deployment
See DEPLOYMENT.md for detailed deployment instructions.
The application can be deployed on:
- Railway (recommended, with included
railway.json) - Docker containers
- Traditional servers
License
This project is licensed under the MIT License - see the LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.