io.github.mizcausevic-dev/mcp-kinetic-gain
NPM · MCP-KINETIC-GAIN
75-tool MCP server for 12 Kinetic Gain specs and DefenseTech checks.
Available components
Last scanned (3 hours ago)
Scores higher than 94% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mizcausevic-dev/mcp-kinetic-gain). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5643 tokens (~75/item across 75 items; 75 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
- Stability check failed: the tool surface changed between 0.9.1 and 0.10.0: 0 tool removals, 1 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "prompt_provenance_eval_result" implies "eval" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 75 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 79 to 99.
- 16 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 99 to 79.
- 15 Oct 26 +5
- Source repository: unverified → pass ▲ security
- 14 Oct 26 −5
- Provenance: pass → unverified ▼ security
- 13 Oct 26 +2
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 26 −1
- Stability: 0.87 → fail ▼ security
- CVE-2026-93687 no longer affects this package ▲ security
- Known CVEs: partial → pass ▲ security
- Security disclosure: pass → unverified ▼ functional
- Package version: 0.9.3 → 0.10.0 functional
- 3 Oct 26 +1
- CVE-2026-93687 affects this package ▼ security
- Known CVEs: pass → partial ▼ security
- 2 Oct 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed npm/mcp-kinetic-gain@0.10.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mizcausevic-dev/mcp-kinetic-gain |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mizcausevic-dev/mcp-kinetic-gain/.github/workflows/publish.yml@refs/tags/v0.10.0 |
| Rekor log index | 3152455928 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e1c00553b4da153477749674e5fa8788c3f0cace937dfef4862d05b975fa8152cd7692c1c1cc485a3c2c3c93e6f698e171f1e8122f8384e0681050b10 |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
disclosure_validate ~62
Validate a Student AI Disclosure JSON document against the v0.1 schema. Enforces conditional rules (ai_used true requires tools/roles/extent/prompt_mode; ai_used false forbids them; prompt mode gates prompts presence).
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | yes | – |
No output schema declared.
No examples provided.
disclosure_verify_artifact_hash ~138
Recompute SHA-256 over a candidate artifact and compare to disclosure.artifact_hash. Pass either `candidate_text` (canonical SHA-256: LF, no trailing newline) for text artifacts, or `candidate_bytes_base64` (raw-bytes SHA-256) for binary artifacts like PDFs / images. Returns ok=true on match, otherwise { error: artifact_hash_mismatch, expected, recomputed }.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_bytes_base64 | string | – | Base64-encoded raw artifact bytes (raw-bytes mode). |
| candidate_text | string | – | Text artifact (canonical-text mode). |
| document_json | string | yes | – |
No output schema declared.
No examples provided.
disclosure_verify_prompt_hash ~93
Verify a single prompt hash in a hashed-mode disclosure. Looks up prompt_id and compares canonical SHA-256 of candidate_text. Returns ok=true on match or { error: prompt_hash_mismatch, expected, recomputed }. Errors with wrong_prompt_mode if prompt_evidence_mode is not 'hashed'.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_text | string | yes | – |
| document_json | string | yes | – |
| prompt_id | string | yes | – |
No output schema declared.
No examples provided.
incident_affected_walk ~67
Walk an Incident Card's `affected` block and return every referenced Suite document as { uri, kind }. Useful as the seed list for incident-correlation-rs or fan-out validation via aeo-validator-service.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
incident_fetch ~34
Fetch an AI Incident Card from a URL. Returns the parsed, schema-validated JSON document.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
incident_index_fetch ~90
HEADLINE TOOL, fetch a vendor's /.well-known/ai-incidents.json index and return a procurement-friendly summary: total count, breakdown by severity, breakdown by status, IDs sorted by disclosed_at descending. The cheapest way for a CISO or procurement reviewer to scan a vendor's incident history.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | yes | Vendor origin (e.g. https://edu.kineticgain.com). |
No output schema declared.
No examples provided.
incident_inspect ~78
Structured summary of an AI Incident Card: incident identity (id, title, severity, categories, status, timeline), affected products + versions + Agent/Tutor/Tool Card cross-references, root cause, harm, mitigation, regulatory filings, withdrawal posture, revision metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
incident_remediation_plan ~78
Map each affected URI in an Incident Card to a recommended Action + Urgency. Single-hop preview of what incident-correlation-rs.correlate() would produce: agent/tutor/tool-card -> revalidate; vendor/product -> request_review. Urgency follows severity.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
incident_validate ~92
Validate an AI Incident Card JSON document against the v0.1 schema. Enforces conditional rules: status=resolved requires resolved_at; status=withdrawn requires withdrawal block; non-empty regulatory.reported_to requires non-empty regulatory_filing_uris; root_cause.category=other and categories containing 'other' both require the corresponding _other_text fields.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | yes | Incident Card as inline JSON. |
No output schema declared.
No examples provided.
incident_well_known_url ~62
Compute the canonical AI Incident Card well-known URL: /.well-known/ai-incidents/<id>.json.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | Convention: INC-<YYYY-MM-DD>-<vendor>-<seq> |
| origin | string | yes | – |
No output schema declared.
No examples provided.
prompt_provenance_eval_result ~49
Extract a single evaluation suite's result from a Prompt Provenance document.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | yes | – |
| suite_name | string | yes | Name of the evaluation suite to extract. |
No output schema declared.
No examples provided.
prompt_provenance_inspect ~40
Structured summary of a Prompt Provenance document: prompt identity, lineage, approval state, evaluation suites.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | yes | – |
No output schema declared.
No examples provided.
prompt_provenance_validate ~61
Validate a Prompt Provenance JSON document against the v0.1 schema. Returns { valid, prompt_id, version } or { valid: false, reason }.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | yes | A Prompt Provenance JSON document as a string. |
No output schema declared.
No examples provided.
suite_doc_detect_spec ~63
Detect which Kinetic Gain Suite spec a JSON document is by sniffing its top-level *_version field. Returns { spec, version_field, version }. Recognises all 12 specs; returns spec='unknown' for anything else.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
No output schema declared.
No examples provided.
suite_doc_drift ~81
Structural diff between two versions of the same Suite document. Returns { drifted, spec_before, spec_after, spec_changed, content_hash_before, content_hash_after, added_fields, removed_fields, changed_fields }, mirrors the DriftReport shape aeo-validator-service emits for watch rechecks.
| Name | Type | Req | Description |
|---|---|---|---|
| after | object | yes | – |
| before | object | yes | – |
No output schema declared.
No examples provided.
tool_card_inspect ~59
Structured summary of an MCP Tool Card: tool identity, safety profile (side-effect class, PII/secrets exposure, approval requirement), test count, p99 latency.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
tool_card_tested_with ~74
Return the tested-LLM entries for a tool, optionally filtered by a substring match on the LLM identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | – | – |
| llm_filter | string | – | Substring of the LLM identifier to filter by (case-insensitive). Optional. |
| url | string | – | – |
No output schema declared.
No examples provided.
tool_card_validate ~32
Validate an MCP Tool Card JSON document against the v0.1 schema.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | yes | – |
No output schema declared.
No examples provided.
tool_card_well_known_url ~55
Compute the canonical MCP Tool Card well-known URL (convention: /.well-known/mcp-tools/<tool_name>.json).
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_server_origin | string | yes | – |
| tool_name | string | yes | – |
No output schema declared.
No examples provided.
tutor_card_coppa_check ~76
Enforce the spec's COPPA conditional rule: if audience.age_range_min < 13, data_privacy.coppa_compliant MUST be true. Returns { ok: true } or { error: coppa_violation, reason }.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
tutor_card_fetch ~33
Fetch a Tutor Card from a URL. Returns the parsed, schema-validated JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
tutor_card_inspect ~65
Structured summary of a Tutor Card: tutor identity, audience, pedagogy, subject scope counts, safety strength, FERPA/COPPA/GDPR posture, evaluation count, COPPA-rule check.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
tutor_card_subject_check ~79
Classify a topic against the tutor's subject scope. Returns one of: primary, included, excluded, unknown, with the matched term when applicable.
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | – | – |
| query | string | yes | Topic to classify, e.g. 'algebra' or 'differential equations'. |
| url | string | – | – |
No output schema declared.
No examples provided.
tutor_card_validate ~54
Validate an AI Tutor Card JSON document against the v0.1 schema, including the COPPA conditional rule (age_range_min < 13 ⇒ coppa_compliant must be true).
| Name | Type | Req | Description |
|---|---|---|---|
| document_json | string | yes | – |
No output schema declared.
No examples provided.
tutor_card_well_known_url ~53
Compute the canonical AI Tutor Card well-known URL (convention: /.well-known/tutors/<tutor_id>.json).
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | yes | – |
| tutor_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.mizcausevic-dev/mcp-kinetic-gain server?
io.github.mizcausevic-dev/mcp-kinetic-gain runs locally as an npm package, launched with npx -y mcp-kinetic-gain. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-kinetic-gain
claude mcp add mizcausevic-dev-mcp-kinetic-gain -- npx -y mcp-kinetic-gain
What is the io.github.mizcausevic-dev/mcp-kinetic-gain server?
io.github.mizcausevic-dev/mcp-kinetic-gain is listed in the public MCP registry as io.github.mizcausevic-dev/mcp-kinetic-gain. 75-tool MCP server for 12 Kinetic Gain specs and DefenseTech checks. This page covers its npm package (mcp-kinetic-gain).
Is the io.github.mizcausevic-dev/mcp-kinetic-gain server safe to use?
io.github.mizcausevic-dev/mcp-kinetic-gain scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mizcausevic-dev/mcp-kinetic-gain server expose?
io.github.mizcausevic-dev/mcp-kinetic-gain exposes 75 tools: aeo_fetch, aeo_inspect, aeo_get_claim, aeo_well_known_url, prompt_provenance_validate, and 70 more. Their descriptions and schemas cost roughly 5,643 tokens of context every time the server is loaded.
Is the io.github.mizcausevic-dev/mcp-kinetic-gain server still maintained?
io.github.mizcausevic-dev/mcp-kinetic-gain is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mizcausevic-dev/mcp-kinetic-gain server under?
io.github.mizcausevic-dev/mcp-kinetic-gain declares the AGPL-3.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.