ShieldAPI MCP
Related Servers
Alternatives to ShieldAPI MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run paid safety and data pre-checks over streamable HTTP — Base token risk and pricing, wallet balances and screening, transaction decoding, calldata and EIP-712 signature checks, ENS resolution, DNS/WHOIS, link phishing and security-header audits — with each tool call settled by an x402 USDC micropayment on Base instead of an account or API key. Also offers x402 seller preflight and web content extraction.MIT
- FlicenseNot gradedqualityDmaintenance53 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.-
- AlicenseNot gradedqualityFmaintenanceArchived and no longer maintained. Tools and prices shown here are out of date. Use the maintained server: glama.ai/mcp/servers/OceanAlt666/oceanalt-aml-mcp (GitHub: OceanAlt666/oceanalt-aml-mcp).444 npmMIT
- FlicenseNot gradedqualityCmaintenancePay-per-call agent tools (web reader, page extract, email/domain/site/wallet/token checks, screenshot, PDF) via x402 USDC micropayments, with 3 free trial calls per wallet.-
- AlicenseNot gradedqualityBmaintenancePay-per-call checks an AI agent runs before it moves money: token safety verdicts and wallet risk profiles on Base, on-chain payment verification, IBAN/VAT/BIC/LEI/ISIN validation, and live TLS and email-spoofing posture for a domain. Paid in USDC over x402 with no API key or account; the free payment_info tool explains the pricing.MIT

relayshield-mcpofficial
AlicenseAqualityBmaintenanceSecurity intelligence for AI agents — breach detection, SIM swap, domain lookalikes, OAuth watchlist, and malware scanning. Subscription or x402 PAYG.11MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose targeting specific security checks: domain, email, IP, password, prompt, URL, full scan, and skill scanning. The descriptions are detailed and non-overlapping, making it easy for an agent to select the right tool. For example, check_password and check_password_range are distinct in handling full hashes versus hash prefixes.
All tools follow a consistent verb_noun pattern with the prefix 'shieldapi.' and use snake_case throughout (e.g., check_domain, check_email, check_ip). This predictability aids in tool discovery and usage. The naming is uniform across all nine tools without any deviations.
With 9 tools, the set is well-scoped for a security-focused server, covering diverse checks from domain reputation to AI skill scanning. Each tool earns its place by addressing a specific security need, avoiding redundancy. The count is typical for such a domain, neither too sparse nor bloated.
The tool surface is highly complete for security scanning, covering key areas like domain, email, IP, password, URL, prompt injection, and AI skills. A minor gap is the lack of tools for remediation or mitigation actions (e.g., blocking threats), but the server's purpose appears focused on detection and analysis, which is well-covered. Agents can work around this by using results for decision-making.