Is the Theluckystrike Service Agreement MCP server down?

mcp-registry/io.github.theluckystrike/service-agreement · v0.22.6

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
down
Last checked 2026-11-08 20:51 UTC · handshake 26ms

As of 2026-11-08 20:51 UTC, the Theluckystrike Service Agreement MCP server is down with a Glimind reliability score of 43/100 (grade D). Over the last 30 days it answered 57.5% of Glimind's liveness checks. It had 1085 outages in 90 days, with a median recovery of 36 minutes.

uptime (30d checks)
57.5%
checks observed
3,219
outages (90d)
1085
tools
9

Service agreements for freelancers: scope, deliverables, rate, termination and liability caps.

Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/service-agreement

Agent-readiness: C (79/100)

C (79/100): 1 error(s), 1 warning(s) across 9 tool(s); ~2,279 tokens of tool definitions.
Scores higher than 15% of 16,487 MCP servers Glimind has audited.
Its tool list costs an agent ~2,279 tokens per session — lighter than 55% of servers.
82 → 79 since 2026-10-17
no tool-poisoning patterns
Descriptions74
Safety hints100
Schemas100
Protocol100
Stability36
Token cost100
Reliability20
Client compatibility70

What to fix (4)

Reachable 57.5% of the time over the last 30 days; median recovery 36 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

4 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: agreement_create, agreement_update_status

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 16 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.theluckystrike/service-agreement"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.theluckystrike/service-agreement"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.theluckystrike%2Fservice-agreement.svg)](https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fservice-agreement?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fservice-agreement?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.theluckystrike%2Fservice-agreement.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:31eadfda7af83748…, first seen 2026-11-06, included at leaf 178575 of 192,931. Version history · verify what your client received.

Working alternatives

Tools (9)

Compare: most reliable knowledge servers · most reliable productivity servers · most reliable security servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Theluckystrike Service Agreement MCP server down right now?

As of 2026-11-08 20:51 UTC, the Theluckystrike Service Agreement MCP server is down with a Glimind reliability score of 43/100 (grade D). Over the last 30 days it answered 57.5% of Glimind's liveness checks. It had 1085 outages in 90 days, with a median recovery of 36 minutes.

How many tools does Theluckystrike Service Agreement MCP server provide?

Theluckystrike Service Agreement MCP server advertises 9 tools, including agreement_checklist, agreement_create, agreement_get, agreement_list, agreement_render.

How do I install Theluckystrike Service Agreement MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/service-agreement

Is the Theluckystrike Service Agreement MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Theluckystrike Service Agreement MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve