grn_add working right now?io.github.theluckystrike/onboarding-goods-receipt-inspection-runs · mcp-registry/io.github.theluckystrike/onboarding-goods-receipt-inspection-runs/grn_add
Recovery track record: 578 outages in 90 days, median time-to-recovery 41 min.
Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.
added — po_add (2026-09-23)added — grn_add (2026-09-23)added — grn_line_add (2026-09-23)added — grn_list (2026-09-23)added — grn_get (2026-09-23)See all live alternatives to grn_add →
Agents that check Glimind first make fewer failed calls, waste fewer tokens, and auto-route around outages like this one. Add it in ~10 seconds — free, no signup:
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
Or wrap your calls with the SDK: npm i glimind · pip install glimind. See how it works
As of the latest check, grn_add (mcp-registry/io.github.theluckystrike/onboarding-goods-receipt-inspection-runs/grn_add) has a Glimind reliability score of 21/100 (grade F) and its current verdict is "down" — recommendation: avoid. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.
grn_add scores 21/100 (grade F) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
Tool is down — don't retry now; switch to a live alternative or back off for minutes. Use a timeout around 1000ms. Live alternatives that do a similar job: hub_receive_purchase_order, hub_record_received_goods, hub_get_purchase_order, reconcile_purchase_documents.
Working alternatives ranked by capability similarity and live health: hub_receive_purchase_order, hub_record_received_goods, hub_get_purchase_order, reconcile_purchase_documents. See each one's live status on Glimind.
Before calling, check grn_add with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.theluckystrike%2Fonboarding-goods-receipt-inspection-runs%2Fgrn_add) to get a known-good input shape, the expected output, a suggested timeout (~1000ms), and a live fallback.
Show live reliability in your README or status page. It auto-updates and links back here — copy one:
[](https://glimind.com/tool/mcp-registry%2Fio.github.theluckystrike%2Fonboarding-goods-receipt-inspection-runs%2Fgrn_add?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fio.github.theluckystrike%2Fonboarding-goods-receipt-inspection-runs%2Fgrn_add?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.github.theluckystrike%2Fonboarding-goods-receipt-inspection-runs%2Fgrn_add.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.theluckystrike%2Fonboarding-goods-receipt-inspection-runs%2Fgrn_add.svg :target: https://glimind.com/tool/mcp-registry%2Fio.github.theluckystrike%2Fonboarding-goods-receipt-inspection-runs%2Fgrn_add?ref=badge :alt: Glimind reliability
io.github.theluckystrike/onboarding-goods-receipt-inspection-runs?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.
Query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.theluckystrike%2Fonboarding-goods-receipt-inspection-runs%2Fgrn_add. 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-10-18T18:48:32.094Z.
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.