Is contract_assemble working right now?

io.github.theluckystrike/terms · mcp-registry/io.github.theluckystrike/terms/contract_assemble

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

Recent contract changes

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

• added — license_activate (2026-09-23)
• added — clause_add (2026-09-23)
• added — clause_get (2026-09-23)
• added — clause_update (2026-09-23)
• added — clause_delete (2026-09-23)

Working alternatives

• mcp-clauses io.github.theluckystrike/job-card
• contract_create io.github.theluckystrike/docx-document-generator-proposal-contract-markdown
• contract_gaps io.tooloracle/contractoracle
• llm_clause_check io.tooloracle/ampel

See all live alternatives to contract_assemble →

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is contract_assemble working right now?

As of the latest check, contract_assemble (mcp-registry/io.github.theluckystrike/terms/contract_assemble) 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.

How reliable is contract_assemble?

contract_assemble scores 21/100 (grade F) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if contract_assemble is down or failing?

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: mcp-clauses, contract_create, contract_gaps, llm_clause_check.

What are the best alternatives to contract_assemble?

Working alternatives ranked by capability similarity and live health: mcp-clauses, contract_create, contract_gaps, llm_clause_check. See each one's live status on Glimind.

How do I call contract_assemble reliably?

Before calling, check contract_assemble with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.theluckystrike%2Fterms%2Fcontract_assemble) 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.theluckystrike%2Fterms%2Fcontract_assemble.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.theluckystrike%2Fterms%2Fcontract_assemble?ref=badge)

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

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.theluckystrike%2Fterms%2Fcontract_assemble.svg
   :target: https://glimind.com/tool/mcp-registry%2Fio.github.theluckystrike%2Fterms%2Fcontract_assemble?ref=badge
   :alt: Glimind reliability

Operator of io.github.theluckystrike/terms?

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.theluckystrike%2Fterms%2Fcontract_assemble. 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-20T05:14:02.684Z.

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.