Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
☰ MenuEnglish Settings
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Trent

by trnt-aiversion 0.3.0i★ 9iRuns in the cloud
Registry nameai.trent/trent

Install

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.

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: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

Before you install

You need

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:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3Connect4
https://mcp.trent.ai/mcp

Run this in your terminal

claude mcp add --transport http trent https://mcp.trent.ai/mcp

Open in Cursor

Or 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.

Open in VS Code

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:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3Connect4
https://mcp.trent.ai/mcp

Menu 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.

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

Guide 85 checks before you install an MCPAbout 2 minutes each: check its page on our site and the permission request in your AI app before you say yes.4 min read

What it can do

The server asks you to sign in before it lists its tools.

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 11, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain trent.ai (the registry checks domain ownership)

  • ✓ Pass

    Still maintained

    Code last changed 8 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • ✓ Pass

    Endpoint responds

    Responded in 706 ms (HTTP 401)

  • ✓ Pass

    Sign-in with OAuth

    Declares OAuth sign-in, so your AI app can take you to log in

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

User reviews

No reviews yet

Compared with others in Cybersecurityi

  • More stars than 91% of the other 1025 servers in this category
  • Published to the registry more recently than 52% of the other 1025 servers in this category
  • Basic checks equal to or better than 100% of the other 1025 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 5 of 5 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 8 days ago, and the latest version (0.3.0) reached the registry 39 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: Robin: AI-Powered Dark Web OSINT, HOL Guard, UniFi Network MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Robin: AI-Powered Dark Web OSINT

Dark web OSINT over Tor: search onion engines, scrape pages, report with your own model.

by apurvsinghgautamGrowing★ 7.9KUpdated 39 days ago

Runs on your computer
Install

HOL Guard

Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.

by hashgraph-onlineWidely used↓ 7.1K/wk★ 1.1KUpdated 6 days ago

Runs on your computer
Install

UniFi Network MCP

Manage UniFi Network devices, clients, firewall, VLANs, VPNs, and more via MCP.

by sirkirbyWidely used↓ 11.3K/wk★ 1KUpdated 8 months ago

Runs on your computer
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-plugin

codex 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_advisor sends the content your agent passes it for that review: code, a diff, a plan or a config. /trent:trent-loop sends 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_upload returns 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, or trent-repo for the repository you are in.
  • Fix what Trent found: run /trent:trent-loop, or /trent:trent-loop 3 to 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.