# Plith Rigor (remote · plith.ai)

Structured multi-step workflows that produce production-quality deliverables. Plan any task free.

- Trust score: 72/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `plith.ai`: 72/100 (this document), [markdown](https://verifymcp.io/servers/ai-plith-rigor/api-mcp-rigor.md), [page](https://verifymcp.io/servers/ai-plith-rigor/api-mcp-rigor)

## Channel facts

- Endpoint: `https://plith.ai/api/mcp/rigor`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1358 tokens (~226/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 11 days we've observed: 0 tool removals, 4 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Plith Rigor MCP server?

Plith Rigor is a hosted endpoint at https://plith.ai/api/mcp/rigor, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-plith-rigor 'https://plith.ai/api/mcp/rigor'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-plith-rigor": {
      "url": "https://plith.ai/api/mcp/rigor"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-plith-rigor": {
      "type": "http",
      "url": "https://plith.ai/api/mcp/rigor"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-plith-rigor]
url = "https://plith.ai/api/mcp/rigor"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-plith-rigor": {
      "type": "remote",
      "url": "https://plith.ai/api/mcp/rigor",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-plith-rigor --url 'https://plith.ai/api/mcp/rigor' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-plith-rigor:
    url: "https://plith.ai/api/mcp/rigor"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-plith-rigor": {
      "Transport": "http",
      "Url": "https://plith.ai/api/mcp/rigor"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-plith-rigor -t streamable-http -u 'https://plith.ai/api/mcp/rigor'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, −3)

- [security regression] Stability: 0.33 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [functional regression] Tool “rigor_execute” dropped its output schema
- [functional regression] Tool “rigor_plan” dropped its output schema
- [functional regression] Tool “rigor_status” dropped its output schema
- [functional regression] Tool “rigor_workflows” dropped its output schema
- [functional] MCP protocol version: 2024-11-05 → 2025-06-18

### 2026-11-03 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 70)

First indexed and scored.

## MCP tools (4)

### `rigor_plan` (~379 tokens)

Before executing a complex task, get a structured workflow plan with per-step cost estimates. Classifies your task, selects the optimal framework sequence, and returns the full plan without executing anything. The response's allowed_modes tells you whether this plan is eligible for direct execution. Free — no credits charged.

Input parameters:

- `context_fields` (array): Optional, with prior_workflow_id: the fields to carry over. Pass ["full_step_results"] for every step output in full.
- `preferences` (object): Optional workflow preferences.
- `prior_workflow_id` (string): Optional: the workflow_id (wr_…) of a finished workflow in your workspace to build on. Its results are passed to this run as context. It is charged as a new run at the normal quote.
- `task_description` (string, required): Natural language description of the task, at most 4,000 characters. Be specific — include what you want produced, constraints, and context. Example: 'Design a caching layer for our API gateway with R…
- `task_type` (string): Optional hint to bypass automatic classification. Passing it also removes the slowest classification tiers from the critical path, so send it whenever you know the shape. Multi-step deliverable types…

### `rigor_execute` (~482 tokens)

Execute a structured workflow end-to-end. Call rigor_plan first (free) to preview the step sequence and cost estimate before committing credits. Classifies the task, selects the optimal tool sequence, and executes each step with the right LLM model. Returns a complete deliverable — solution designs, competitive analyses, governance documents, and more. Supports SSE streaming for real-time progress, webhook callback, or polling. For atomic work — classification, scoring, ranking, entity extraction, query parsing — set preferences.execution to 'direct' and declare preferences.output_contract to get validated JSON records from a single call, routed to the cheapest model that holds the schema.

Input parameters:

- `context` (object): Additional context for the workflow.
- `context_fields` (array): Optional, with prior_workflow_id: the fields to carry over. Pass ["full_step_results"] for every step output in full.
- `delivery` (object): Delivery method. Default: polling (MCP clients typically can't handle SSE).
- `preferences` (object): Optional workflow preferences.
- `prior_workflow_id` (string): Optional: the workflow_id (wr_…) of a finished workflow in your workspace to build on. Its results are passed to this run as context. It is charged as a new run at the normal quote.
- `task_description` (string, required): Natural language description of the task, at most 4,000 characters. Be specific — include what you want produced, constraints, and context. Example: 'Design a caching layer for our API gateway with R…
- `task_type` (string): Optional hint to bypass automatic classification. Passing it also removes the slowest classification tiers from the critical path, so send it whenever you know the shape. Multi-step deliverable types…

### `rigor_status` (~66 tokens)

Check the status of a running or completed Rigor workflow. Returns progress, step results, and the full deliverable when complete. Use after rigor_execute with polling delivery to retrieve results.

Input parameters:

- `workflow_id` (string, required): The workflow ID returned by rigor_execute (format: wr_xxx).

### `rigor_workflows` (~364 tokens)

List and search Rigor workflows for your organization, with filtering and pagination. Returns status, progress, capacity usage, and available actions per workflow. Use to monitor workflow state, understand concurrent limit usage, identify stuck or completed workflows, and — via q — find prior work on a subject before commissioning it again. Pair a q hit with rigor_status to read that workflow's deliverable.

Input parameters:

- `counts_toward_limit` (string): Filter to workflows counting toward the concurrent limit
- `created_after` (string): ISO timestamp — only workflows created after this time
- `created_before` (string): ISO timestamp — only workflows created before this time
- `cursor` (string): Pagination cursor (created_at timestamp from previous page)
- `folder_id` (string): Filter by folder ID. Pass "unassigned" for workflows in no folder
- `limit` (number): Page size (default 20, max 100)
- `q` (string): Search the workflow title and task description. Every whitespace-separated term must appear in one or the other, as a case-insensitive substring — so "vector search postgres" matches a task described…
- `status` (string): Filter by status (comma-separated). Valid values: executing, step_executing, completed, failed, halted, pending_approval, cancelled. E.g. "halted,failed,pending_approval"
- `task_type` (string): Filter by classified task type

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-plith-rigor/api-mcp-rigor#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70

## Common questions

### What is the Plith Rigor MCP server?

Plith Rigor is an MCP server listed in the public MCP registry as ai.plith/rigor. Structured multi-step workflows that produce production-quality deliverables. Plan any task free. This page covers its hosted endpoint (https://plith.ai/api/mcp/rigor).

### Is the Plith Rigor MCP server safe to use?

Plith Rigor scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Plith Rigor MCP server expose?

Plith Rigor exposes 4 tools: rigor_plan, rigor_execute, rigor_status, rigor_workflows. Their descriptions and schemas cost roughly 1,291 tokens of context every time the server is loaded.

### Does the Plith Rigor MCP server require authentication?

No. We connected to Plith Rigor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Plith Rigor MCP server still maintained?

Plith Rigor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://plith.ai/api/mcp/rigor
- Repository: https://github.com/NewsSpectator/plith
- Website: https://plith.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-plith-rigor/api-mcp-rigor.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-plith-rigor/api-mcp-rigor.json
- HTML version of this page: https://verifymcp.io/servers/ai-plith-rigor/api-mcp-rigor