Skip to main content
Glama
Kaidn-io

Kaidn-mcp

Official
by Kaidn-io

Related Servers

Alternatives to Kaidn-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      12 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Give your AI agents direct access to live honeypot threat intelligence. Look up attacker IPs, browse indicators of compromise (IOCs), inspect captured credentials and malware payloads, profile threat actors, and render a real-time global attack map — all from Claude, Cursor, or any MCP-compatible client.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Scans suspicious messages, URLs, and text for scams inside any MCP-compatible AI assistant. No signup or API key needed for anonymous use.
      1
      41 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      53 security & enrichment MCP tools for AI agents. Contract scanning, threat intel, OSINT, crypto data, DNS/WAF recon. Pay-per-call via HTTP 402 + USDC on Base mainnet. No API keys. First call free.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides trust infrastructure for AI agents by enabling reputation lookup, website trust scanning, and identity verification via MCP tools.
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time threat intelligence for AI agents, enabling checks on IPs, domains, URLs, hashes, CVEs, prompt-injection payloads, and malicious AI-skill/MCP-tool definitions against a free database of 890K+ IOCs.
      -

    TDQS

    A4.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo issues