Is the npm:@pharmatools/pubcrawl MCP server safe to use?
Independent trust grade C- (70/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:@pharmatools/pubcrawl for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.
What it offers — 4 tools · Database
get_abstract
Get the full structured abstract and metadata for a PubMed article. Returns abstract sections (background, methods, results, conclusions), keywords, M
format_citation
Format a citation for a PubMed article in APA, Vancouver, Harvard, or BibTeX style.
compare_labels
Compare US FDA Prescribing Information vs UK/EU SmPC for a drug side-by-side. Maps equivalent sections (e.g., US Indications ↔ UK 4.1) and returns pai
get_full_text
Get the full text of an open-access article from PubMed Central. Returns article sections, figure/table captions, and reference count. Only works for
INFO Static analysis of npm package @pharmatools/pubcrawl@2.1.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:@pharmatools/pubcrawl on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.