Should my agent depend on the MCP server io.github.pipeworx-io/pubmed?

Verdict: allow — gateway — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Pubmed

io.github.pipeworx-io/pubmed

PubMed MCP — wraps the NCBI E-utilities API (biomedical literature, free, no auth)

— the operator's own registry description reported

Publisher io.github.pipeworx-io · first seen 2026-08-12 · endpoint https://gateway.pipeworx.io/pubmed/mcp

allow

verdict

gateway

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — gateway — safe to depend on

Cluster gateway · distinctiveness 0.737 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency47 ms

vs populationfast

protocolcurrent

authopen

Use — can it use it?

tools40

vs populationhigh

capabilities3

harnessA

Trust — can it rely on it?

identityfarm_member

servers on its host1312

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_842d1138b9c3935bdf5efdb5 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

ai_visibility_check ask_pipeworx ask_pipeworx_beta ask_pipeworx_grounded bet_research compare_entities deep_research discover_tools entity_profile forget generate_llms_txt get_abstract get_citations get_full_text get_related_articles get_summary list_subscriptions pipeworx_feedback pipeworx_trending polymarket_arbitrage polymarket_edge_tracker polymarket_edges polymarket_fill_risk polymarket_kalshi_spread pubmed_evidence_landscape pubmed_integrity_check pubmed_publication_trend recall recent_alerts recent_changes remember resolve_entity scan_competitor_ai_presence scan_dependency search_pubmed search_within subscribe suggest_questions unsubscribe validate_claim

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	40/40	✓
has a description	40/40	✓
description is substantive	40/40	✓
parameters are typed	40/40	✓
parameters are described	40/40	✓

40 of 40 tools graded · 40 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.1.0

server version pipeworx-gateway

Capabilities: prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:06Z	ok_tools	200	47	2025-06-18
2026-08-12T05:35:19Z	ok_tools	200	22	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.pipeworx-io/pubmed.svg)](https://robinsaige.com/s/io.github.pipeworx-io/pubmed)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview