Ext Ops Panel
Open dashboard
Comparison

io.github.shawndei/glimind vs NotWorking

io.github.shawndei/glimind is an MCP server published by shawndei. Marketplaces we read that list it: 1 (Official MCP Registry). NotWorking is an MCP server published by notworking.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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.shawndei/glimindNotWorking
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 0.1.3
Forks (GitHub): 0
Stars (GitHub): 2
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.shawndei/glimind vs NotWorking
Factio.github.shawndei/glimindNotWorking
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (glimind.com/mcp)Remote server (notworking.io/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/shawndei/mcpinfrastructuregithub.com/ryannsj/notworking
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days agoResponded 3 days 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

io.github.shawndei/glimind

In its own words, on Official MCP Registry:

Live reliability for AI agent tools: is it working right now, and how do I call it correctly?

NotWorking

In its own words, on Official MCP Registry:

Downdetector for AI agents: stop paying for retries that can't succeed. Check once, then report.

How to run each

io.github.shawndei/glimind As a remote MCP server

Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp

NotWorking As a remote MCP server

Claude Code
claude mcp add --transport http notworking https://notworking.io/mcp

Commands 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 the marketplaces of io.github.shawndei/glimind nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.shawndei/glimind · What it can do: NotWorking · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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