Ext Ops Panel
Open dashboard
Comparison

citepath vs Probe V0

citepath is an MCP server published by citepath.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Probe V0 is an MCP server published by lexbritten. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
MarketplacecitepathProbe V0
Official MCP Registry Listed
Version: 0.1.1
No figure published
Not marked · First seen
Listed
Version: 0.1.0
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

citepath vs Probe V0
FactcitepathProbe V0
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (citepath.ai/api/mcp)Remote server (probe-evidence.probe-lab.workers.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/homezloco/citepathgithub.com/lexbritten/probe-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 5 days ago returned HTTP 308Status out of date: last check 5 days ago returned HTTP 405

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

citepath

In its own words, on Official MCP Registry:

Citepath public MCP server for LLM readiness audits and public scan results.

Probe V0

In its own words, on Official MCP Registry:

Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.

How to run each

citepath As a remote MCP server

Claude Code
claude mcp add --transport http citepath https://citepath.ai/api/mcp

Probe V0 As a remote MCP server

Claude Code
claude mcp add --transport http probe https://probe-evidence.probe-lab.workers.dev/mcp

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

Only the endpoint of Probe V0 responded at the last daily 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: citepath · What it can do: Probe V0 · 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