
Coinintel
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Crypto market intelligence: prices, sentiment, risk, narratives, funding and signals.
Overview
Coinintel's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Coinintel in the dashboard and add it to a workspace.
- 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
coinintel
coinintel wraps a read-only crypto market-intelligence API: finding and resolving coins, current prices and history, per-coin sentiment, risk and signals, market-wide health, sentiment and regime reads, trend and coin scans, narratives, categories, and funding momentum and alerts. One binary serves a command-line interface and a stdio MCP server.
An API key is required. Set SHUMI_TOKEN before use; when it
is missing or blank, every tool fails with an error naming
SHUMI_TOKEN before any request is made. The key is sent as
the x-api-key header. The API base URL can be overridden
with SHUMI_API_URL; when it is not set, calls go to
https://api.shumi.ai (a reconstruction — the upstream README
does not publish a base URL).
List-returning tools share a convention: top (an integer)
keeps only the first N entries, and fields (a comma-separated
list of names) keeps only those fields on each entry. Both are
sent to the API, and the same trimming is applied to array
responses locally.
This build is a labelled core subset: 20 read-only tools. The upstream tool set also documents signal-quality, pair suggestions, real-world-asset, unlock, holder, wallet, futures, basket, transcript, question-answering, and web-search tools; those are not part of this subset.
Install
Or run the container image:
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
CLI
The subcommands mirror the MCP tool names:
Results print the upstream JSON payload. Exit codes: 0 on
success, 1 when a call fails (including a missing token or an
upstream API error), 2 for usage errors.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio
MCP server:
MCP client configuration:
Tools
Development
License
MIT — see LICENSE.
Source: README.md at commit e5cfff8
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% 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