ShieldAPI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIELDAPI_URL | No | API base URL | https://shield.vainplex.dev |
| SHIELDAPI_WALLET_PRIVATE_KEY | No | EVM private key for USDC payments. If not set, the server operates in demo mode with free tier limits. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shieldapi.check_urlA | Check a URL for malware, phishing, and other threats. Uses URLhaus + heuristic analysis. |
| shieldapi.check_passwordA | Check if a password hash (SHA-1) has been exposed in known data breaches via HIBP. |
| shieldapi.check_password_rangeA | Look up a SHA-1 hash prefix in the HIBP k-Anonymity database. |
| shieldapi.check_domainA | Check domain reputation: DNS records, blacklists (Spamhaus, SpamCop, SORBS), SPF/DMARC, SSL. |
| shieldapi.check_ipA | Check IP reputation: blacklists, Tor exit node detection, reverse DNS. |
| shieldapi.check_emailA | Check if an email address has been exposed in known data breaches via HIBP. |
| shieldapi.full_scanA | Run all security checks on a target (URL, domain, IP, or email). Most comprehensive scan. |
| shieldapi.scan_skillA | Scan an AI agent skill/plugin for security issues across 8 risk categories (Snyk ToxicSkills taxonomy). Checks for prompt injection, malicious code, suspicious downloads, credential handling, secret detection, third-party content, unverifiable dependencies, and financial access patterns. Static analysis only — no code execution. Returns risk score (0-100), severity-ranked findings with file locations, and human-readable summary. |
| shieldapi.check_promptA | Detect prompt injection in text. Analyzes across 4 categories (direct injection, encoding tricks, exfiltration, indirect injection) with 200+ detection patterns. Designed for real-time inline usage before processing untrusted user input. Returns boolean verdict, confidence score (0-1), matched patterns with evidence, and decoded content if encoding obfuscation was detected. Response time <100ms p95. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| security_assessment | Generate a security assessment report for a target (domain, URL, IP, or email) |
| quick_check | Quick security check — automatically detects target type and runs the right scan |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.