Is the Plith MCP server down?

mcp-registry/ai.plith/plith · v1.0.0

As of 2026-10-20 10:53 UTC, the Plith MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 4 minutes.

AI agent infrastructure: dedup, cost prediction, validation, governance, failure intelligence.

claude mcp add --transport http plith-mcp-server https://plith.ai/api/mcp

{
  "mcpServers": {
    "plith-mcp-server": {
      "type": "http",
      "url": "https://plith.ai/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (88/100)

What to fix (5)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.plith%2Fplith/fixes

{
  "name": "dedupq_complete",
  "description": "After executing a task, store the result so future identical or similar tasks return a cache hit via dedupq_check. Costs 2 credits.",
  "inputSchema": {
    "type": "object",
    "required": [
      "content",
      "result"
    ],
    "properties": {
      "result": {
        "description": "The task result to cache. Can be any JSON value.",
        "type": "string"
      },
      "content": {
        "type": "string",
        "description": "Original task content. Used to compute hash and embedding for future matching."
      },
      "task_id": {
        "type": "string",
        "description": "Optional task ID. Used as the database row ID if provided."
      },
      "hash_only": {
        "type": "boolean",
        "description": "If true, skip embedding generation. Default: false."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Store completed task result",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

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/ai.plith/plith"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.plith/plith"}) over MCP.

Passed

• Every tool and parameter is described.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• 99.90% uptime over 30 days.

Largest tool definitions

• rigor_plan ~1,822 tokens
• rigor_execute ~1,797 tokens
• guardrail_create_policy ~640 tokens
• rigor_workflows ~557 tokens
• qualitygate_validate ~498 tokens

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. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.plith%2Fplith.svg)](https://glimind.com/server/mcp-registry%2Fai.plith%2Fplith?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fai.plith%2Fplith?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.plith%2Fplith.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.plith%2Fplith.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.plith%2Fplith?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a7f96b96ede5b2b7…, first seen 2026-10-17, included at leaf 14236 of 32,481. Version history · verify what your client received.

Tools (15)

• burnrate_budget
• burnrate_estimate
• burnrate_optimize
• burnrate_track
• dedupq_check
• dedupq_complete
• guardrail_check
• guardrail_create_policy
• pitfalldb_query
• pitfalldb_report
• qualitygate_validate
• rigor_execute
• rigor_plan
• rigor_status
• rigor_workflows

Compare: most reliable ml servers · most reliable knowledge servers · most reliable security servers · most reliable quality servers · most reliable productivity servers

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

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

FAQ

Is the Plith MCP server down right now?

As of 2026-10-20 10:53 UTC, the Plith MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Plith MCP server provide?

Plith MCP server advertises 15 tools, including burnrate_budget, burnrate_estimate, burnrate_optimize, burnrate_track, dedupq_check.

How do I install Plith MCP server?

Point your MCP client at this streamable-http endpoint: https://plith.ai/api/mcp

Is the Plith MCP server safe to connect to an AI agent?

Glimind scanned all 15 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 Plith 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.