Ext Ops Panel
Open dashboard
Comparison

sublinear-time-solver vs io.github.ejentum/self-inspect-mcp

sublinear-time-solver is an MCP server published by ruvnet. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.ejentum/self-inspect-mcp is an MCP server published by ejentum. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
Marketplacesublinear-time-solverio.github.ejentum/self-inspect-mcp
npm registry (MCP servers) Listed
Version: 1.8.0
Downloads/month (npm): 4 099
Downloads/week (npm): 1 205
Forks (GitHub): 36
Stars (GitHub): 93
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 112
Downloads/week (npm): 44
Forks (GitHub): 2
Stars (GitHub): 7
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

sublinear-time-solver vs io.github.ejentum/self-inspect-mcp
Factsublinear-time-solverio.github.ejentum/self-inspect-mcp
Marketplaces that list it11
Stars (GitHub) (differs)93 (better)7 (worse)
Forks (GitHub) (differs)36 (better)2 (worse)
Last release (differs)2026-11-06Not published
Where it runs (differs)On your machine (sublinear-time-solver)Remote server (api.ejentum.com/self-inspect-mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MIT OR Apache-2.0Not stated
Repository (differs)github.com/ruvnet/sublinear-time-solvergithub.com/ejentum/self-inspect-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (1 h ago)

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

sublinear-time-solver

In its own words, on npm registry (MCP servers):

Sparse linear solvers (Neumann, Jacobi, Gauss-Seidel, conjugate gradient), PageRank, personalized PageRank and local forward/backward push, as an MCP server, CLI and library. The dependency-free core ships separately as @ruvnet/sublinear-core.

io.github.ejentum/self-inspect-mcp

In its own words, on Official MCP Registry:

Send a thought, get one metathought that makes your agent inspect its own assumptions. Keyless.

How to run each

sublinear-time-solver

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.ejentum/self-inspect-mcp As a remote MCP server

Claude Code
claude mcp add --transport http self-inspect-mcp https://api.ejentum.com/self-inspect-mcp

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

Only io.github.ejentum/self-inspect-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: sublinear-time-solver · What it can do: io.github.ejentum/self-inspect-mcp · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.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.

Where the data comes from: how the catalog is built