relayshield-mcp
OfficialRelated Servers
Alternatives to relayshield-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenancesecurity 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.915 npm1MIT
- FlicenseNot gradedqualityDmaintenanceProvides 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.-
- FlicenseNot gradedqualityCmaintenance53 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.-
- AlicenseAqualityDmaintenanceURL intelligence for AI agents. One URL in, structured security and data quality signals out across 7 dimensions. 13 tools, risk score 0-100 with 23 configurable weights.1656 npm1MIT
- AlicenseNot gradedqualityCmaintenanceCrypto compliance tools for AI-agent payments: screen any address for sanctions, frozen-stablecoin and hacker/mixer exposure across 8+ chains, trace fund taint, and get an allow/review/decline decision before settlement. Free keyless address checks; deeper endpoints are x402-payable.483 npmMIT
- FlicenseAqualityCmaintenancePay-per-call tools for AI agents including trust checks, due diligence, market data, and human-verified approvals, settled in USDC on Base via the x402 protocol.16-
TDQS
Scored across 11 tools
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.
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.
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.
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.