revenium-mcp vs dev.onchainforensics/forensics-mcp
revenium-mcp is an MCP server published by revenium. Marketplaces we read that list it: 1 (PyPI (MCP servers)). dev.onchainforensics/forensics-mcp is an MCP server published by onchainforensics.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  revenium-mcp |  dev.onchainforensics/forensics-mcp |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.11.1 Downloads/month (PyPI): 653 Downloads/week (PyPI): 297 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.1 Forks (GitHub): 0 Stars (GitHub): 0 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 | revenium-mcp | dev.onchainforensics/forensics-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-11-09 | Not published |
| Where it runs (differs) | On your machine (revenium-mcp) | Remote server or your machine |
| Transport (differs) | Not stated | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/revenium/revenium-mcp | github.com/leohoudinisanders-byte/forensics-mcp |
| Changes in the last 7 days (differs) | 2 | 3 |
| First seen (differs) | 2026-10-13 | 2026-10-20 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 31 h ago returned HTTP 200 |
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
revenium-mcp
Model Context Protocol (MCP) server for Revenium API monitoring, analytics, and AI spending management
dev.onchainforensics/forensics-mcp
Token due-diligence for AI agents: grade verdicts, mint activity, settlement safety.
How to run each
revenium-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
dev.onchainforensics/forensics-mcp As a local MCP server: npm package
claude mcp add --transport stdio forensics-mcp -- npx -y onchain-forensics-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only dev.onchainforensics/forensics-mcp has a remote endpoint we 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: revenium-mcp · What it can do: dev.onchainforensics/forensics-mcp · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.