ShieldNet MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_urlA | Run a comprehensive security scan on a URL. Checks 7 modules: security headers, injection (XSS/SQLi/SSTI/command injection/path traversal), CORS, info disclosure (25 sensitive paths), TLS, authentication issues, and misconfigurations. Returns findings with severity ratings and a security grade (A-F). Use 'aggressive' mode to also test rate limiting. |
| assess_riskA | Security governance gate: scan a URL and return an ALLOW/WARN/BLOCK decision with confidence score. Use as a guardrail before an AI agent connects to any external service. |
| check_headersA | Quick security headers audit — checks HSTS, CSP, CORS, X-Frame-Options, cookie flags, and more. |
| scan_historyA | View history of security scans performed in this session with grades and scores. |
| compare_scansB | Compare security posture of two URLs side by side — useful for evaluating which endpoint is safer. |
| governance_policyB | View the security governance policy or evaluate a score against ALLOW/WARN/BLOCK thresholds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| security_audit | Full security audit with governance decision |
| pre_deployment_check | Security gate check before deployment |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Attack Vector Database | Security checks performed by ShieldNet |
| Scan History | All scans from this session |
| Governance Policy | ALLOW/WARN/BLOCK thresholds and rules |
TDQS
Scored across 6 tools
scan_url and assess_risk both scan a URL and could be confused, though assess_risk explicitly returns a governance decision. check_headers overlaps heavily with the headers module inside scan_url, creating ambiguity about which tool to call. Descriptions help clarify intent, but some boundaries remain fuzzy.
Most tools follow a clear verb_noun snake_case pattern: scan_url, check_headers, scan_history, compare_scans, assess_risk. governance_policy deviates by using a noun_noun name rather than a verb-led action name like view_policy, but the overall naming style is still predictable.
Six tools is a well-scoped set for a security scanning and governance server. Each tool has a distinct role within the workflow, and the count is neither bloated nor too thin.
The tool surface covers scanning, risk assessment, governance policy, history, and comparison, which are the core needs for this domain. A minor gap is that users cannot retrieve detailed findings from a past scan, only grades and scores, but agents can work around this by re-scanning.