ai.plith/plith
REMOTE · PLITH.AI · SCANNED SEP 21
AI agent infrastructure: dedup, cost prediction, validation, governance, failure intelligence.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2969 tokens (~141/item across 21 items; 15 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the ai.plith/plith MCP server?
ai.plith/plith is a hosted endpoint at https://plith.ai/api/mcp, 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.
remote · plith.ai
claude mcp add --transport http ai-plith-plith 'https://plith.ai/api/mcp'
{
"mcpServers": {
"ai-plith-plith": {
"url": "https://plith.ai/api/mcp"
}
}
} {
"servers": {
"ai-plith-plith": {
"type": "http",
"url": "https://plith.ai/api/mcp"
}
}
} [mcp_servers.ai-plith-plith] url = "https://plith.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-plith-plith": {
"type": "remote",
"url": "https://plith.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-plith-plith --url 'https://plith.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-plith-plith:
url: "https://plith.ai/api/mcp" {
"McpServers": {
"ai-plith-plith": {
"Transport": "http",
"Url": "https://plith.ai/api/mcp"
}
}
} assistant mcp add ai-plith-plith -t streamable-http -u 'https://plith.ai/api/mcp'
{
"mcpServers": {
"ai-plith-plith": {
"type": "http",
"url": "https://plith.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Sept 26 0
- “rigor_execute” reworded the description of “task_type” cosmetic
- “rigor_plan” reworded the description of “task_type” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 30 Aug 26 0
- Tool “rigor_workflows” rewrote its description, which is the text the model reads security
- “rigor_workflows” added an optional parameter “created_after” cosmetic
- “rigor_workflows” added an optional parameter “created_before” cosmetic
- “rigor_workflows” added an optional parameter “folder_id” cosmetic
- “rigor_workflows” added an optional parameter “q” cosmetic
- 28 Aug 26 +8
- Judged manipulation: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- 27 Aug 26 −8
- Judged manipulation: pass → unverified ▼ security
- Tool “rigor_execute” rewrote its description, which is the text the model reads security
- Tool “rigor_plan” rewrote its description, which is the text the model reads security
- Schema quality: excellent → unverified ▼ functional
- “rigor_execute” reworded the description of “task_type” cosmetic
- “rigor_plan” reworded the description of “task_type” cosmetic
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://plith.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=plith.ai | CN=YR2,O=Let's Encrypt,C=US | 14 Aug 2026 | 12 Nov 2026 | RSA 2048 | SHA256-RSA | 5f8c76b4ee6972a11ce55394955901e92df |
| SANs: plith.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of plith.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| plith.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://umami.peaklight.news; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://umami.peaklight.news; frame-ancestors 'none'; form-action 'self'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://plith.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://plith.ai/api/mcp | HTTPS enforced | 308 | https://plith.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
burnrate_budget ~69
Get today's tracked LLM spend, per-model breakdown, projection, and budget alerts. Free — no credits charged.
| Name | Type | Req | Description |
|---|---|---|---|
| daily_limit | number | – | Optional. Daily budget in USD (e.g., 10.0 for a $10/day cap). Enables budget alerts and remaining-balance calculation. |
| Name | Type | Req | Description |
|---|---|---|---|
| alerts | array | – | – |
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| date | string | – | – |
| fallback_behavior | string | – | – |
| projection | object | – | – |
| request_id | string | – | – |
| spend | object | – | – |
No examples provided.
burnrate_estimate ~74
Before executing a multi-step agent plan, estimate the total LLM cost. Returns per-step breakdown and optimization suggestions. If the estimate exceeds your budget, pipe the same plan into burnrate_optimize. Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | array | yes | Array of plan steps with provider, model, and token estimates. |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| estimate | object | – | – |
| fallback_behavior | string | – | – |
| optimization_suggestions | array | – | – |
| request_id | string | – | – |
No examples provided.
burnrate_optimize ~128
Get a cheaper equivalent plan by substituting models with lower-cost alternatives. Call after burnrate_estimate if the estimated cost exceeds your budget. Returns the optimized plan with substituted models, new per-step costs, total savings, and whether the target_budget is met. Optionally set target_budget to constrain the optimization. Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | array | yes | Array of plan steps. Same schema as burnrate_estimate: each step needs step, provider, model, estimated_input_tokens, estimated_output_tokens. |
| target_budget | number | – | Optional. Target total cost in USD. |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| fallback_behavior | string | – | – |
| optimized | object | – | – |
| original | object | – | – |
| request_id | string | – | – |
| steps | array | – | – |
| suggestions | array | – | – |
No examples provided.
burnrate_track ~268
Log the actual cost of an LLM call after execution. Call this after every LLM request to build calibration data that improves burnrate_estimate accuracy over time. Free — no credits charged. Returns the recorded cost entry with computed margin versus the prior estimate when one exists for this model and token range.
| Name | Type | Req | Description |
|---|---|---|---|
| cache_read_tokens | number | – | Optional. Cache-read tokens. |
| input_tokens | number | yes | Actual prompt tokens used. Must be >= 0. |
| model | string | yes | Model identifier as returned by the provider. Examples: claude-sonnet-4-6, gpt-4o, gemini-2.0-flash, mistral-large-latest. Unknown models are accepted but cost may show as $0. |
| output_tokens | number | yes | Actual completion tokens used. Must be >= 0. |
| provider | string | yes | LLM provider identifier. Supported: anthropic, openai, google, mistral, cohere, deepseek, together, fireworks, groq. Must match the provider of the model used. |
| task_id | string | – | Optional task ID for cross-referencing spend with DedupQ deduplication results. Use the same task_id passed to dedupq_check to link cost tracking with deduplication. |
| Name | Type | Req | Description |
|---|---|---|---|
| actual_cost_usd | number | – | – |
| actual_cost_usd_formatted | string | – | – |
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| fallback_behavior | string | – | – |
| input_tokens | number | – | – |
| model | string | – | – |
| output_tokens | number | – | – |
| pricing_found | boolean | – | – |
| provider | string | – | – |
| record_id | string | – | – |
| request_id | string | – | – |
| tracked | boolean | – | – |
No examples provided.
dedupq_check ~169
Before executing any LLM task, check if an identical or semantically similar task has already been completed. Returns cached result on hit, saving one LLM call. On a miss, execute your task and call dedupq_complete to cache the result for future hits. Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The task content to check for duplicates. This is hashed and embedded for matching. |
| hash_only | boolean | – | If true, skip vector similarity search and use exact hash matching only. Default: false. |
| similarity_threshold | number | – | Cosine similarity threshold for semantic matching, 0.0 to 1.0. Default: 0.80. |
| task_id | string | – | Optional caller task ID for tracing and cross-referencing with BurnRate. |
| Name | Type | Req | Description |
|---|---|---|---|
| cache_age_seconds | number | – | – |
| cache_hit | string | – | – |
| content_hash | string | – | – |
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| fallback_behavior | string | – | – |
| match | object | – | – |
| request_id | string | – | – |
| status | string | – | hit | miss | in_progress |
No examples provided.
dedupq_complete ~113
After executing a task, store the result so future identical or similar tasks return a cache hit via dedupq_check. Costs 2 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Original task content. Used to compute hash and embedding for future matching. |
| hash_only | boolean | – | If true, skip embedding generation. Default: false. |
| result | – | yes | The task result to cache. Can be any JSON value. |
| task_id | string | – | Optional task ID. Used as the database row ID if provided. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_hash | string | – | – |
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| fallback_behavior | string | – | – |
| has_embedding | boolean | – | – |
| request_id | string | – | – |
| stored | boolean | – | – |
| task_id | string | – | – |
No examples provided.
guardrail_check ~121
Evaluate a proposed agent action against your governance policies. Returns allow or deny with the matched policy reason. Requires at least one active policy created via guardrail_create_policy. Deterministic rule evaluation — no LLM. Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent identifier. |
| proposed_action | object | yes | Action to evaluate. Must contain a 'type' field. Example: {"type": "http_request", "url": "https://external.example.com"} or {"type": "file_write", "path": "/etc/config"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | – | – |
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| decision | string | – | – |
| fallback_behavior | string | – | – |
| policy_id | string | – | – |
| reason | string | – | – |
| request_id | string | – | – |
No examples provided.
guardrail_create_policy ~342
Create a persistent governance policy that guardrail_check evaluates on every subsequent call. Define rules using and/or/not operators over action types, resource patterns, and budget thresholds. Call this before using guardrail_check — checks require at least one active policy. Policies persist until explicitly deleted. Duplicate policy names return an error. Returns the created policy with its ID and active status.
| Name | Type | Req | Description |
|---|---|---|---|
| action_types | array | – | Optional. Restrict this policy to only evaluate when proposed_action.type matches one of these values. Examples: ['file_write', 'api_call', 'db_delete']. Omit to apply the policy to all action types… |
| description | string | – | Optional human-readable summary of what this policy enforces. Returned in guardrail_check responses and guardrail_list_policies output for auditability. |
| name | string | yes | Unique policy name per org. Examples: 'no-delete-in-prod', 'budget-cap-50', 'pii-block'. |
| priority | number | – | Optional. Evaluation order. Default: 0. |
| rules | array | yes | Array of rule objects evaluated against the proposed_action in guardrail_check. Leaf operators: eq, starts_with, contains, gt, lt (compare field to value). Compound operators: and, or, not (nest sub-… |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| fallback_behavior | string | – | – |
| policy | object | – | – |
| request_id | string | – | – |
No examples provided.
pitfalldb_query ~101
Check for known failure patterns before executing a task type. Returns pitfalls with severity, fix suggestions, and confidence scores. After your agent runs, submit failures via pitfalldb_report so others benefit. Costs 2 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Optional filters. |
| task_description | string | – | Optional. Natural-language task description for semantic search. |
| task_type | string | yes | Task category: code_generation, web_search, data_analysis, etc. |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| fallback_behavior | string | – | – |
| pitfalls | array | – | – |
| request_id | string | – | – |
| total_matching | number | – | – |
No examples provided.
pitfalldb_report ~69
Report an agent failure. PII-scrubbed before storage. Linked to existing pitfalls if similar. Free — no credits charged.
| Name | Type | Req | Description |
|---|---|---|---|
| failure | object | yes | Failure details. |
| task_description | string | yes | Description of the failed task. |
| task_type | string | yes | Task category. |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| fallback_behavior | string | – | – |
| linked_pitfall_id | string | – | – |
| message | string | – | – |
| report_id | string | – | – |
| request_id | string | – | – |
| verified | boolean | – | – |
No examples provided.
qualitygate_validate ~230
After your agent generates output, validate it against your rules before shipping. Runs deterministic checks (regex, JSON schema, syntax) plus optional LLM-powered tone and factual analysis. Returns a structured verdict (pass, warn, or fail) with a 0-100 score and per-check issue details. Use qualitygate_trends to spot recurring failure patterns over time. Variable cost: 1 credit per deterministic check, 8 credits per LLM check.
| Name | Type | Req | Description |
|---|---|---|---|
| check_types | array | – | Checks to run. Auto-inferred if omitted. |
| directives | array | – | Directive objects. Types: must_include, must_not_include, must_match, must_not_match, must_contain, must_not_contain, min_length, max_length. |
| language | string | – | Code language for syntax check: json, python, javascript, typescript. |
| output | string | yes | The agent output text to validate. |
| override | boolean | – | Force pass. Requires override_reason. |
| override_reason | string | – | Required when override is true. |
| schema | object | – | JSON Schema to validate output against. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks_run | array | – | – |
| credits_remaining | number | – | – |
| credits_used | number | – | – |
| fallback_behavior | string | – | – |
| issues | array | – | – |
| request_id | string | – | – |
| summary | object | – | – |
| verdict | string | – | – |
No examples provided.
rigor_execute ~389
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Additional context for the workflow. |
| delivery | object | – | Delivery method. Default: polling (MCP clients typically can't handle SSE). |
| preferences | object | – | Optional workflow preferences. |
| task_description | string | yes | Natural language description of the task. Be specific — include what you want produced, constraints, and context. Example: 'Design a caching layer for our API gateway with Redis integration.' |
| 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| available_modes | array | – | – |
| delivery_mode | string | – | – |
| estimated_credits | number | – | – |
| execution | string | – | Present with value 'direct' when direct execution ran. Absent for standard multi-call execution. |
| execution_fallback | boolean | – | True when you explicitly requested direct execution and it could not be honoured — the workflow ran as standard multi-call instead. Never set for an auto-selected attempt, since you did not ask. |
| ok | boolean | – | – |
| poll_url | string | – | – |
| status | string | – | – |
| task_type | string | – | – |
| value_class | string | – | – |
| workflow_id | string | – | – |
No examples provided.
rigor_plan ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| preferences | object | – | Optional workflow preferences. |
| task_description | string | yes | Natural language description of the task. Be specific — include what you want produced, constraints, and context. Example: 'Design a caching layer for our API gateway with Redis integration.' |
| 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| generated_title | string | – | – |
| ok | boolean | – | – |
| plan | object | – | – |
No examples provided.
rigor_status ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | The workflow ID returned by rigor_execute (format: wr_xxx). |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | – | – |
| workflow | object | – | – |
No examples provided.
rigor_workflows ~364
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| concurrent_summary | object | – | – |
| credits_remaining | number | – | – |
| ok | boolean | – | – |
| pagination | object | – | – |
| workflows | array | – | – |
No examples provided.
What is the ai.plith/plith MCP server?
ai.plith/plith is an MCP server listed in the public MCP registry as ai.plith/plith. AI agent infrastructure: dedup, cost prediction, validation, governance, failure intelligence. This page covers its hosted endpoint (https://plith.ai/api/mcp).
Is the ai.plith/plith MCP server safe to use?
ai.plith/plith scores 86 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 ai.plith/plith MCP server expose?
ai.plith/plith exposes 15 tools: dedupq_check, dedupq_complete, burnrate_estimate, burnrate_track, burnrate_optimize, and 10 more. Their descriptions and schemas cost roughly 2,789 tokens of context every time the server is loaded.
Does the ai.plith/plith MCP server require authentication?
No. We connected to ai.plith/plith without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.plith/plith MCP server still maintained?
ai.plith/plith is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.