dev.onchainforensics/forensics-mcp vs tech.htsapp/crypto-mcp
dev.onchainforensics/forensics-mcp is an MCP server published by onchainforensics.dev. Marketplaces we read that list it: 1 (Official MCP Registry). tech.htsapp/crypto-mcp is an MCP server published by htsapp.tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  dev.onchainforensics/forensics-mcp |  tech.htsapp/crypto-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | dev.onchainforensics/forensics-mcp | tech.htsapp/crypto-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (mcp.htsapp.tech/mcp) |
| Transport (differs) | stdio, Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/leohoudinisanders-byte/forensics-mcp | Not stated |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 31 h ago returned HTTP 200 | Status out of date: last check 36 h ago returned HTTP 406 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
dev.onchainforensics/forensics-mcp
Token due-diligence for AI agents: grade verdicts, mint activity, settlement safety.
tech.htsapp/crypto-mcp
Crypto rug/scam-risk scans + wallet snapshots (EVM + Solana), paid per call via x402.
How to run each
dev.onchainforensics/forensics-mcp As a local MCP server: npm package
claude mcp add --transport stdio forensics-mcp -- npx -y onchain-forensics-mcptech.htsapp/crypto-mcp As a remote MCP server
claude mcp add --transport http crypto-mcp https://mcp.htsapp.tech/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: dev.onchainforensics/forensics-mcp · What it can do: tech.htsapp/crypto-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.