Vigil Fraud Alert MCP server

Read from the package source without running it. The installed server may list more.

• vigil_add_travel_plan

  Add a travel plan to a card. In travel mode, any transaction in a matching destination_country within [start_date, end_date] is approved without GPS check. Multiple overlapping plans are supported (e.g. US + MX for a road trip).

• vigil_analyze_transactionwrite action

  Run Claude Haiku analysis on a transaction or pending authorization. Returns: risk_score 0\u2013100 integer (100 = certain fraud) risk_factors Array of plain-English factors (location mismatch, late hour, etc.) recommended_action "block" | "confirm" | "allow" alert_message Ready-to-send SMS copy (160 chars, ends with YES=confirm NO=block) explanation 1\u20132 sentence plain-English reasoning Use t

• vigil_authorize

  Authorize a transaction using GPS proximity and card mode

• vigil_block_transaction

  Immediately lock a card (set mode=lockdown) and escalate any open alerts. Use when: - User confirmed fraud via "Was this you? NO" response - AI analysis returns recommended_action="block" - Analyst manually confirms suspicious activity What this does: 1. Sets card.mode = 'lockdown' (all future transactions declined instantly) 2. Escalates all open alerts for this card to status='investigating' 3.

• vigil_confirm_transaction

  Record user response to "Was this you?" push notification. confirmed="yes" \u2014 user made this transaction (marks a blocked txn as false positive) confirmed="no" \u2014 user did NOT make this transaction (escalates alert to investigating) This data feeds directly into risk score calculation and fraud analytics.

• vigil_generate_report

  Generate a professional AML/fraud compliance report for a card using Claude Sonnet. Produces a structured report with: - Executive Summary - Incident Timeline (all declined transactions in period) - Risk Assessment with score breakdown - Recommended Actions - Compliance Notes (for bank/regulator submission) Use for: - Monthly fraud review submission to Stripe/Lithic - AML regulatory filing - Inter

• vigil_get_card

  Get a card's current config: mode, radius, home location, travel plans. Also returns gps_age_minutes so you can assess GPS freshness before authorizing.

• vigil_get_risk_profile

  Get the risk profile for a card. Recalculates live from transaction history. risk_score 0.0\u20131.0 weighted: 40% block rate | 20% false-positive rate | 30% outside-radius count | 10% lockdown usage anomaly_reason: plain-English explanation set by the async AI analyser (Claude Haiku).

• vigil_list_alerts

  List fraud alerts. Filter by card_id, status, or severity. Auto-created for OUTSIDE_RADIUS, SPOOFED_DEVICE, and LOCKDOWN declines. Severity: critical (SPOOFED/LOCKDOWN), high (distance >5000km), medium (distance \u22645000km). Statuses: open \u2192 investigating \u2192 resolved | false_positive

• vigil_list_transactions

  List transaction decisions. Filter by card_id and/or approval outcome. Returns full records: merchant, amount, reason_code, distance_km, GPS coords, processing_ms. Ordered most-recent first. Max 100 per call.

• vigil_update_alertwrite action

  Advance a fraud alert through the investigation workflow and append notes. Typical flow: open \u2192 investigating (analyst picks it up) investigating \u2192 resolved (confirmed fraud, card actioned) investigating \u2192 false_positive (user confirmed it was them) Notes are appended with a timestamp \u2014 not replaced.

• vigil_update_card_modewrite action

  Switch card operating mode: home | travel | lockdown. home \u2014 proximity-based auth against GPS + configured radius travel \u2014 country-match auth using active travel plans; falls back to proximity lockdown \u2014 all transactions declined, no exceptions, instant effect

• vigil_update_gpswrite action

  Push a fresh GPS snapshot for a card. Called by the mobile app on significant-change events (>100m move) and every 60s while foregrounded. GPS freshness is critical to authorization: >5 min old \u2192 GPS_STALE_SOFT decline >15 min old \u2192 GPS_STALE_HARD decline Set is_mock_location=true or is_jailbroken=true to test spoofing detection.

• Code scan21 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Vigil Fraud Alert: common questions

Is Vigil Fraud Alert MCP server safe?

With care: it is graded C, so read the findings first (55/100). Read the Vigil Fraud Alert safety report

How do I install Vigil Fraud Alert?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Vigil Fraud Alert need an API key?

Yes. The registry entry asks for UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN.

Is Vigil Fraud Alert maintained?

The latest release is v1.0.1.

What can I use instead of Vigil Fraud Alert?

Servers from other publishers that do the same job: Netdata MCP server.