MCP servers for cryptocurrency
MCP servers whose description mentions a cryptocurrency, a blockchain or a marketplace for one.
1,410 servers 3.2% of 43,736 in the directory
This category in numbers
- 795 56 % Execution location: remote
- 1,001 71 % Repository URL listed: yes
- 1,227 87 % Required secrets declared: no
- 785 56 % Delivery form (raw): remote
The most frequent value per property, counted across the entries of this category. The full distribution is further down.
Entries
Filter further
- Execution location: local
- Execution location: remote
- Required secrets declared: no
- Required secrets declared: yes
- Repository URL listed: yes
- Repository URL listed: no
- recently updated first
Entries 1,401 to 1,410 of 1,410
| xyz.fluxiq/agent | xyz.fluxiq/agent |
|---|---|
| xyz.getava/ava | xyz.getava/ava |
| xyz.groundtruths/groundtruth | xyz.groundtruths/groundtruth |
| xyz.lonestaroracle/mcp-server | xyz.lonestaroracle/mcp-server |
| xyz.mindjack/mcp | xyz.mindjack/mcp |
| xyz.tenzro/tenzro | xyz.tenzro/tenzro |
| xyz.tenzro/tenzro-ethereum | xyz.tenzro/tenzro-ethereum |
| xyz.tenzro/tenzro-solana | xyz.tenzro/tenzro-solana |
| yieldprobe: DeFi intel for agents | com.yieldprobe/defi-intel |
| zFinia Intelligence | com.zfinia.api/intelligence |
All 1,410 entries in the list, with filters and pagination
What this category selects
| Field of use, derived from the vendor description | Cryptocurrency derived from: Description (raw) |
|---|
A derived value carries its original data beside it; the derivation rule is published, with a version, on the methodology page.
Caveats, distribution and query
What this category does not say
- Field of use, derived from the vendor description is not declared but computed: from Description (raw). The rule is published, with a version, on the methodology page.
What is measured is what a manifest declares, not what a piece of software does. This registry fetches no repository URL, no endpoint and no package index; nothing here is verified. Which value comes from which source, and by which rule it was formed, is set out in the Methodology.
Every sentence here follows from the condition above, not from an assessment.
How this category is distributed
Delivery form (raw)
1,410| remote | 785 56 % |
|---|---|
| package | 506 36 % |
| package and remote | 95 6.7 % |
| neither | 24 1.7 % |
Execution location
1,410| remote | 795 56 % |
|---|---|
| local | 615 44 % |
Repository platform (raw)
1,410| github | 1,000 71 % |
|---|---|
| nothing declared | 409 29 % |
| gitlab | 1 0.1 % |
Repository URL listed
1,410| yes | 1,001 71 % |
|---|---|
| no | 409 29 % |
Required secrets declared
1,410| no | 1,227 87 % |
|---|---|
| yes | 183 13 % |
Icon formats (raw)
1,410| nothing declared | 1,261 89 % |
|---|---|
| image/png | 86 6.1 % |
| image/svg+xml | 37 2.6 % |
| image/png, image/svg+xml | 20 1.4 % |
| image/jpeg | 5 0.4 % |
| image/webp | 1 0.1 % |
Per property, the measured values inside this category. The share refers to the 1,410 entries of the category, not to the registry. Shown are 6 of 8 properties: those whose values spread the most inside this category.
The same category through the interface
curl -s "https://api.tracevero.com/v1/eintraege?art=mcp_server&einsatzgebiet=kryptowaehrung&grenze=200"
The command carries exactly the condition of this page. 1,410 entries at 200 each are 8 requests; the total is in the X-Gesamt header.
Changes to these entries
https://tracevero.com/aenderungen.atom?thema=einsatz-kryptowaehrung
Both addresses narrow the change stream to exactly the entries in this category. The feed carries an identifier of its own, so a feed reader keeps it apart from the full stream.
Categories sharing entries with this one
Per neighbour its own size and the counted number of shared entries. A category without a single shared entry is not listed here.
tracevero · https://tracevero.com/themen/einsatz-kryptowaehrung?seite=29