Other · Remote MCP server
Mission - Trust Graduation Gate
Trust Graduation gate: Claude can do real work once Mission decides what it is allowed to do.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.gomission/mcp- Version
- 0.1.4
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-12
- Updated
- 2026-06-12
- Publisher
- gomission (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/gomission) · how
- Website
- claude.gomission.io
- Repository
- github.com/gomission/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://claude.gomission.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 410)
- Handshake
- HTTP 410
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @gomission/mcp | 0.1.4 | stdio |
How to connect Mission - Trust Graduation Gate
Mission - Trust Graduation Gate is a remote MCP server: there is nothing to install. Its endpoint is https://claude.gomission.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.
It can also run locally from a Node.js package published to the npm registry: @gomission/mcp version 0.1.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @gomission/mcp@0.1.4.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@gomission/mcp@0.1.4"
]
}
}
}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 other servers
| Server | Runs |
|---|---|
| MirrorGive Claude an honest self-model - behavioral tendencies built from evidence, not session memory. Mi. | Remote · HTTPLive check: ✗ no handshake |
| MirrorEdge AI: WavesLet your assistant see your recording's spectrogram, box the noise, and heal only that. | Local · stdio |
| Misfit Machine StoreUCP-compatible machine catalog for paid Misfit agent APIs and MCP services. | Remote · HTTPLive check: ✓ handshake |
| MISSINGFallback capability resolver for AI agents with replay-verified discovery and x402 paid execution. | Remote · HTTPLive check: ✗ no handshake |
| Mission QuotesQuote a proxy-presence mission: what a real person on the ground in city X costs. | Remote · HTTPLive check: ✓ handshake |
| Mitre Atlas MCPMITRE ATLAS - Adversarial Threat Landscape for AI Systems. Tactics + techniques for attacking AI... | Local · stdio |
| Mitre Attack MCP ServerMCP server providing 50+ tools for MITRE ATT&CK techniques, groups, and mitigations. | Local · stdio |
| Mixer4AIMixer4AI - verified AI agents, trusted introductions, for agents acting for real businesses. | Remote · HTTPLive check: ✓ handshake |