Developer · Remote MCP server
Trusteed
CTEM for your Trusteed tenant: security summary, findings, compliance gaps, and scans via OAuth.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.trusteed-io/trusteed-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-17
- Updated
- 2026-07-17
- Publisher
- trusteed-io (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/trusteed-io) · how
- Repository
- github.com/trusteed-io/trusteed-mcp-plugin
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.trusteed.io/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Trusteed
Trusteed is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.trusteed.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Trunk Flaky TestsFlaky test detection, root cause analysis, and fix suggestions for development teams. | Remote · HTTPLive check: sign-in required |
| Trust Score APITrust scoring for domains, wallets, APIs. SSL+DNS+WHOIS+headers. Score 0-100. | Remote · SSELive check: ✗ no handshake |
| Trust ToolsWebsite security ratings, token verification, and tamper-evident ledger heads from Obelisk Gate. | Remote · HTTPLive check: ✓ handshake |
| TrustablFind and fix reliability and safety gaps in agent code, across nine agent SDKs. | Local · stdio |
| Trustmodel MCPScore any AI for trust across 10 dimensions; evaluate, monitor & govern LLMs and agents. | Local · stdio |
| TrustNotchTamper-evident audit logs for AI agents: submit, fetch, and verify cryptographic proof bundles. | Local · stdio |
| TrustScanSecurity scanner for MCP servers and skills: Unicode injection, patterns, secrets. | Remote · HTTPLive check: ✓ handshake |
| TrustsourceX402-paid domain verification for AI agents - trustscore, SSL, security headers, robots. | Local · stdio |