Skip to main content
Glama
relayshield

relayshield-mcp

Official
by relayshield

Related Servers

Alternatives to relayshield-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      security tools for AI agents: URL safety scanning, prompt injection detection (200+ patterns), email/password breach checks via HIBP, domain & IP reputation analysis, and AI skill supply chain scanning. Free tier (3 calls/day) or pay-per-request with USDC micropayments via x402.
      9
      26 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Gives AI agents threat-intelligence verdicts for IPs, domains, URLs and hashes, CVE lookups with EPSS and CISA KEV data, and a prompt-injection gate that scans untrusted text before the agent acts on it. Agents can also batch-check up to 100 indicators, hunt brand-lookalike domains, and track scan and request quotas.
      1
      868 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform pay-per-call security verification of wallets, tokens, contracts, dApps, agents, and more via a remote endpoint with no installation.
      2
      MIT
    • 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.
      -
    • 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.
      -

    TDQS

    A4.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool targets a distinct risk surface (phone, email, URL/file, wallet, MCP, domains), and the async scan tools have a clear poller companion. The only real ambiguity is among check_breach, check_infostealer, and check_prompt_injection_breach, which all take an email address but are differentiated by data source.

    Naming Consistency4/5

    The set follows a consistent check_/scan_ + target convention, and check_scan_result clearly pairs with scan_url/scan_file. scan_wallet and check_domain_lookalikes deviate slightly from the expected direct-check naming, but the pattern remains predictable.

    Tool Count5/5

    Eleven tools is a reasonable size for a security-checking server covering phone, email, URLs, files, wallets, MCP servers, and domains. Each tool represents a distinct check or required polling helper, with no obvious filler.

    Completeness4/5

    The surface covers the main security-check workflows end to end, including async URL/file scans paired with check_scan_result. Minor gaps exist (e.g., general domain reputation checking or historical result retrieval), but they do not create dead ends for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues