Is deep_research working right now?

io.github.pipeworx-io/pubchem · mcp-registry/io.github.pipeworx-io/pubchem/deep_research

Recent contract changes

Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.

• schema_changed — pipeworx_feedback (2026-08-11)
• schema_changed — bet_research (2026-07-29)
• schema_changed — validate_claim (2026-07-15)
• added — ask_pipeworx_beta (2026-07-14)
• schema_changed — deep_research (2026-07-14)

See all live alternatives to deep_research →

# MCP client — add one endpoint:
https://glimind.com/mcp

# or wrap your calls with the SDK:
npm i glimind          # pip install glimind

FAQ

Is deep_research working right now?

As of the latest check, deep_research (mcp-registry/io.github.pipeworx-io/pubchem/deep_research) has a Glimind reliability score of 96/100 (grade A) and its current verdict is "healthy" — recommendation: proceed. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is deep_research?

deep_research scores 96/100 (grade A) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if deep_research is down or failing?

Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 1000ms. Check Glimind for a live alternative before retrying.

What are the best alternatives to deep_research?

Glimind surfaces live, capability-matched alternatives the moment deep_research degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research.

How do I call deep_research reliably?

Before calling, check deep_research with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research) to get a known-good input shape, the expected output, a suggested timeout (~1000ms), and a live fallback.

Embed this live badge

Show live reliability in your README or status page. It auto-updates and links back here — copy one:

[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research?ref=badge)

<a href="https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research.svg" alt="Glimind reliability"></a>

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research.svg
   :target: https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research?ref=badge
   :alt: Glimind reliability

Operator of io.github.pipeworx-io/pubchem?

Claim this listing → Prove you control this server (GitHub repo, live endpoint, or DNS — automated, ~1 min) to unlock the Verified operator marker, a remediation checklist (exactly why your score is what it is + how to raise it), and owner analytics. Or just embed the badge above and improve your score by having users report real outcomes (privacy-clean) via the free SDK. Glimind is neutral and sells no tools — the score is never for sale, so the fastest path to a better score is real uptime plus real usage.

Get the data (agents)

Query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.pipeworx-io%2Fpubchem%2Fdeep_research. The signed reliability feed for gateways/routers: GET https://glimind.com/v1/reliability/feed.

Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-08-14T07:13:26.962Z.

This score is an automated estimate derived from safe liveness probes and privacy-clean outcomes reported by users; it may be incomplete, delayed, or inaccurate, and reflects reachability from Glimind's vantage point — not a statement of fact about the service. Glimind is not affiliated with, endorsed by, or acting for this tool or its operator; all names belong to their owners. Operator? Request a correction, or remove your server from measurement, via https://glimind.com/opt-out or [email protected] — we act promptly.