Keyspoor
NPM · KEYSPOOR · SCANNED OCT 4
Offline secret scanning for AI agents. Redacted findings; scans text and files in a chosen root.
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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to majiayu000/keyspoor). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 143 tokens (~71/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Keyspoor MCP server?
Keyspoor runs locally as an npm package, launched with npx -y keyspoor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · keyspoor
claude mcp add majiayu000-keyspoor -- npx -y keyspoor
{
"mcpServers": {
"majiayu000-keyspoor": {
"command": "npx",
"args": [
"-y",
"keyspoor"
]
}
}
} {
"servers": {
"majiayu000-keyspoor": {
"command": "npx",
"args": [
"-y",
"keyspoor"
]
}
}
} codex mcp add majiayu000-keyspoor -- npx -y keyspoor
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"majiayu000-keyspoor": {
"type": "local",
"command": [
"npx",
"-y",
"keyspoor"
],
"enabled": true
}
}
} openclaw mcp add majiayu000-keyspoor --command npx --arg -y --arg keyspoor
mcp_servers:
majiayu000-keyspoor:
command: "npx"
args: ["-y", "keyspoor"] {
"McpServers": {
"majiayu000-keyspoor": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"keyspoor"
]
}
}
} assistant mcp add majiayu000-keyspoor -t stdio -c npx -a -y keyspoor
{
"mcpServers": {
"majiayu000-keyspoor": {
"command": "npx",
"args": [
"-y",
"keyspoor"
]
}
}
} 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.
- 4 Oct 26 78
First indexed and scored.
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 4 Oct 2026 · Analysed npm/keyspoor@0.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | majiayu000/keyspoor |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/majiayu000/keyspoor/.github/workflows/release.yml@refs/tags/v0.1.3 |
| Rekor log index | 3076537291 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:59a884036fcbef86b0c36ea42279d467ad902c5e02cd86951736871d32c8e8382fc1b721c6eb3b36857bb50125b5296140a4ce43b54faa2936eea7baa |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
scan_paths ~70
Read files or directories within the configured server root, respecting ignore files. Does not follow directory symlinks. Returns a bounded redacted preview with complete, total counts and output_truncated. Only one scan may run at a time; requests support cancellation and optional progressToken.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | – |
No output schema declared.
No examples provided.
scan_text ~73
Scan supplied text offline. Returns a redacted report with at most 100 findings/errors and a shared 512 KiB preview budget. Check complete, finding_count, error_count and output_truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Logical filename, not read from disk; defaults to stdin |
| text | string | yes | – |
No output schema declared.
No examples provided.
What is the Keyspoor MCP server?
Keyspoor is an MCP server listed in the public MCP registry as io.github.majiayu000/keyspoor. Offline secret scanning for AI agents. Redacted findings; scans text and files in a chosen root. This page covers its npm package (keyspoor).
Is the Keyspoor MCP server safe to use?
Keyspoor scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Keyspoor MCP server expose?
Keyspoor exposes 2 tools: scan_text, scan_paths. Their descriptions and schemas cost roughly 143 tokens of context every time the server is loaded.
Is the Keyspoor MCP server still maintained?
Keyspoor is still listed as active in the MCP registry. We last reached this channel on 4 October 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 Keyspoor MCP server under?
Keyspoor declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.