Trusteed

io.github.trusteed-ioPublished by GitHub account trusteed-iov1.0.0Updated Oct 24, 2026

CTEM for your Trusteed tenant: security summary, findings, compliance gaps, and scans via OAuth.

The publisher's own server: Mcp Gateway

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Trusteed's remote MCP server lets an assistant read a tenant's security posture, findings, assets and compliance gaps, and start or cancel scans.

What you can do
Read security posture summaries and narrative risk explanations for the tenant, plus scan and connection statuses. Search the asset inventory. List and open findings, and check compliance status and control gaps. Start or cancel on-demand scans. Get a hosted link to connect a cloud account, with credentials entered outside chat.
When to use it
Useful for security teams already on Trusteed who want an assistant to triage findings, summarize posture and compliance gaps, or kick off scans without leaving the chat. Not useful without an existing Trusteed tenant.
Requirements
Remote Streamable HTTP endpoint at mcp.trusteed.io, reached over the network along with app.trusteed.io for OAuth. An active Trusteed account is required; the server does not create users. OAuth 2.0 sign-in through the Trusteed portal; Claude.ai connectors need the static public OAuth client ID from the README, with the client secret left empty.
Before you install
OAuth grants the assistant access to your tenant's security and asset data. Write tools can start or cancel scans, which may consume scan capacity or affect monitoring. Cloud credentials must only be entered on hosted Trusteed pages, never through chat. Tenant security data is processed by Trusteed under its privacy policy.

Installation

In SourceWeft

  1. Open Trusteed in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.trusteed-io%2Ftrusteed-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "trusteed": {
      "type": "http",
      "url": "https://mcp.trusteed.io/mcp"
    }
  }
}

README

Trusteed Claude Marketplace

Official Trusteed plugins for Claude Code and Claude Cowork.

This repository is a Claude plugin marketplace. It packages the Trusteed remote MCP server so teams can install it with a single plugin command.

ItemValue
Marketplace nametrusteed
Plugintrusteed-mcp
MCP endpointhttps://mcp.trusteed.io/mcp
TransportStreamable HTTP (type: http)
AuthOAuth 2.0 (Trusteed portal login)

OAuth Client ID (required for Claude.ai connectors)

Trusteed uses a static public PKCE client (no secret). If Claude shows “Automatic client registration isn’t supported… add an OAuth Client ID”, paste:

text
f5f30ba8-da81-40ef-8e75-aaf98f75f324

Claude.ai / Desktop custom connector

  1. Settings → Connectors → Add custom connector
  2. MCP URL: https://mcp.trusteed.io/mcp
  3. Advanced → OAuth Client ID: value above (leave Client Secret empty)
  4. Connect and sign in with an existing Trusteed portal account

Install (Claude Code plugin)

bash
# Add this marketplace/plugin marketplace add trusteed-io/trusteed-mcp-plugin
# Install the Trusteed MCP plugin/plugin install trusteed-mcp@trusteed

Then authenticate:

bash
/mcp

Select trusteed, complete the browser login with your existing Trusteed portal account, and return to Claude.

Local development test

bash
claude --plugin-dir ./plugins/trusteed-mcp

Prerequisites

  1. An active Trusteed account (MCP does not create users).
  2. Claude Code (or Cowork) with plugin support.
  3. Network access to:
    • https://mcp.trusteed.io (MCP resource server)
    • https://app.trusteed.io (OAuth authorization server)

What you get

After install + OAuth, Claude can call Trusteed MCP tools for your tenant:

Read

  • get_security_summary — high-level posture
  • search_assets — inventory search
  • list_findings / get_finding — vulnerabilities
  • get_compliance_status / list_control_gaps — compliance
  • explain_risk — narrative risk summary
  • get_scan_status / get_connection_status — status

Write / action

  • start_scan / cancel_scan — on-demand scans
  • connect_cloud_account — hosted URL to connect cloud credentials (never through chat)

Bundled skills (examples):

  • /trusteed-mcp:security-overview
  • /trusteed-mcp:findings-triage
  • /trusteed-mcp:connect-cloud

Repository layout

text
.claude-plugin/marketplace.json     # marketplace catalogplugins/trusteed-mcp/  .claude-plugin/plugin.json        # plugin manifest  .mcp.json                         # remote MCP + OAuth  README.md                         # detailed plugin docs  skills/                           # Claude skills

Website / how-to copy

Ready-to-publish page content (EN + TR) for Claude & ChatGPT setup:

Privacy

Trusteed processes security and asset data for your tenant according to our privacy policy:

Cloud credentials are entered only on hosted Trusteed pages; they are never sent through the MCP chat channel.

Support

License

Apache-2.0 — see LICENSE.

Source: README.md at commit fbd314e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Trusteed integrations