Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Trent
Overview
Description from the maker (original English)
Security reviews, threat models over a repo or website, and remediation tracking, in your editor.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.trent.ai/mcpRun this in your terminal
claude mcp add --transport http trent https://mcp.trent.ai/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"trent": {
"url": "https://mcp.trent.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"trent": {
"type": "http",
"url": "https://mcp.trent.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.trent.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain trent.ai (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32464 servers in this category
- Published to the registry more recently than 53% of the other 32464 servers in this category
- Basic checks equal to or better than 100% of the other 32464 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Trent safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 35 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, yontu
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
yontu
by senrecep
Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Trent agent plugin
Trent, an AI security engineer. Review code, plans and configs for security problems, run threat models over a repo or website, and track remediation without leaving the editor.
Installing
Add the marketplace by repository name. trnt-ai/trent-agent-plugin is the only public marketplace that carries Trent, and adding it by name is what ties the install to us. (A plugin manifest carries no signature, so the name is what you are trusting; never add a marketplace from a URL to a file.)
Claude Code:
/plugin marketplace add trnt-ai/trent-agent-plugin/plugin install trent@trent
Codex CLI:
codex plugin marketplace add trnt-ai/trent-agent-plugincodex plugin add trent@trent
Check what you installed with claude plugin details trent. It prints Source: trent@trent and the manifest's identity fields.
Signing in
The plugin declares a remote MCP server and no credentials. Authentication happens in the browser the first time a tool runs; there is no API key to paste and none is shipped here.
What the plugin sends, and where
The plugin holds no code of its own: four skills and the addresses of Trent's two servers. Everything it sends goes through your coding agent, as Trent tool calls, to the server for your account's region: https://mcp.trent.ai/mcp (US) or https://mcp.eu.trent.ai/mcp (EU).
- Repository scans. Trent reads a repository through the Trent GitHub App you install on it. The plugin does not upload your repository; it sends the repository's owner and name.
- Reviews.
security_advisorsends the content your agent passes it for that review: code, a diff, a plan or a config./trent:trent-loopsends the diff of each fix it makes. - Documents. A design document or findings file you choose to attach is uploaded straight to Trent's storage on Amazon S3, through a signed URL that
prepare_file_uploadreturns and that expires. - What you type. Feedback, edits to findings and project settings go as tool arguments.
The plugin also sends its version in the x-trent-plugin-version header. It reads no credentials from your machine.
Trent handles this data under its privacy policy, https://trent.ai/privacy-policy/. Security documentation is in the Trent Trust Center, https://trust.trent.ai/.
Using it
Ask your coding agent in plain words; the plugin's skills tell it which Trent tool to use:
- Review one piece of work (a diff, a plan, a config):
trent-security-advisor. - Scan a repository or website and read what Trent found:
trent-threats, ortrent-repofor the repository you are in. - Fix what Trent found: run
/trent:trent-loop, or/trent:trent-loop 3to fix at most three. It works on a new branch, checks each fix with your own tests and with Trent's security advisor, and opens one pull request for you to review. After you merge it, run it again: Trent scans the merged code, reports which fixes it now counts as done, and carries on with the rest.
Verifying where a release came from
Each release is one commit, and its message carries the revision it was built from:
Published from source revision <sha>Run git log -1 in a clone of this repository to read it. The is an identifier, not a link; there is nowhere to follow it to. What it gives you is an exact name for the build you are running: quote it to support and they can say which release you have. If a copy of this plugin does not carry a message in that form, it was not published by us.
Each release's pull request also runs a check, provenance, that the commit has that shape: one commit on main, that subject, plain files, and a changed version when the content changed. It reads the commit and holds no credential.
The plugin manifest names https://github.com/trnt-ai/trent-agent-plugin, this repository, as its repository, and trent.ai as its homepage. A plugin claiming to be Trent from anywhere else is not ours.
Pinning a release
Every release is tagged plugin-v , on the commit that release published. git tag -l in a clone lists them. A tag here never moves: the repository's rules refuse it, so a pin keeps resolving to the same files.
On a Team or Enterprise plan an admin can register this marketplace for everyone in managed-settings.json, pinned to a release. ref is the tag and sha is the commit it names; with both set the sha is the pin and the ref says which release it came from:
{"extraKnownMarketplaces": { "trent": { "source": { "source": "github", "repo": "trnt-ai/trent-agent-plugin", "ref": "plugin-v0.1.0", "sha": " " } } }, "enabledPlugins": { "trent@trent": true } }
Read the sha off the tag rather than copying one from anywhere else:
git ls-remote https://github.com/trnt-ai/trent-agent-plugin refs/tags/plugin-v0.1.0 'refs/tags/plugin-v0.1.0^{}'One line back means the tag names that commit: pin it. Two lines back means the tag is annotated: the line ending ^{} names the commit, and that is the one to pin.
Upgrading is then a deliberate edit of those two fields, not something that happens when someone reinstalls.
Getting help
Questions, bugs and feature requests reach us at https://trent.ai or through your usual support channel; that is where they get answered.
This repository is published from Trent's build on each release; every file in it is generated, so it is not the place to file or fix anything.
Licence
Copyright Trent AI. See LICENSE for the terms, and https://trent.ai for anything the terms do not answer.