Is pdf working right now?

com.agishub/agent-memory · mcp-registry/com.agishub/agent-memory/pdf

Recovery track record: 1318 outages in 90 days, median time-to-recovery 3 min.

Working alternatives

• pdf com.agishub/crypto-prices
• render_pdf com.skillforge99/render-api
• page_pdf com.thenextgennexus/playwright-mcp-server
• snapforge_pdf org.snapforge/snapforge

See all live alternatives to pdf →

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

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

FAQ

Is pdf working right now?

As of the latest check, pdf (mcp-registry/com.agishub/agent-memory/pdf) has a Glimind reliability score of 40/100 (grade D) and its current verdict is "degraded" — recommendation: proceed with caution. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is pdf?

pdf scores 40/100 (grade D) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if pdf is down or failing?

Degraded — retry at most once with backoff and a longer timeout; line up an alternative. Use a timeout around 35952ms. Live alternatives that do a similar job: pdf, render_pdf, page_pdf, snapforge_pdf.

What are the best alternatives to pdf?

Working alternatives ranked by capability similarity and live health: pdf, render_pdf, page_pdf, snapforge_pdf. See each one's live status on Glimind.

How do I call pdf reliably?

Before calling, check pdf with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.agishub%2Fagent-memory%2Fpdf) to get a known-good input shape, the expected output, a suggested timeout (~35952ms), 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%2Fcom.agishub%2Fagent-memory%2Fpdf.svg)](https://glimind.com/tool/mcp-registry%2Fcom.agishub%2Fagent-memory%2Fpdf?ref=badge)

<a href="https://glimind.com/tool/mcp-registry%2Fcom.agishub%2Fagent-memory%2Fpdf?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fcom.agishub%2Fagent-memory%2Fpdf.svg" alt="Glimind reliability"></a>

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fcom.agishub%2Fagent-memory%2Fpdf.svg
   :target: https://glimind.com/tool/mcp-registry%2Fcom.agishub%2Fagent-memory%2Fpdf?ref=badge
   :alt: Glimind reliability

Operator of com.agishub/agent-memory?

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%2Fcom.agishub%2Fagent-memory%2Fpdf. 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-09-02T05:49:25.262Z.

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.