Kaidn-mcp
OfficialRelated Servers
Alternatives to Kaidn-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to look up domains, URLs, IPs/ASNs, email addresses, phone numbers, crypto wallets, and business records; run autonomous investigations; collect crawl artifacts; and perform evidence-backed scam checks with traceable provenance.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and apps to check URLs, domains, IP addresses, phone numbers, emails, crypto wallets, IBANs, mobile apps, and payment handles for scam, phishing, and fraud risk, returning verdicts, probabilities, facts, and reason codes.MIT
- AlicenseNot gradedqualityBmaintenanceEnables checking any IP address for VPN, proxy, Tor, datacenter hosting, anonymity, and fraud risk signals, plus API service status, directly from MCP-capable clients like Claude and Cursor.118 npm2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to investigate synthetic fraud cases by pulling transactions, running deterministic rules evaluations, pivoting across devices, and recording auditable case files with provenance.4MIT
- FlicenseAqualityDmaintenanceEnables real-time fraud detection and transaction analysis by integrating with Claude through MCP, providing tools to analyze transactions, flag suspicious activity, and manage fraud rules.9-
- AlicenseCqualityBmaintenanceEnables Claude Desktop, Cursor, and other MCP clients to inspect a Remnawave 3.x panel through natural-language chat, covering users, nodes, traffic, devices, connections, and GeoCheck, with tools generated from the official backend contract to match the panel version. Read-only by default and privacy-filtered, so secrets, keys, and client identifiers are hidden or replaced with aliases before reaching the chat.9113 npm21MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: check_email/check_ip/check_phone target different entity types, the read-only analytics tools (list_events, get_stats, get_config, explain_event, triage_queue) each serve a unique function, investigate_entity combines enrichment and history, and score_event is the only action that records an event. No two tools are easily confused.
All tool names follow a consistent verb_noun snake_case pattern (check_email, list_events, get_config, score_event, etc.). The verbs (check, list, get, explain, investigate, triage, score) clearly indicate the action, and the nouns (email, events, stats, config, entity, queue) indicate the resource.
10 tools is well within the ideal range for a fraud investigation MCP. Each tool covers a distinct need — enrichment, event browsing, stats, config, explanation, investigation, triage, and scoring — without unnecessary redundancy or bloat.
The tool set covers the full investigation lifecycle: enrichment for email/IP/phone/device, listing and triaging events, understanding scores via stats and config, explaining individual verdicts, investigating entity history, and testing new events. There are no obvious missing operations for the stated purpose.