io.github.atushi1841/kensho-sweep-mcp
MCPB · SERVER.MCPB
Sweep MCP. Apify apify.com/fruitful_quintessence | Gumroad: https://atushi5.gumroad.com/l/kutuxe
Available components
Last scanned (24 days ago)
Scores higher than 0% of MCPB servers
Category News and Social
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security12
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 15 of 15 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Install-script risk not yet assessed.Unverified
- 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).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 Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need 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 the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 12 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Oct 26 13
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 12 Oct 2026 · Analysed mcpb/https://github.com/atushi1841/kensho-sweep-mcp/releases/download/v1.0.0/server.mcpb@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 1 |
| 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.
How do I install the io.github.atushi1841/kensho-sweep-mcp server?
io.github.atushi1841/kensho-sweep-mcp ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 55b8d8520c6eaac76828518d86b8b625adbc3b1da371854fd500095ab6be1a97; the commands to do that are on this page. If it does not match, do not open it.
mcpb · server.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
55b8d8520c6eaac76828518d86b8b625adbc3b1da371854fd500095ab6be1a97
macOS / Linux
echo "55b8d8520c6eaac76828518d86b8b625adbc3b1da371854fd500095ab6be1a97 server.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\server.mcpb).Hash -eq "55b8d8520c6eaac76828518d86b8b625adbc3b1da371854fd500095ab6be1a97"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the io.github.atushi1841/kensho-sweep-mcp server?
io.github.atushi1841/kensho-sweep-mcp is listed in the public MCP registry as io.github.atushi1841/kensho-sweep-mcp. Sweep MCP. Apify apify.com/fruitful_quintessence | Gumroad: https://atushi5.gumroad.com/l/kutuxe. This page covers its MCPB bundle (https://github.com/atushi1841/kensho-sweep-mcp/releases/download/v1.3.0/server.mcpb).
Is the io.github.atushi1841/kensho-sweep-mcp server safe to use?
io.github.atushi1841/kensho-sweep-mcp scores 0 out of 100 on VerifyMCP. 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 io.github.atushi1841/kensho-sweep-mcp server still maintained?
io.github.atushi1841/kensho-sweep-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. 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.atushi1841/kensho-sweep-mcp server under?
io.github.atushi1841/kensho-sweep-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.