Ext Ops Panel
Open dashboard
Comparison

nagomi vs com.titratelab/evidence

nagomi is a plugin bundle for AI coding tools published by avivlyweb. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.titratelab/evidence is an MCP server published by titratelab.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplacenagomicom.titratelab/evidence
Claude Code: claude-plugins-community Listed
Version: 1.4.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.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

nagomi vs com.titratelab/evidence
Factnagomicom.titratelab/evidence
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (titratelab.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/avivlyweb/nagomi-pubmed-pluginNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago, requires a key

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

nagomi

In its own words, on Claude Code: claude-plugins-community:

Forensic-grade PubMed research engine for Claude Code. Search 36M+ biomedical articles with PICO-structured queries, synthesize evidence with GRADE confidence ratings, critically appraise article trustworthiness using Oxford CEBM hierarchy, verify citation accuracy against PubMed records, and export references in APA/Vancouver/BibTeX. Includes a research-assistant agent for comprehensive literature reviews. No API key required — queries PubMed E-utilities directly.

com.titratelab/evidence

In its own words, on Official MCP Registry:

Find lab-report identities and clinical research with dated sources and evidence limitations.

How to run each

nagomi As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install nagomi@claude-community

com.titratelab/evidence As a remote MCP server

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

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

Only com.titratelab/evidence 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: nagomi · What it can do: com.titratelab/evidence · 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.

Where the data comes from: how the catalog is built