Skip to content

MCP servers › dev.tryplinth › plinth

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

dev.tryplinth/plinth

App hosting your agent runs: git, deploys, staging/production, Postgres. Owner approves risky steps. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: cloud-and-devops · AI-classifiedPricing: paid-subscription · AI-classifiedversion 1.0.0streamable HTTP72 tools

Summary

dev.tryplinth/plinth is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 72 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
72
Described as changing data
39 of 72 toolsAI-classified
Mainly works on
files and code on the machine it runs on; a database; cloud accounts, servers or DevOps toolsAI-classified
Topic
cloud-and-devopsAI-classified
Pricing
paid-subscriptionAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 12 tools whose name or declaration suggests they change data (account.create, project.create, project.delete, code.write, env.secrets.set and 7 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 39 tools are described as changing something (account.create, project.create, project.delete, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-15 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-15 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-15).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
72tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; a database; cloud accounts, servers or DevOps tools.

39 of 72 tools are described as changing something (creating, editing, deleting, sending or running).

  • account.createcreates or changes datadescribed as changing data

    “Create a Plinth account for your human owner (or join theirs if their email already has one).”

    3 inputs, 1 required
    • emailstringrequired“Owner email”
    • agentstring“Your name, e.g.”
    • projectstring“Optional first project name”
  • account.statuson 1 other serverreads or searches

    “Finish signup: checks whether the owner approved, and returns your token (once) when they have.”

    2 inputs, 2 required
    • signup_idstringrequired“From account.create”
    • pollstringrequired“From account.create”
  • whoamion 178 other serversreads or searches

    “Show the account this token belongs to, its policy and projects.”

    Takes no inputs.

  • project.createon 1 other servercreates or changes datadescribed as changing data

    “Create a project: a git repo plus production and staging environments, each with its own Postgres database.”

    1 input, 1 required
    • namestringrequired“Lowercase name, 3-40 chars, e.g.”
  • project.liston 1 other serverreads or searches

    “List projects with their environments, live releases and URLs.”

    Takes no inputs.

  • project.getreads or searches

    “Show one project: git remote, environments, live release per environment, URLs.”

    1 input, 1 required
    • projectstringrequired“Project name”
  • project.deleteon 1 other serverdeletesdescribed as changing data

    “Delete a project, its repo, environments and databases.”

    1 input, 1 required
    • projectstringrequired“Project name”
  • code.writecreates or changes datadescribed as changing data

    “Commit files to the project without git: for agents that cannot run git or the CLI (e.g.”

    5 inputs, 1 required
    • projectstringrequired“Project name”
    • branchstring“Default main”
    • messagestring“Commit message”
    • filesarray
    • deletearray“Paths to remove”
  • code.listreads or searches

    “List files in the project repo (path and size) on a branch or commit.”

    3 inputs, 1 required
    • projectstringrequired“Project name”
    • refstring“Branch or commit, default main”
    • prefixstring“Only files under this folder”
  • code.readreads or searches

    “Read one file from the project repo.”

    3 inputs, 2 required
    • projectstringrequired“Project name”
    • pathstringrequired
    • refstring“Branch or commit, default main”
  • git.remotereads or searches

    “Get the authenticated git remote URL for pushing.”

    1 input, 1 required
    • projectstringrequired“Project name”
  • git.logreads or searches

    “Recent commits on a branch.”

    3 inputs, 1 required
    • projectstringrequired“Project name”
    • branchstring“Default main”
    • limitnumber
Show 60 more tools
  • git.branchesreads or searches

    “Branches and their head commits.”

    1 input, 1 required
    • projectstringrequired“Project name”
  • git.revertcreates or changes datadescribed as changing data

    “Revert a commit on a branch server-side.”

    3 inputs, 2 required
    • projectstringrequired“Project name”
    • commitstringrequired
    • branchstring“Default main”
  • env.listreads or searches

    “Environments for a project with live release and URL.”

    1 input, 1 required
    • projectstringrequired“Project name”
  • env.secrets.setcreates or changes datadescribed as changing data

    “Set an environment variable for an environment.”

    4 inputs, 4 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • keystringrequired
    • valuestringrequired
  • env.secrets.listreads or searches

    “List environment variable names (values are never returned).”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
  • env.secrets.importcreates or changes datadescribed as changing data

    “Set many environment variables at once from .env text (KEY=value lines; # comments, quotes and "export" are fine).”

    4 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • dotenvstringrequired“Contents of a .env file”
    • replaceboolean“Remove variables not in the file (default false)”
  • env.secrets.unsetdeletesdescribed as changing data

    “Remove an environment variable.”

    3 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • keystringrequired
  • deployon 17 other serversdescribed as changing data

    “Rebuild and deploy the head of the branch an environment tracks (staging tracks main).”

    3 inputs, 1 required
    • projectstringrequired“Project name”
    • envstring“Environment: production, staging, or a preview name”
    • commitstring“Optional commit sha; defaults to branch head”
  • deploy.statusreads or searches

    “Releases for an environment, newest first, with status and build log of the latest.”

    4 inputs, 1 required
    • projectstringrequired“Project name”
    • envstring“Environment: production, staging, or a preview name”
    • limitnumber
    • log_fromnumber
  • deploy.canceldeletesdescribed as changing data

    “Stop a build that is still running (the latest one in the environment, or a given release id).”

    3 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • releasestring
  • promoteon 3 other serversdescribed as changing data

    “Promote the release running on one environment to another (default staging to production).”

    3 inputs, 1 required
    • projectstringrequired“Project name”
    • fromstring“Default staging”
    • tostring“Default production”
  • rollbackon 11 other serversdescribed as changing data

    “Point an environment back at its previous release (or a given release id).”

    3 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • releasestring
  • db.queryruns code or commandsdescribed as changing data

    “Run SQL against an environment database.”

    4 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • sqlstringrequired
    • paramsarray
  • db.migrationsreads or searches

    “Applied and pending migrations (files in migrations/*.sql, applied in name order).”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
  • db.migratedescribed as changing data

    “Apply pending migrations from the live release now (deploys do this automatically).”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
  • db.snapshotcreates or changes datadescribed as changing data

    “Take a snapshot (pg_dump) of an environment database.”

    3 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • labelstring
  • db.snapshotsreads or searches

    “List snapshots for an environment.”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
  • db.restorecreates or changes datadescribed as changing data

    “Restore an environment database from a snapshot.”

    3 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • snapshotstringrequired
  • db.connectionreads or searchesdescribed as changing data

    “Get the DATABASE_URL for an environment (the same one the app receives).”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
  • cron.addcreates or changes datadescribed as changing data

    “Schedule a job: Plinth POSTs to path on the environment at each tick (5-field cron, UTC), with the header x-plinth-cron-secret.”

    6 inputs, 5 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • namestringrequired
    • schedulestringrequired“e.g.”
    • pathstringrequired“e.g.”
    • enabledboolean
  • cron.listreads or searches

    “Cron jobs on an environment with last run and next run.”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
  • cron.pausecreates or changes datadescribed as changing data

    “Pause a cron job (it stays defined but does not run).”

    3 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • namestringrequired
  • cron.resumecreates or changes datadescribed as changing data

    “Resume a paused cron job.”

    3 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • namestringrequired
  • cron.removedeletesdescribed as changing data

    “Delete a cron job.”

    3 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • namestringrequired
  • cron.runruns code or commandsdescribed as changing data

    “Run a cron job now and return its result.”

    3 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • namestringrequired
  • cron.runsreads or searches

    “Recent runs of a cron job.”

    3 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • namestringrequired
  • domains.connectcreates or changes datadescribed as changing data

    “Map a domain you own to an environment.”

    3 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • hoststringrequired“e.g.”
  • domains.liston 1 other serverreads or searches

    “Domains mapped to a project.”

    1 input, 1 required
    • projectstringrequired“Project name”
  • domains.verifyreads or searches

    “Check the TXT record of a connected domain; once it matches, the domain is served.”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • hoststringrequired
  • domains.removedeletesdescribed as changing data

    “Unmap a domain.”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • hoststringrequired
  • billing.statusreads or searches

    “Whether a card is on file, this month's spend, the spend cap and recent charges.”

    Takes no inputs.

  • project.upgradedescribed as changing data

    “Move a project to Pro ($19/month per project): own domains and more room.”

    1 input, 1 required
    • projectstringrequired“Project name”
  • project.downgradedescribed as changing data

    “Move a project back to the free plan.”

    1 input, 1 required
    • projectstringrequired“Project name”
  • billing.carddescribed as changing data

    “Ask the owner to add or replace the payment card.”

    Takes no inputs.

  • domains.searchreads or searches

    “Check if domains can be bought here, with price.”

    1 input, 1 required
    • querystringrequired“e.g.”
  • domains.buydescribed as changing data

    “Buy a domain and connect it to an environment: registers it, points DNS at Plinth, issues HTTPS.”

    4 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • domainstringrequired“e.g.”
    • yearsnumber“1-10, default 1”
  • domains.ordersreads or searches

    “Domains bought through Plinth on this account, with price, status and expiry.”

    Takes no inputs.

  • logs.queryreads or searches

    “Logs for an environment: app stdout/stderr, build, cron and system lines.”

    6 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • sincestring“30s, 15m, 2h, 7d (default 15m)”
    • grepstring
    • streamstring“stdout, stderr, build, cron, system”
    • limitnumber
  • metrics.getreads or searches

    “Request count, error rate and latency percentiles for an environment.”

    3 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • sincestring
  • analytics.getreads or searches

    “Visitors and page views per day, top pages, where visitors come from, and phone vs desktop.”

    3 inputs, 1 required
    • projectstringrequired“Project name”
    • envstring“Environment: production, staging, or a preview name”
    • daysnumber“Default 30 (Pro) or 1 (Free)”
  • seo.setup

    “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: key…”

    2 inputs, 1 required
    • projectstringrequired“Project name”
    • envstring“Default production”
  • env.statusreads or searches

    “Debug an environment: is it running, restarts, out-of-memory kills, memory/CPU use, live release, and the last errors from its logs.”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
  • env.restartdescribed as changing data

    “Restart an environment on its current release (fresh sandbox, same code and data).”

    2 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
  • env.execruns code or commandsdescribed as changing data

    “Production needs owner approval.”

    4 inputs, 3 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • commandstringrequired
    • timeout_secondsnumber
  • http.probereads or searches

    “Send one HTTP request to the environment from inside Plinth and return status, headers, timing and the first 8 KB of the body.”

    6 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • pathstring“e.g.”
    • methodstring
    • bodystring
    • headersobject
  • requests.queryreads or searches

    “Recent HTTP requests to an environment: method, path, status, time taken.”

    6 inputs, 2 required
    • projectstringrequired“Project name”
    • envstringrequired“Environment: production, staging, or a preview name”
    • sincestring
    • min_statusnumber
    • pathstring
    • limitnumber
  • approvals.listreads or searches

    “Approvals requested by this account, newest first.”

    1 input
    • statusstring“pending, approved, denied, cancelled, superseded (default all)”
  • approval.canceldescribed as changing data

    “Withdraw a pending approval request you made (for example one that is no longer needed).”

    1 input, 1 required
    • idstringrequired
  • approval.statusreads or searches

    “Check an approval.”

    1 input, 1 required
    • idstringrequired
  • support.sendsends messagesdescribed as changing data

    “Send the Plinth team a bug report, feature request or question.”

    5 inputs, 3 required
    • kindstringrequired“bug, feature, question or other”
    • titlestringrequired“One line”
    • bodystringrequired“Details: steps, expected vs actual, commands, error text”
    • projectstring“Optional project it is about”
    • envstring“Optional environment”
  • support.listreads or searches

    “Your support tickets with their status and the team's reply.”

    Takes no inputs.

  • webhooks.addcreates or changes datadescribed as changing data

    “Send Plinth events to a URL (your bot, Slack, Discord, Telegram, Zapier...).”

    3 inputs, 1 required
    • urlstringrequired“https URL”
    • eventsarray
    • authorizationstring“Optional Authorization header value, e.g.”
  • webhooks.listreads or searches

    “Your webhooks with their last delivery status.”

    Takes no inputs.

  • webhooks.removedeletesdescribed as changing data

    “Delete a webhook.”

    1 input, 1 required
    • idstringrequired
  • webhooks.testdescribed as changing data

    “Send a test event to all your webhooks; check webhooks.list a few seconds later for the result.”

    Takes no inputs.

  • console.signincontrols a browser or desktopdescribed as changing data

    “Get the owner into the web console.”

    Takes no inputs.

  • token.rotatedescribed as changing data

    “Replace your own agent token with a new one; the old one stops working immediately.”

    Takes no inputs.

  • agents.liston 1 other serverreads or searches

    “Agents that have a key to this account, when each was last used, and which one you are.”

    Takes no inputs.

  • agents.revokedeletesdescribed as changing data

    “Owner only.”

    1 input, 1 required
    • idstringrequired
  • policy.setcreates or changes datadescribed as changing data

    “Owner only.”

    1 input, 1 required
    • auto_approvearrayrequired

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 72 tools
Says what it returns
64% of 72 tools
States limits, defaults or errors
14% of 71 tools
Says when to use it
3% of 71 tools
Items covered per tool
1.8 of 4 on average

Counted from the listing

Parameters with a description
74% of 161
Tools with a description
100% of 72
Typical description length
135 characters

The tool set

Counted from the listing

Tools
72
Size of the list
about 6,924 tokens for an agent to load (characters ÷ 4)
Naming
68 of 72 names use mixed or other styles

AI reading: easy to mix up

  • project.upgrade and project.downgrade
  • domains.verify and domains.remove

The AI items cover 72 of 72 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found these, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://tryplinth.dev/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "plinth": {
      "url": "https://tryplinth.dev/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "plinth": {
      "type": "http",
      "url": "https://tryplinth.dev/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"plinth","type":"http","url":"https://tryplinth.dev/mcp"}'
Claude Code
claude mcp add --transport http plinth https://tryplinth.dev/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://tryplinth.dev/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint tryplinth.dev/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about dev.tryplinth/plinth

Answered from the data above

Is dev.tryplinth/plinth safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 39 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is dev.tryplinth/plinth free to use?

Its website (tryplinth.dev/) describes a paid-subscription pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does dev.tryplinth/plinth need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has dev.tryplinth/plinth been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can dev.tryplinth/plinth do?

It lists 72 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages, run code or commands and control a browser or desktop. We did not call any tool, so this describes the text, not the behaviour.

Can dev.tryplinth/plinth change or delete data?

39 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “cloud-and-devops” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,346 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 72 tools, 0 resources, 0 prompts.
  4. 8,147 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
paid-subscription
read from tryplinth.dev/ · 2026-10-23

“project.upgrade (Pro, $19/month per project: own domains, 1 GB / 1 CPU, 30-day backups, 90-day analytics, a preview per branch, uptime emails) and domains.buy . Charged to the owner's card after approval.”

Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “dev.tryplinth/plinth: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/dev.tryplinth/plinth

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/dev.tryplinth/plinth)](https://protocolprobe.com/mcp/servers/dev.tryplinth/plinth)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology