MCP Server

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. Unified MCP server for the eleven Kinetic Gain Protocol Suite specs — 63 governance tools.

What you get

One MCP server, all twelve Kinetic Gain Protocol Suite specs + the v0.1.0 implementation tooling + the DefenseTech 6-pack. Drop into Claude Desktop, Cursor, or any MCP-compatible client with a single config entry. The agent gains 75 tools (47 spec + 16 implementation-preview + 8 DefenseTech + 4 AI Claims Decision Card, v0.9.0): AEO Protocol, Prompt Provenance, Agent Cards, AI Evidence Format, MCP Tool Cards, AI Tutor Cards, Student AI Disclosure, Classroom AI AUP, Clinical AI Disclosure, AI Incident Card, AI Procurement Decision Card, AI Claims Decision Card - plus hash

• One Claude Desktop config entry — instead of five
• Cross-spec workflows are atomic — - an agent can agent_card_tool_disclosure to find a Tool Card URI, then call tool_card_inspect on that URI in the same conversation, all through one server
• Shared schemas + utilities — keep the implementation cohesive
• Deprecation path — - if mcp-aeo-server (the AEO-only predecessor) gets retired, the AEO tools live on here with the same names and contracts

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

• aeo_fetch — Fetch the full AEO Protocol declaration at an origin's
• aeo_inspect — Return a structured summary of an AEO declaration: entity
• aeo_get_claim — Extract a single AEO claim by ID
• aeo_well_known_url — Compute the canonical AEO well-known URL for an origin
• prompt_provenance_validate — Validate a Prompt Provenance JSON document against the v0.1
• prompt_provenance_inspect — Structured summary of a Prompt Provenance document: prompt
• prompt_provenance_eval_result — Extract a single evaluation suite's result from a Prompt
• agent_card_well_known_url — Compute the canonical Agent Card well-known URL for a given
• agent_card_inspect — Structured summary of an Agent Card document
• agent_card_tool_disclosure — Return the list of tools an agent declares, with side-effect
• agent_card_validate — Validate an Agent Card JSON document against the v0.1 schema
• ai_evidence_validate — Validate an AI Evidence object against the v0.1 schema

Configuration and credentials

You will need one environment variable: AUDIT_STREAM_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at mcp-kinetic-gain on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — aeo_fetch, aeo_inspect, aeo_get_claim and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mizcausevic-dev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.