Needle Remote vs LLMVerify
Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). LLMVerify is an MCP server published by subodhkc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  LLMVerify | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.8.0 Downloads/month (npm): 26 256 Downloads/week (npm): 3 734 Forks (GitHub): 17 Stars (GitHub): 18 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 | Needle Remote | LLMVerify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 18 |
| Forks (GitHub) (differs) | No figure on GitHub | 17 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.needle.app/mcp) | On your machine (llmverify) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 11, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/subodhkc/llmverify-npm |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
Needle Remote
Production-ready RAG service to search and retrieve data from your documents.
LLMVerify
Local-first MCP server for LLM output verification — risk signals, injection and PII checks.
How to run each
Needle Remote As a remote MCP server
claude mcp add --transport http needle https://mcp.needle.app/mcpRequires: NEEDLE_API_KEY (secret)
LLMVerify As a local MCP server: npm package
claude mcp add --env "LLMVERIFY_AUDIT_HASH_KEY=<YOUR_LLMVERIFY_AUDIT_HASH_KEY>" --transport stdio llmverify -- npx -y llmverify mcpRequires: LLMVERIFY_AUDIT_HASH_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Needle Remote asks for
NEEDLE_API_KEY (secret)
Only LLMVerify asks for
LLMVERIFY_AUDIT_DIRLLMVERIFY_AUDIT_HASH_KEY (secret)LLMVERIFY_AUDIT_NO_CONTENT_HASHLLMVERIFY_BASELINE_DIRLLMVERIFY_HOMELLMVERIFY_LOG_DIRLLMVERIFY_MCP_MAX_INPUT_CHARSLLMVERIFY_MCP_MAX_OUTPUT_ITEMSLLMVERIFY_MCP_MAX_TEXT_FIELD_CHARSLLMVERIFY_MCP_TIMEOUT_MSLLMVERIFY_USAGE_FILE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Needle Remote · What it can do: LLMVerify · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.