ARKOSCOPE Public Sources

io.github.arkoscopePublished by GitHub account arkoscopev1.0.1Updated Oct 29, 2026

Read-only, dated public crypto source registry with evidence status. Local stdio; no API keys.

The publisher's own server: verified.fyi

VerifiedSTDIODesktop onlyFinanceKnowledge & Memory

Overview

AI-generated overview

A local, read-only MCP server that lets an assistant look up projects in a bundled, dated public crypto source registry with evidence status.

What you can do
  • List projects by optional query (up to 80 characters) and wave, returning names, tickers and stable lookup IDs
  • Fetch a project's sources by exact name, ticker or ID, returning URLs, evidence status, check date and scope notes
  • Read the whole dated public registry as a single resource
  • Report unknown or ambiguous names instead of guessing
When to use it
Useful when you want an assistant to check which public sources back a crypto project and how recently they were verified, from a fixed offline snapshot. It is not a live news feed or a phishing detector.
Requirements
Node.js 20 or later and a local clone of the public repository, run as a stdio process via node with an absolute path to server.mjs. No API keys, tokens, wallet or environment variables are needed, and it makes no runtime network calls.
Before you install
Read-only and offline: it only reads the bundled sources.json and never writes, fetches URLs or executes commands. Data is a snapshot, so updates require a new checkout. Some X references are not reconfirmed by a current official-site link, and a listing does not certify a project or its security.

Installation

In SourceWeft

  1. Open ARKOSCOPE Public Sources in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ARKOSCOPE Public Sources MCP

A local, read-only Model Context Protocol server for the public ARKOSCOPE source registry. Two tools, one resource, no keys, no private backend, no runtime network calls. It is not a live crypto news feed or a phishing detector.

Install and run

Node.js 20 or later. Clone this public repository, then:

sh
cd awesome-crypto-verified-sources/mcp-servernpm ci --ignore-scriptsnpm testnpm start

The process speaks MCP on stdin/stdout. Do not run it as an HTTP server. GitHub Pages hosts only the static directory; it cannot host this Node process. No server has to be left running on ARKOSCOPE's Mac.

Client configuration

Use your client's local stdio configuration, with an absolute path to your own clone:

json
{  "mcpServers": {    "arkoscope-public-sources": {      "command": "node",      "args": ["/absolute/path/awesome-crypto-verified-sources/mcp-server/server.mjs"]    }  }}

No environment variables, access tokens or wallet are required. This repository does not install or change any client configuration automatically.

Tools and data

InterfaceInputResult
list_projectsOptional query (80 characters maximum), optional wave (1–3)Names, tickers and stable lookup IDs
get_project_sourcesExact project name, ticker or IDURLs, evidence status, check date, scope notes
arkoscope://public/sourcesResource readThe same dated public registry

Example: get_project_sources with {"project":"SOL"}. Unknown or ambiguous names are reported, never guessed. The only file read at startup is the bundled ../sources.json. Tool arguments never select paths, execute commands or fetch URLs. Updates require an explicit new checkout of the public data.

Every result includes the requested ARKOSCOPE attribution and the limitations. Some X references are retained from the public Android catalogue but have not been reconfirmed by a current official-site link; those evidence statuses are returned unchanged. A source listing does not certify a project, claim or future security. iOS approval is distinct from public App Store availability.

Validation and licensing

npm test performs a real MCP client/server stdio handshake, checks both tools and the resource, preserves evidence levels, rejects unknown paths and overlong input, and confirms that the registry was not written. Dependencies are pinned in package-lock.json.

The new server code is MIT licensed; see LICENSE. Third-party dependencies retain their own licenses. Project names, logos, trademarks and external content are not relicensed. This project is maintained by ARKOSCOPE SRL (Brussels), independently of the listed protocols.

Français

Ce connecteur consulte uniquement le registre JSON public livré avec le dépôt. Il ne contacte ni Cloudflare, ni l’application privée, ni un portefeuille. Il ne publie aucun message et ne fournit pas de nouvelles en direct. Les références encore à reconfirmer restent explicitement signalées. Installation locale facultative ; aucun compte payant requis.

Source: mcp-server/README.md at commit 2751da7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestOct 29, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Verified integrations