MissionのオープンMCPインターセプションアダプター。アクション実行権限を厳密に制御します。
その役割はただ一つ：ラップされたMCPプロバイダーの前に立ち、提案されたツールコールを分類し、重要な呼び出しを不変のトラストグラデュエーションアクションバインディングで保留します。低リスクの呼び出しは通過を許可されます。「承認」というチャットメッセージは決して権限として扱われません。
ステータス：実験的ベータ版。Apache-2.0。ランタイム依存関係ゼロ。
要件：Node.js 20以降。
npx -y @gomission/mcp@beta demoこのコマンドはダミーのメールプロバイダーを使用し、機械可読なDEMO_RESULTを1つ出力します。以下を証明します：
重要なプロバイダー関数が0回呼び出されたこと；
保留に正確なアクションと入力ハッシュが含まれていること；
レビュー済みの入力を変更するとコミットメントが変わること；
チャットテキストが実行権限を与えないこと。
これはインターセプションを証明するものであり、完全な認可や実稼働での採用を証明するものではありません。ポータブルなグラント/リプレイの証明は@trust-graduation/coreにあります：
npx -y @trust-graduation/core@beta demoRelated MCP server: agentpassport
プリミティブ | 責任 | ポータブルオブジェクト |
Mission Gate | プロバイダー効果の前に判断 | アクション判断 |
Trust Profile | プリンシパルとアクションクラスごとの権限実績を追跡 | 証拠プロファイル |
Mission Key | 期限切れまたは失効まで1つの正確なアクションを認可 | 1回限りのグラント |
MCPアダプターはプロバイダー前の保留を実装します。信頼されたMission Keyを発行せず、保留された呼び出しを再開できません。信頼された承認ホストと実行環境は、対応するキーを検証し、アトミックに消費する必要があります。実験的なA2A継続は以下で公開されています：
https://trustgraduation.org/extensions/a2a/action-authorization/v1
パッケージルートは、外部の承認ホストと実行環境が使用する安定した依存関係ゼロのバインディングブリッジを公開します：
import { providerActionFromMcpBinding } from "@gomission/mcp";
import { createProviderGate } from "@trust-graduation/core";
const gate = createProviderGate({
store: sharedAtomicGrantStore,
authenticateGrant: verifyApprovalIssuer,
provider: existingProviderFunction,
writeReceipt: durableReceiptSink
});
// Re-read the actual provider input at the final seam; never trust a preview.
const action = providerActionFromMcpBinding(
heldReceipt.action_binding,
actualProviderInput
);
const execution = await gate.execute({
binding: heldReceipt.action_binding,
approval: authenticatedMissionKey,
action
});ブリッジはバインディングの整合性を検証し、インターセプトされたID、ターゲット、制約、有効期限、ノンスをコア実行環境の形状にマッピングします。その後、コアは実際のプロバイダー入力を再ハッシュ化し、キーを認証してアトミックに消費し、プロバイダーを呼び出し、結果にリンクされた証拠を書き込みます。改変やリプレイがプロバイダーに到達することはありません。
生成されたアダプターと客観的なプロバイダー呼び出しカウンターについては：
npm install @trust-graduation/core@beta
npx trust-graduation init-adapter
npx trust-graduation conformance ./mission-gate-adapter.mjs --json両方のパッケージがインストールされた状態で、含まれている互換性証明は以下です：
node node_modules/@trust-graduation/core/examples/mcp-provider-roundtrip.mjsMCPプロキシは、チャットが「承認」と言っただけで保留された呼び出しを決して再開しません。このブリッジは、別途認証された承認ホストとプロバイダーにバインドされた実行環境のためのものです。
npx -y @gomission/mcp@beta install-claudeインストーラーは既存のClaude Desktop MCP設定を検査します：
重要なMCPサーバーを検出した場合、--wrapを選択します；
それ以外の場合は、アドバイザリーな正確なバインディングデモである--localを選択します；
ホストされた読み取り専用モードを自動選択することはありません。
インストール後にClaude Desktopを再起動し、以下を確認します：
npx -y @gomission/mcp@beta verifyverifyは最新のMCPをserver/discoverとtools/listでプローブし、古いエンドポイントにはinitialize時代のプロトコルにフォールバックします。機械可読なレポートを出力するには--jsonを、設定のみを検査するには--no-probeを追加します。
モード | 適用される内容 | 行わないこと |
| 選択された子MCPサーバーをインターセプト；子が利用できない場合はフェイルクローズで高/重大または低信頼度の呼び出しをプロバイダー前に保留 | 保留された呼び出しの再開やチャット承認を信頼しない |
| アドバイザリーな正確なアクション保留とローカルレビューレシートを記録 | 他のツールとそのプロバイダーの間には位置しない |
| ホストされた読み取り専用のMissionコンテキストを公開 | 他のMCPサーバーをインターセプトしない |
必要に応じて明示的に選択します：
npx -y @gomission/mcp@beta install-claude --wrap
npx -y @gomission/mcp@beta install-claude --local
npx -y @gomission/mcp@beta install-claude --remote便利なフラグ：
--workspace <path> — 既存のワークスペースにローカルレシートを保存。
--dry-run — 設定変更を書き込まずに表示。
--force — Claude Desktopが検出されなくても設定を作成。
--remote-url <url> — ホストされたエンドポイントを上書き。
`MISSION_DONT_WRAP=
Fetch a Mission receipt by id.
| Name | Required | Description | Default |
|---|---|---|---|
| receipt_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states a basic fetch operation without disclosing any behavioral traits such as read-only nature, error handling, or performance implications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no waste, but it could benefit from a bit more detail without losing brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (one parameter, no output schema, no annotations), the description is minimally adequate but lacks information on return format, error conditions, or how receipt_id is obtained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter (receipt_id) with no description, and the tool description only mentions 'by id' without explaining format, examples, or how to obtain the id.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Fetch a Mission receipt by id' uses a specific verb and resource, clearly distinguishing it from sibling tools like log_action or mission_status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, and no exclusions or context are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Log a safe internal action with Mission. Returns a receipt id. Use for non-external actions that still benefit from a permanent receipt.
| Name | Required | Description | Default |
|---|---|---|---|
| summary | Yes | ||
| evidence | No | ||
| action_class | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It only states 'safe internal action' and output, but omits details about authentication, side effects, or error conditions. The term 'safe' is vague and insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Very concise: two sentences, no filler. Key information is front-loaded. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 3 parameters, no output schema, and no annotations, the description is too sparse. It provides no parameter guidance, no return value details beyond receipt id, and no error handling. The complexity is not matched by the description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% (no parameter descriptions in schema). The description does not mention any parameters, their purpose, or constraints. It fails to compensate for the lack of schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states action 'log a safe internal action' and output 'returns a receipt id'. It gives a specific verb and resource, but does not explicitly differentiate from siblings like 'get_receipt' or 'request_approval', though the internal purpose is implied.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides guidance on when to use: 'Use for non-external actions that still benefit from a permanent receipt.' This gives a clear context, but lacks explicit exclusions or alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Check the explicitly selected local Mission workspace for chat availability. Requires MISSION_WORKSPACE and an explicit loopback MISSION_LOCAL_URL or MISSION_LOCAL_PORT. Chat is currently unavailable until a workspace-scoped authentication handoff is supported; this tool does not forward queries or prepare actions.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | A natural-language question or instruction for Mission. Examples: 'what should I approve today?', 'who am I dropping?', 'prepare a reply to Sandro', 'show me my weekly proof', 'what did I just learn?' |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and delivers unusually candid behavior: it discloses required environment variables and, critically, that chat is currently unavailable pending a workspace-scoped authentication handoff. It also states the tool has no side effects (no query forwarding, no action preparation). It falls short of a 5 only because it does not describe what the call actually returns in its unavailable state.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with the core purpose front-loaded and no obvious padding. It is dense but efficient; minor jargon ('loopback', 'workspace-scoped authentication handoff') slightly slows comprehension.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is a non-functional availability probe with no output schema, the description is largely complete: it covers required env configuration, the blocked state, and the absence of side effects. It would be fully complete if it pointed the agent at mission_status or otherwise told it what to do instead.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single required 'query' parameter is fully documented with examples in the schema, so the baseline is 3. The line 'does not forward queries' does tell the agent the parameter is effectively inert, which is useful, but otherwise the description adds no syntax or format detail beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action and scope: checking the explicitly selected local Mission workspace for chat availability, and explicitly narrows it by saying it 'does not forward queries or prepare actions.' This distinguishes it from request_approval and log_action. It loses a point because the name 'mission_ask' implies a working Q&A tool, creating tension the description only partially resolves, and it never contrasts itself with mission_status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Preconditions are stated clearly (MISSION_WORKSPACE plus an explicit loopback MISSION_LOCAL_URL or MISSION_LOCAL_PORT), which is real context. However, there is no explicit when-to-use vs when-not-to-use guidance relative to siblings like mission_status, and the reader must infer that this tool is effectively a no-op probe.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Return Mission gate status, version, and the current Trust Graduation action classes. Call this first in any session to introduce the permission layer.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It describes the return values but does not explicitly state that it has no side effects or that it is read-only. However, the nature of returning status information implies safety, so it is adequate but not exceptional.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: the first states what it returns, the second gives usage guidance. No unnecessary words, highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately lists the three return categories (gate status, version, action classes). It could provide more detail on the format, but it is sufficient for a simple tool with no parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so baseline is 4. The description does not need to add parameter meaning; it correctly omits parameter information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'Mission gate status, version, and the current Trust Graduation action classes'. It distinguishes itself from siblings by instructing to call it first in any session to introduce the permission layer, making its unique role obvious.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells when to use: 'Call this first in any session'. This implies it is a prerequisite for other tools, though it does not explicitly state when not to use it or provide alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Legacy-named advisory hold. Call before a consequential action to produce an exact action binding and local review receipt. This tool does not grant authority or resume execution; the executor must validate a matching single-use Mission Key.
| Name | Required | Description | Default |
|---|---|---|---|
| summary | Yes | One-line plain-English summary of the action. | |
| evidence | No | Optional evidence supporting the action. | |
| action_class | Yes | One of: send_email, post_public, send_dm, schedule_meeting, spend_money, publish_artifact, modify_external_record, change_trust_policy |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and discharges much of it: it discloses that the call is advisory-only, non-authoritative, does not resume execution, and that the executor must validate a matching single-use Mission Key. It omits auth requirements and what the receipt actually contains, which are notable gaps for a zero-annotation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with no filler, and the most consequential caveat (legacy name, advisory-only) is front-loaded before the invocation condition. Every sentence changes how an agent would behave.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter, no-annotation, no-output-schema tool, the description covers the critical semantics: advisory scope, non-authority, and the Mission Key handoff. It does not describe the receipt's contents or the full Mission Key flow, which leaves a small but real gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so action_class, summary, and evidence are already documented with their allowed values. The description adds no syntax or format guidance beyond the schema, so the baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a concrete deliverable (an exact action binding and a local review receipt) for a consequential-action workflow, and flags that the tool name 'request_approval' is legacy and misleading. It does not, however, position itself against siblings like mission_ask or get_receipt, so the agent gets the function but not the sibling routing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear positive timing ('Call before a consequential action') and an explicit negative boundary ('does not grant authority or resume execution'). It stops short of naming which sibling to use instead when the agent actually needs authority or status, so the alternative-routing half of the guidance is missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0get_receiptlog_actionmission_askmission_statusrequest_approvalScored across 5 tools
Each tool targets a distinct action: request_approval for consequential holds, log_action for internal receipts, get_receipt for retrieval, mission_status for gate status, and mission_ask for chat availability. The overlap between request_approval and log_action (both producing receipts) is clarified by descriptions, but the legacy advisory nature of request_approval could still cause confusion.
Most tools use a verb_noun pattern (request_approval, get_receipt, log_action), but mission_ask and mission_status use a noun-prefix convention, and request_approval is explicitly labeled legacy-named. The mix is readable but not fully consistent.
Five tools is a reasonable size for a focused permission-layer server. However, mission_ask is currently non-functional and request_approval is legacy, so one tool does not fully earn its place, making the count slightly heavy rather than ideal.
The core lifecycle of status, approval request, action logging, and receipt retrieval is covered, but there are notable gaps: no way to list or search receipts, no tool to validate the single-use Mission Key that request_approval requires the executor to check, and mission_ask only checks unavailable chat functionality.
Decision-assurance for AI agents: an auditable action boundary + receipt before it acts.
Trust gate for AI agents: multi-model adversarial consensus, signed and verifiable verdicts.
Independent effect verification and signed receipts for consequential AI agent actions.
Pre-execution policy gate for consequential agent actions with durable trust receipts.
