Comparison

io.github.cyanheads/usda-mcp-server vs Fruityvice

io.github.cyanheads/usda-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). Fruityvice is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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

Where each is published
Marketplace	io.github.cyanheads/usda-mcp-server	Fruityvice
Official MCP Registry	Listed Version: 0.2.1 Downloads/month (npm): 1 192 Downloads/week (npm): 126 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen 2026-10-11	Listed Version: 1.1.1 Downloads/month (npm): 837 Downloads/week (npm): 127 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen 2026-10-11

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.cyanheads/usda-mcp-server vs Fruityvice
Fact	io.github.cyanheads/usda-mcp-server	Fruityvice
Marketplaces that list it	1	1
Stars (GitHub) (differs)	1 (better)	0 (worse)
Forks (GitHub)	0	0
Last release (differs)	2026-11-11 (better)	2026-11-02 (worse)
Where it runs (differs)	Remote server (usda.caseyjhand.com/mcp)	Remote server (gateway.pipeworx.io/fruityvice/mcp)
Transport	Streamable HTTP	Streamable HTTP
Tools it declares	Not published	Not published
Environment variables it asks for (differs)	8, secrets among them: 0	1, secrets among them: 1
Licence	Not stated	Not stated
Repository (differs)	github.com/cyanheads/usda-mcp-server	github.com/pipeworx-io/mcp-fruityvice
Changes in the last 7 days (differs)	2	0
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	Responded 18 h ago	Responded 23 h 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.cyanheads/usda-mcp-server

In its own words, on Official MCP Registry:

Search foods, compare nutrients, and look up the full USDA FoodData Central database.

Fruityvice

In its own words, on Official MCP Registry:

Fruityvice MCP — wraps Fruityvice API (free, no auth)

How to run each

io.github.cyanheads/usda-mcp-server As a remote MCP server

Claude Code

claude mcp add --transport http usda-mcp-server https://usda.caseyjhand.com/mcp

Requires: USDA_FDC_API_KEY

Fruityvice As a remote MCP server

Claude Code

claude mcp add --transport http fruityvice https://gateway.pipeworx.io/fruityvice/mcp

Requires: PIPEWORX_API_KEY (secret)

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

Only io.github.cyanheads/usda-mcp-server has

usda_compare_foods
usda_get_food
usda_get_foods
usda_list_nutrients
usda_search_foods

Only Fruityvice has

ai_visibility_check
archive_compare
archive_evidence
ask_pipeworx
ask_pipeworx_beta
ask_pipeworx_grounded
bet_research
classify_row
company_facts
company_register_search
compare_entities
deep_research

Show the remaining 35

discover_tools
entity_profile
forget
generate_llms_txt
get_by_nutrition
get_fruit
kalshi_weather_edge
list_fruits
list_subscriptions
pipeworx_feedback
pipeworx_trending
polymarket_arbitrage
polymarket_edge_tracker
polymarket_edges
polymarket_fill_risk
polymarket_kalshi_spread
prediction_calibration
recall
recent_alerts
recent_changes
release_calendar_markets
remember
research_row
resolution_audit
resolution_diff
resolve_entity
scan_competitor_ai_presence
scan_dependency
search_within
subscribe
suggest_questions
unsubscribe
updown_divergence_rate
updown_venue_compare
validate_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.cyanheads/usda-mcp-server as of 2026-11-06; Fruityvice as of 2026-11-06). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only io.github.cyanheads/usda-mcp-server asks for

MCP_AUTH_MODE
MCP_HTTP_ENDPOINT_PATH
MCP_HTTP_HOST
MCP_HTTP_PORT
MCP_LOG_LEVEL
MCP_TRANSPORT_TYPE
USDA_CLAMP_LIMITS
USDA_FDC_API_KEY

Only Fruityvice asks for

PIPEWORX_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.cyanheads/usda-mcp-server · What it can do: Fruityvice · 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 2026-11-12. We publish no contact details for plugin publishers.