# ARKOSCOPE Public Sources (mcpb · arkoscope-verified-sources-1.0.1.mcpb) Read-only, dated public crypto source registry with evidence status. Local stdio; no API keys. - Trust score: 38/100 (low) - Change this week: 0 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - mcpb · `arkoscope-verified-sources-1.0.1.mcpb`: 38/100 (this document), [markdown](https://verifymcp.io/servers/arkoscope-crypto-verified-sources/arkoscope-verified-sources.md), [page](https://verifymcp.io/servers/arkoscope-crypto-verified-sources/arkoscope-verified-sources) ## Channel facts - Registry: `mcpb` - Package: `https://github.com/arkoscope/awesome-crypto-verified-sources/releases/download/mcp-v1.0.1/arkoscope-verified-sources-1.0.1.mcpb` - Transport: `stdio` - SHA-256: `4865ca0fa64b4ea5d10a0cb1931c982831d1041cceedcf492c3ae20f9d042a5e` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - 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. - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none). - Install-script risk not yet assessed. - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none). - **Provenance & Transparency**: 45/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 8 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 74/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (fair). - Tool/resource definitions use about 117 tokens (~39/item across 3 items; 2 tools + 1 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **Tool Coverage**: 67/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). **Unverified: 2 categories.** Categories scored 0 because we could not verify them: 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. ## Install ### How do I install the ARKOSCOPE Public Sources MCP server? ARKOSCOPE Public Sources 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, 4865ca0fa64b4ea5d10a0cb1931c982831d1041cceedcf492c3ae20f9d042a5e; the commands to do that are on this page. If it does not match, do not open it. - Download bundle: `https://github.com/arkoscope/awesome-crypto-verified-sources/releases/download/mcp-v1.0.1/arkoscope-verified-sources-1.0.1.mcpb` - SHA-256: `4865ca0fa64b4ea5d10a0cb1931c982831d1041cceedcf492c3ae20f9d042a5e` ### Verify on macOS / Linux ```bash echo "4865ca0fa64b4ea5d10a0cb1931c982831d1041cceedcf492c3ae20f9d042a5e arkoscope-verified-sources-1.0.1.mcpb" | shasum -a 256 -c ``` ### Verify on Windows (PowerShell) ```powershell (Get-FileHash -Algorithm SHA256 .\arkoscope-verified-sources-1.0.1.mcpb).Hash -eq "4865ca0fa64b4ea5d10a0cb1931c982831d1041cceedcf492c3ae20f9d042a5e" ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-27 (score 38) First indexed and scored. ## MCP tools (2) ### `list_projects` (~49 tokens) List projects in the bundled, dated public ARKOSCOPE registry. Optional bounded text filter. No live feed or private API access. Input parameters: - `query` (string) - `wave` (integer) ### `get_project_sources` (~47 tokens) Return an exact project name, ticker or id with public source URLs and evidence levels. Unknown inputs are not guessed. Does not fetch URLs or certify safety. Input parameters: - `project` (string, required) ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/arkoscope-crypto-verified-sources/arkoscope-verified-sources#diagnostics ## Score history - 2026-11-05: 38 - 2026-11-04: 38 - 2026-11-03: 38 - 2026-11-02: 38 - 2026-11-01: 38 - 2026-10-31: 38 - 2026-10-30: 38 - 2026-10-29: 38 - 2026-10-28: 38 - 2026-10-27: 38 ## Common questions ### What is the ARKOSCOPE Public Sources MCP server? ARKOSCOPE Public Sources is an MCP server listed in the public MCP registry as io.github.arkoscope/crypto-verified-sources. Read-only, dated public crypto source registry with evidence status. Local stdio; no API keys. This page covers its MCPB bundle (https://github.com/arkoscope/awesome-crypto-verified-sources/releases/download/mcp-v1.0.1/arkoscope-verified-sources-1.). ### Is the ARKOSCOPE Public Sources MCP server safe to use? ARKOSCOPE Public Sources scores 38 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. ### What tools does the ARKOSCOPE Public Sources MCP server expose? ARKOSCOPE Public Sources exposes 2 tools: list_projects, get_project_sources. Their descriptions and schemas cost roughly 96 tokens of context every time the server is loaded. ### What licence is the ARKOSCOPE Public Sources MCP server under? ARKOSCOPE Public Sources declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - Repository: https://github.com/arkoscope/awesome-crypto-verified-sources - Changelog RSS feed: https://verifymcp.io/servers/arkoscope-crypto-verified-sources/arkoscope-verified-sources.xml - Changelog JSON feed: https://verifymcp.io/servers/arkoscope-crypto-verified-sources/arkoscope-verified-sources.json - HTML version of this page: https://verifymcp.io/servers/arkoscope-crypto-verified-sources/arkoscope-verified-sources