Skim MCP Server
NPM · SKIM-MCP-SERVER · SCANNED SEP 29
MCP server for Skim code transformation. Compresses code 60-95% for LLM context optimization.
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 Security74
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 21 of 43 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
- Repository check failed: no source repository is declared. 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 291 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
How do I install the Skim MCP Server server?
Skim MCP Server runs locally as an npm package, launched with npx -y skim-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · skim-mcp-server
claude mcp add luw2007-skim-mcp-server -- npx -y skim-mcp-server
{
"mcpServers": {
"luw2007-skim-mcp-server": {
"command": "npx",
"args": [
"-y",
"skim-mcp-server"
]
}
}
} {
"servers": {
"luw2007-skim-mcp-server": {
"command": "npx",
"args": [
"-y",
"skim-mcp-server"
]
}
}
} codex mcp add luw2007-skim-mcp-server -- npx -y skim-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"luw2007-skim-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"skim-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add luw2007-skim-mcp-server --command npx --arg -y --arg skim-mcp-server
mcp_servers:
luw2007-skim-mcp-server:
command: "npx"
args: ["-y", "skim-mcp-server"] {
"McpServers": {
"luw2007-skim-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"skim-mcp-server"
]
}
}
} assistant mcp add luw2007-skim-mcp-server -t stdio -c npx -a -y skim-mcp-server
{
"mcpServers": {
"luw2007-skim-mcp-server": {
"command": "npx",
"args": [
"-y",
"skim-mcp-server"
]
}
}
} 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 8 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 7 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 29 Sept 2026 · Analysed npm/skim-mcp-server@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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | npm run install-skim |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 43 packages
| Packages resolved | 43 |
|---|---|
| Stale | 21 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the Skim MCP Server server?
Skim MCP Server is listed in the public MCP registry as io.github.luw2007/skim-mcp-server. MCP server for Skim code transformation. Compresses code 60-95% for LLM context optimization. This page covers its npm package (skim-mcp-server).
Is the Skim MCP Server server safe to use?
Skim MCP Server scores 26 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 29 September 2026. 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.
Is the Skim MCP Server server still maintained?
Skim MCP Server is still listed as active in the MCP registry. We last reached this channel on 29 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 Skim MCP Server server under?
Skim MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.