75 governance tools.
One MCP config entry.
The unified Model Context Protocol server exposes twelve Kinetic Gain Protocol Suite specs and the DefenseTech 8-tool pack to MCP clients. 75 tools = 47 spec tools + 16 implementation-preview tools + 8 DefenseTech tools + 4 AI Claims Decision Card tools. It runs locally over stdio. URL fetch tools can contact user-supplied public origins; optional audit tools need a configured service and token. The published package does not intercept downstream requests or enforce buyer authorization.
npm install -g mcp-kinetic-gain@0.10.0
npx -y mcp-kinetic-gain@0.10.0
Registry status
Version 0.10.0 was checked against npm and the official MCP Registry. Community directories are separate listings and are not release evidence here.
Scroll sideways to see every registry column.
| Registry | Status | Version | Record |
|---|---|---|---|
| npm | ● LIVE | 0.10.0 | npm package and provenance |
| Official MCP Registry | ● LIVE | 0.10.0 | io.github.mizcausevic-dev/mcp-kinetic-gain |
The twelve Suite specs, as MCP tools
Each Kinetic Gain Protocol Suite specification exposes a tight tool surface — typically fetch + inspect + validate + cross-cutting checks. The agent picks the spec by the document's *_version field; the tool family handles the rest.
The same 12 specs above, mapped by real tool count — plus the DefenseTech extension. Click a hub to filter, click a leaf for the real tool name. Tab through with a keyboard; Enter/Space activates a node like a click.
AEO Protocol
Entity declaration at /.well-known/aeo.json. Fetch, inspect, extract a claim, compute the well-known URL.
aeo_fetch aeo_inspectPrompt Provenance
Validate Prompt Provenance documents against the v0.1 schema. Inspect, evaluate result.
prompt_provenance_validate prompt_provenance_eval_resultAgent Cards
Inspect or validate Agent Cards. Probe the tool disclosure surface. Resolve well-known URL.
agent_card_validate agent_card_tool_disclosureAI Evidence Format
Validate, inspect, and verify the content hash of an AI Evidence object.
ai_evidence_validate ai_evidence_verify_hashMCP Tool Cards
Inspect or validate MCP Tool Cards. Check tested-with declarations. Resolve well-known URL.
tool_card_validate tool_card_tested_withAI Tutor Cards
Fetch, inspect, validate, check COPPA applicability, check subject coverage, well-known.
tutor_card_coppa_check tutor_card_subject_checkStudent AI Disclosure
Validate, inspect, check against AUP, verify prompt hash, verify artifact hash.
disclosure_aup_check disclosure_verify_prompt_hashClassroom AI AUP
Fetch, inspect, validate, check compliance against a student disclosure, well-known URL.
aup_check_compliance aup_validateClinical AI Disclosure
Fetch, inspect, validate, well-known. Clinical-AI vocabulary aligned with FDA SaMD + IMDRF.
clinical_ai_validate clinical_ai_inspectAI Incident Card
Fetch, inspect, validate, index, well-known.
incident_validate incident_inspectAI Procurement Decision Card
Fetch, inspect, validate, well-known.
decision_card_validate decision_card_inspectAI Claims Decision Card
Validate and inspect an insurer/adjudicator claims record. Sign the canonical hash, chain a new card to its predecessor.
claims_card_validate claims_card_signDefenseTech 8-pack — 8 tools
Beyond the 12 horizontal specs, the DefenseTech 8-pack adds a vertical-specific tool family: 3-axis vault contract resolver (CUI tier × export-control × foreign-person), CUI distribution-statement invariant (DoDI 5230.24), ITAR us-person check (22 CFR 120.62 + deemed-export rule), DFARS 72-hour wall-clock, CMMC evidence-bundle summarizer, Incident Card event-type classifier, cross-binding consistency check.
defensetech_vault_resolve_3axis defensetech_audit_event_check_invariants defensetech_check_dfars_72h_clock defensetech_summarize_cmmc_evidence_bundleImplementation-preview tools (16)
Beyond the spec-level surface, the unified server wraps the v0.1.0 implementation stack at preview scale — read-only, deterministic, no HTTP round trip. These are the tools an agent reaches for when it needs to compute against governance state, not just validate documents.
Hash attestation (3 tools)
Canonical-hash an object, verify a detached signature, inspect a signed attestation envelope. Same math as hash-attestation-rs.
Audit-stream (6 tools)
Compose events, verify a supplied hash chain, and inspect events. Optional emit/query/verify calls need a running audit-stream-py service plus AUDIT_STREAM_URL and AUDIT_STREAM_TOKEN; chain verification alone does not establish a complete audit trail.
Decision Intelligence (5 tools)
Infer Decision Card status from a rubric, compute signature, preview generated PolicyBundle, plan incident remediation, walk affected systems.
Cross-spec drift (2 tools)
Detect which Suite spec a JSON document is. Compute a structural diff between two versions of the same document — catches the silent re-shape.
Use it in 60 seconds
Drop one entry into your Claude Desktop / Cursor / Cline config. Restart the client. 75 tools appear.
~/Library/Application Support/Claude/ · Windows: %APPDATA%\Claude\){ "mcpServers": { "kinetic-gain": { "command": "npx", "args": ["-y", "mcp-kinetic-gain@0.10.0"] } } }
The three optional live audit-stream tools require both AUDIT_STREAM_URL and a configured AUDIT_STREAM_TOKEN for an approved audit-stream-py service. The shared token authenticates the MCP process, not the caller-asserted source or tenant. Without that configuration those tools return an error; URL fetch tools can still contact user-supplied public origins. The default stdio tools are previews, not a governed request gateway.
A separate one-tool signed-card HTTP pilot is still a draft source change. It is not in the published npm package or MCP Registry release and has not passed a hosted buyer-boundary drill.
Who's this for
Three audiences. One config entry.
Application developers
Building an agent that needs to inspect or validate Kinetic Gain Protocol Suite documents. Optional audit-event writes require an approved configured sink.
Security / GRC teams
Auditing vendor AI disclosures, running policy-as-code previews against Decision Cards, verifying hash-chained event logs, checking DefenseTech invariants on CUI/ITAR-bearing artifacts.
Procurement / DPO
Pair with the Lock-In Cost calculator and SLA Negotiator — let the agent fetch + validate a vendor's published disclosures while you negotiate the contract.
Where to next
The published server is a local MCP tool surface. To explore the specs, the visualizer, or the implementation stack:
Suite hub
The twelve specs, side-by-side, with audit-stream + Decision Card patterns.
Visualizer
Explore the currently supported Suite document types visually; the visualizer's latest verified detector covers 11 of the 12 MCP/spec types.
Source
TypeScript source, AGPL-3.0 license, tool catalog, tests, and release workflows.
Registry docs
Distribution and release notes; verify a registry's current record before relying on it.