Skarn
NPM · @SKARN-SECURITY/SKARN · SCANNED SEP 21
Scans AI coding sessions and assistant configs for leaked secrets and risky hooks; local, redacted
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 Security100
- 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
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN EULA.md) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 885 tokens (~221/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 Skarn MCP server?
Skarn runs locally as an npm package, launched with npx -y @skarn-security/skarn. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @skarn-security/skarn
claude mcp add com-getskarn-skarn -- npx -y @skarn-security/skarn
{
"mcpServers": {
"com-getskarn-skarn": {
"command": "npx",
"args": [
"-y",
"@skarn-security/skarn"
]
}
}
} {
"servers": {
"com-getskarn-skarn": {
"command": "npx",
"args": [
"-y",
"@skarn-security/skarn"
]
}
}
} codex mcp add com-getskarn-skarn -- npx -y @skarn-security/skarn
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-getskarn-skarn": {
"type": "local",
"command": [
"npx",
"-y",
"@skarn-security/skarn"
],
"enabled": true
}
}
} openclaw mcp add com-getskarn-skarn --command npx --arg -y --arg @skarn-security/skarn
mcp_servers:
com-getskarn-skarn:
command: "npx"
args: ["-y", "@skarn-security/skarn"] {
"McpServers": {
"com-getskarn-skarn": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@skarn-security/skarn"
]
}
}
} assistant mcp add com-getskarn-skarn -t stdio -c npx -a -y @skarn-security/skarn
{
"mcpServers": {
"com-getskarn-skarn": {
"command": "npx",
"args": [
"-y",
"@skarn-security/skarn"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.30.0 → 0.31.0 functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 10 Sept 26 −16
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Schema quality: 163 → 221 ▼ functional
- Schema quality: 163 → 199 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.28.0 → 0.30.0 functional
- Package version: 0.28.0 → 0.29.0 functional
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 21 Sept 2026 · Analysed npm/@skarn-security/skarn@0.31.0
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 6 packages
| Packages resolved | 6 |
|---|---|
| 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 →
list_sessions List recent sessions ~233
List recent AI coding assistant sessions as structural metadata only: session id, assistant, timestamps, message and tool counts, and token totals. No session message text is returned, and no label authored inside a transcript such as a project name, git branch or model id. hours bounds the window, limit caps the row count, project, cli and user narrow the list; a row from a Compliance API export carries the recorded user id and never the email address. compliance_withheld counts the Compliance API export sessions that were found and withheld unread because reading them needs an Enterprise license; they contribute no row.
| Name | Type | Req | Description |
|---|---|---|---|
| cli | string | – | Only sessions recorded by this assistant, for example claude, codex or cursor. |
| hours | integer | – | Only sessions active in the last N hours. 0 lists all history. Default 168. |
| limit | integer | – | Maximum rows to return. Default 50. |
| project | string | – | Only sessions whose project name or path matches this filter. |
| user | string | – | Only sessions whose user id or email address matches this filter; only a Compliance API export carries either. |
No output schema declared.
No examples provided.
scan_sessions Scan sessions for leaked secrets ~231
Scan this machine's AI coding assistant session transcripts for leaked credentials and risky agent behaviour, and return the redacted JSON report as a text block. Each detected secret is reported in a truncated mask that keeps at most its first character and last two characters; the surrounding transcript snippet and the transcript-authored project label are not returned. severity sets the lowest reported level, hours bounds the window (0 scans all history and is the slowest form), project narrows to one project, user narrows to the user ids or email addresses a Compliance API export recorded. compliance_withheld counts the Compliance API export sessions that were found and withheld unread because reading them needs an Enterprise license; they contribute nothing to the counts.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Only sessions active in the last N hours. 0 scans all history. Default 0. |
| project | string | – | Only sessions whose project name or path matches this filter. |
| severity | string | – | Lowest severity to report. Default low. |
| user | string | – | Only sessions whose user id or email address matches this filter; only a Compliance API export carries either. |
No output schema declared.
No examples provided.
session_stats Session statistics ~176
Aggregate recent AI coding assistant sessions into counts: sessions per assistant, total messages, distinct projects, token totals and estimated cost. No session message text is returned. hours bounds the window, project, cli and user narrow what is aggregated. compliance_withheld counts the Compliance API export sessions that were found and withheld unread because reading them needs an Enterprise license; they contribute nothing to the counts.
| Name | Type | Req | Description |
|---|---|---|---|
| cli | string | – | Only sessions recorded by this assistant, for example claude, codex or cursor. |
| hours | integer | – | Only sessions active in the last N hours. 0 aggregates all history. Default 168. |
| project | string | – | Only sessions whose project name or path matches this filter. |
| user | string | – | Only sessions whose user id or email address matches this filter; only a Compliance API export carries either. |
No output schema declared.
No examples provided.
vet_configs Vet assistant configuration ~71
Statically vet this machine's AI assistant configuration - hook commands, MCP server definitions, permission grants, installed plugins and skills - and return the masked JSON findings report as a text block. Read-only: config files are opened for reading and never written. Project-level configuration is read from this server process's working directory.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Skarn MCP server?
Skarn is an MCP server listed in the public MCP registry as com.getskarn/skarn. Scans AI coding sessions and assistant configs for leaked secrets and risky hooks; local, redacted. This page covers its npm package (@skarn-security/skarn).
Is the Skarn MCP server safe to use?
Skarn scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Skarn MCP server expose?
Skarn exposes 4 tools: scan_sessions, vet_configs, list_sessions, session_stats. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.
Is the Skarn MCP server still maintained?
Skarn is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.