io.github.joepangallo/mcp-server-security-audit
NPM · MCP-SERVER-SECURITY-AUDIT · SCANNED SEP 25
Scan websites for security vulnerabilities, headers, TLS, and email security.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 207 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 516 tokens (~51/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.joepangallo/mcp-server-security-audit server?
io.github.joepangallo/mcp-server-security-audit runs locally as an npm package, launched with npx -y mcp-server-security-audit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-server-security-audit
claude mcp add joepangallo-mcp-server-security-audit -- npx -y mcp-server-security-audit
{
"mcpServers": {
"joepangallo-mcp-server-security-audit": {
"command": "npx",
"args": [
"-y",
"mcp-server-security-audit"
]
}
}
} {
"servers": {
"joepangallo-mcp-server-security-audit": {
"command": "npx",
"args": [
"-y",
"mcp-server-security-audit"
]
}
}
} codex mcp add joepangallo-mcp-server-security-audit -- npx -y mcp-server-security-audit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joepangallo-mcp-server-security-audit": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-server-security-audit"
],
"enabled": true
}
}
} openclaw mcp add joepangallo-mcp-server-security-audit --command npx --arg -y --arg mcp-server-security-audit
mcp_servers:
joepangallo-mcp-server-security-audit:
command: "npx"
args: ["-y", "mcp-server-security-audit"] {
"McpServers": {
"joepangallo-mcp-server-security-audit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-server-security-audit"
]
}
}
} assistant mcp add joepangallo-mcp-server-security-audit -t stdio -c npx -a -y mcp-server-security-audit
{
"mcpServers": {
"joepangallo-mcp-server-security-audit": {
"command": "npx",
"args": [
"-y",
"mcp-server-security-audit"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/mcp-server-security-audit@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
api_usage ~24
Check your current API usage — scans remaining, monitors active, and plan limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compare_sites ~55
Compare the security posture of two websites side by side. Runs quick scans on both and returns scores, grades, and differences.
| Name | Type | Req | Description |
|---|---|---|---|
| url1 | string | yes | First website URL |
| url2 | string | yes | Second website URL |
No output schema declared.
No examples provided.
discover_subdomains ~53
Discover subdomains for a domain using Certificate Transparency logs. Returns list of subdomains with reachability status, HTTP status codes, and response times.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The root domain to discover subdomains for |
No output schema declared.
No examples provided.
full_security_audit ~79
Run a comprehensive security audit with AI analysis, endpoint discovery, and vulnerability scanning (Nuclei). Requires an API key (paid plan). Returns detailed findings, critical issues, and prioritized fix recommendations with code snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email to receive the report (optional) | |
| url | string | yes | The website URL to audit |
No output schema declared.
No examples provided.
get_audit_result ~35
Retrieve the result of a previously started audit by its job ID.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The audit job ID |
No output schema declared.
No examples provided.
scan_history ~48
Get the security scan history for a domain, showing how its score and grade have changed over time.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to get history for (e.g. 'example.com') |
No output schema declared.
No examples provided.
score_trend ~43
Get the security score trend for a domain — whether it's improving, declining, or stable over recent scans.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check trend for |
No output schema declared.
No examples provided.
security_check ~68
Quick pass/fail security check for CI/CD pipelines. Returns score, grade, and whether it meets the minimum threshold. Fast — typically under 10 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| min_score | number | – | Minimum passing score (default: 70) |
| url | string | yes | The website URL to check |
No output schema declared.
No examples provided.
security_dashboard ~31
Get your security dashboard — overview of all monitored domains, scores, trends, and alerts. Requires an API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
security_scan ~80
Run a quick passive security scan on any website. Returns score (0-100), grade (A+ to F), security headers, TLS/SSL status, cookie issues, and email security. Free, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website URL to scan (e.g. 'example.com' or 'https://example.com') |
No output schema declared.
No examples provided.
What is the io.github.joepangallo/mcp-server-security-audit server?
io.github.joepangallo/mcp-server-security-audit is listed in the public MCP registry as io.github.joepangallo/mcp-server-security-audit. Scan websites for security vulnerabilities, headers, TLS, and email security. This page covers its npm package (mcp-server-security-audit).
Is the io.github.joepangallo/mcp-server-security-audit server safe to use?
io.github.joepangallo/mcp-server-security-audit scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.joepangallo/mcp-server-security-audit server expose?
io.github.joepangallo/mcp-server-security-audit exposes 10 tools: security_scan, full_security_audit, security_check, scan_history, score_trend, and 5 more. Their descriptions and schemas cost roughly 516 tokens of context every time the server is loaded.
Is the io.github.joepangallo/mcp-server-security-audit server still maintained?
io.github.joepangallo/mcp-server-security-audit is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.joepangallo/mcp-server-security-audit server under?
io.github.joepangallo/mcp-server-security-audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.