Plinth
REMOTE · TRYPLINTH.DEV
App hosting your agent runs: git, deploys, staging/production, Postgres. Owner approves risky steps.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Cloud Infrastructure
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 72 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4593 tokens (~63/item across 72 items; 72 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "project.delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 73 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 63
First indexed and scored.
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 17 Oct 2026 · Probed https://tryplinth.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tryplinth.dev | CN=YE1,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 550df37adb5f8a0ee8dd7bd95bde3fb022f |
| SANs: tryplinth.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tryplinth.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| tryplinth.dev. | 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=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tryplinth.dev/mcp | Verified | 200 | |
| http (plaintext) | http://tryplinth.dev/mcp | HTTPS enforced | 308 | https://tryplinth.dev/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 →
http.probe ~108
Send one HTTP request to the environment from inside Plinth and return status, headers, timing and the first 8 KB of the body. Use it to reproduce a failing route.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| env | string | yes | Environment: production, staging, or a preview name |
| headers | object | – | – |
| method | string | – | – |
| path | string | – | e.g. /api/orders?id=3 |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
logs.query ~114
Logs for an environment: app stdout/stderr, build, cron and system lines. Filter by text and stream.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | yes | Environment: production, staging, or a preview name |
| grep | string | – | – |
| limit | number | – | – |
| project | string | yes | Project name |
| since | string | – | 30s, 15m, 2h, 7d (default 15m) |
| stream | string | – | stdout, stderr, build, cron, system |
No output schema declared.
No examples provided.
metrics.get ~54
Request count, error rate and latency percentiles for an environment.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | yes | Environment: production, staging, or a preview name |
| project | string | yes | Project name |
| since | string | – | – |
No output schema declared.
No examples provided.
policy.set ~49
Owner only. Choose which approval types run without asking. Keys: project.create, project.delete, promote.production, migration.destructive, db.restore.production, billing.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_approve | array | yes | – |
No output schema declared.
No examples provided.
project.create ~79
Create a project: a git repo plus production and staging environments, each with its own Postgres database. May return pending_approval: the owner is emailed a link to approve; tell them it is waiting, then poll approval.status.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Lowercase name, 3-40 chars, e.g. acme-crm |
No output schema declared.
No examples provided.
project.delete ~58
Delete a project, its repo, environments and databases. Irreversible. May return pending_approval: the owner is emailed a link to approve; tell them it is waiting, then poll approval.status.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
project.downgrade ~46
Move a project back to the free plan. Its custom domains stop being served. The subscription shrinks with a prorated credit.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
project.get ~33
Show one project: git remote, environments, live release per environment, URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
project.list ~19
List projects with their environments, live releases and URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project.upgrade ~75
Move a project to Pro ($19/month per project): own domains and more room. Charges the owner's card now (prorated) after they approve. May return pending_approval: the owner is emailed a link to approve; tell them it is waiting, then poll approval.status.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
promote ~80
Promote the release running on one environment to another (default staging to production). Applies pending migrations first. May return pending_approval: the owner is emailed a link to approve; tell them it is waiting, then poll approval.status.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Default staging |
| project | string | yes | Project name |
| to | string | – | Default production |
No output schema declared.
No examples provided.
requests.query ~92
Recent HTTP requests to an environment: method, path, status, time taken. Filter to failures with min_status 500, or by path.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | yes | Environment: production, staging, or a preview name |
| limit | number | – | – |
| min_status | number | – | – |
| path | string | – | – |
| project | string | yes | Project name |
| since | string | – | – |
No output schema declared.
No examples provided.
rollback ~62
Point an environment back at its previous release (or a given release id). Does not roll back the database.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | yes | Environment: production, staging, or a preview name |
| project | string | yes | Project name |
| release | string | – | – |
No output schema declared.
No examples provided.
seo.setup ~100
Check how search engines see an environment (title, description, robots.txt, sitemap, noindex) and get the steps to connect OpenSEO (openseo.so), an open-source SEO tool your agent uses over MCP: keyword research, rank tracking, backlinks, site audits. The owner signs up on OpenSEO; Plinth does not share any data with it.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | – | Default production |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
support.list ~19
Your support tickets with their status and the team's reply.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
support.send ~109
Send the Plinth team a bug report, feature request or question. Include what you tried and what happened. Recent errors for the project are attached automatically. Replies show up in support.list.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Details: steps, expected vs actual, commands, error text |
| env | string | – | Optional environment |
| kind | string | yes | bug, feature, question or other |
| project | string | – | Optional project it is about |
| title | string | yes | One line |
No output schema declared.
No examples provided.
token.rotate ~43
Replace your own agent token with a new one; the old one stops working immediately. Save the new token in ~/.plinth/config.json (the CLI does this for you).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
webhooks.add ~145
Send Plinth events to a URL (your bot, Slack, Discord, Telegram, Zapier...). Events: deploy.succeeded, deploy.failed, approval.requested, approval.decided, app.down, app.up, support.created, support.replied, charge.succeeded, signup.approved. Leave events empty for all. Payloads are JSON with a "text" summary and an x-plinth-signature HMAC header; Slack/Discord webhook URLs and Telegram sendMessage URLs work as-is.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | – | Optional Authorization header value, e.g. "Bearer abc". Stored encrypted. |
| events | array | – | – |
| url | string | yes | https URL |
No output schema declared.
No examples provided.
webhooks.list ~18
Your webhooks with their last delivery status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
webhooks.remove ~20
Delete a webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
webhooks.test ~31
Send a test event to all your webhooks; check webhooks.list a few seconds later for the result.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whoami ~21
Show the account this token belongs to, its policy and projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Plinth MCP server?
Plinth is a hosted endpoint at https://tryplinth.dev/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 · tryplinth.dev
claude mcp add --transport http dev-tryplinth-plinth 'https://tryplinth.dev/mcp'
What is the Plinth MCP server?
Plinth is an MCP server listed in the public MCP registry as dev.tryplinth/plinth. App hosting your agent runs: git, deploys, staging/production, Postgres. Owner approves risky steps. This page covers its hosted endpoint (https://tryplinth.dev/mcp).
Is the Plinth MCP server safe to use?
Plinth scores 64 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 Plinth MCP server expose?
Plinth exposes 72 tools: account.create, account.status, whoami, project.create, project.list, and 67 more. Their descriptions and schemas cost roughly 4,541 tokens of context every time the server is loaded.
Does the Plinth MCP server require authentication?
No. We connected to Plinth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Plinth MCP server still maintained?
Plinth is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.