Plith Rigor
ai.plith/rigorplith.aistreamable-httpv1.0.0Scanned
Structured multi-step workflows that produce production-quality deliverables. Plan any task free.
4 tools: 2 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 1
- No findings
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
rigor_executeExecute a structured workflow end-to-end.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "rigor_execute" says "execute": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.delivery.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- title: Execute a Rigor workflow
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
rigor_planBefore executing a complex task, get a structured workflow plan with per-step cost estimates.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Plan a Rigor workflow
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
rigor_statusCheck the status of a running or completed Rigor workflow.No findings
Why it is in this group
- The name "rigor_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check workflow status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
rigor_workflowsList and search Rigor workflows for your organization, with filtering and pagination.Reads private dataNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe input names a folder (input.folder_id), and the tool reads: it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: List Rigor workflows
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__rigor__rigor_execute"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http rigor https://plith.ai/api/mcp/rigorclaude mcp add --transport http rigor https://plith.ai/api/mcp/rigorRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__rigor__rigor_status",
"mcp__rigor__rigor_workflows"
],
"ask": [
"mcp__rigor__rigor_plan",
"mcp__rigor__rigor_execute"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rigor. Review it before you use it.
Capability tags behind 3 rules
- mcp__rigor__rigor_plan untrusted-input
- mcp__rigor__rigor_execute untrusted-input, outbound
- mcp__rigor__rigor_workflows private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/ai.plith/rigor/verify?hash=8971acf331132c3d5543d1325de0d43a41bee972fab42f6e4e8c5d91c4107bc4" | jq -e '.changed == false'Pinned hash 8971acf33113, from Oct 24, 2026, 23:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/ai.plith/rigor/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/ai.plith/rigor)Source: MCP Registry · repository. Synced Oct 24, 2026, 23:17 UTC.