sourceverify vs refcheck
sourceverify is a plugin bundle for AI coding tools published by SourceVerify-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). refcheck is an MCP server published by benchoi93. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.0-beta Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 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
| Fact | sourceverify | refcheck |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (refcheck-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 4 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/sourceverify-ai/sourceverify-skill | github.com/umn-choi-lab/refcheck |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
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
sourceverify
Verify academic citations and references using the SourceVerify API
refcheck
Verify academic citations against real databases. Catches hallucinated references, exports BibTeX.
How to run each
sourceverify
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
refcheck As a local MCP server: PyPI package
claude mcp add --env "ELSEVIER_INSTTOKEN=<YOUR_ELSEVIER_INSTTOKEN>" --env "ELSEVIER_KEY=<YOUR_ELSEVIER_KEY>" --env "IEEE_API_KEY=<YOUR_IEEE_API_KEY>" --env "S2_API_KEY=<YOUR_S2_API_KEY>" --transport stdio refcheck -- uvx refcheck-mcpRequires: ELSEVIER_INSTTOKEN (secret), ELSEVIER_KEY (secret), IEEE_API_KEY (secret), S2_API_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
The marketplaces of sourceverify publish no settings it asks for, so we do not compare settings.
What it can do: sourceverify · What it can do: refcheck · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.