Ext Ops Panel
Open dashboard
Comparison

io.github.nexus-api-lab/digest-mcp vs devutils

io.github.nexus-api-lab/digest-mcp is an MCP server published by nexus-api-lab. Marketplaces we read that list it: 1 (Official MCP Registry). devutils is an MCP server published by devutils.bigfloppy.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
Marketplaceio.github.nexus-api-lab/digest-mcpdevutils
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 1.0.2
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

io.github.nexus-api-lab/digest-mcp vs devutils
Factio.github.nexus-api-lab/digest-mcpdevutils
Marketplaces that list it11
Last release (differs)Not published2026-10-26
Where it runs (differs)Remote server (digest-mcp.dokasukadon.workers.dev/mcp)Remote server (devutils.bigfloppy.net/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/wminno/devutils
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-10-25
Endpoint at the last check (differs)Answered with HTTP 404 (6 days ago)not checked yet

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

io.github.nexus-api-lab/digest-mcp

In its own words, on Official MCP Registry:

Exact hashing, base64/hex/URL encoding, JWT decoding and UUIDs for AI agents. No auth required.

devutils

In its own words, on Official MCP Registry:

Free hosted dev toolkit: uuid, hash, base64, JWT decode, CSV->JSON, time, JSON tools as MCP

How to run each

io.github.nexus-api-lab/digest-mcp As a remote MCP server

Claude Code
claude mcp add --transport http digest-mcp https://digest-mcp.dokasukadon.workers.dev/mcp

devutils As a remote MCP server

Claude Code
claude mcp add --transport http devutils https://devutils.bigfloppy.net/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.nexus-api-lab/digest-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: io.github.nexus-api-lab/digest-mcp · What it can do: devutils · 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.

Where the data comes from: how the catalog is built