@mima-ai/governance-mcp

MCP@deman-maker
v0.1.13works.mimaUnknownUpdated 3mo agonpmGitHub

AI governance evidence for EU AI Act, ISO 42001, SOC 2, and NIST AI RMF.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

@deman-maker
Identity-verified publisher GitHub@deman-maker
Verified Aug 11, 2026
3mo agoLast update
Package
Authorworks.mima
LicenseUnknown
Version0.1.13
Sourcenpm+mcp-registry
Trust Status
A
80/100Trusted
✓Listed in Forge index+10/10
✓Publisher identity verified+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
Publisher@deman-maker
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv0.1.13 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 4, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev0.1.13 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

acknowledge_policyRecord that a team member has read and understood an AI governance policy.

Record that a team member has read and understood an AI governance policy.

No input schema was published for this tool.

attestRecord a compliance evidence event in the Mima governance ledger, mapped to

Record a compliance evidence event in the Mima governance ledger, mapped to

No input schema was published for this tool.

derive_controlsReturns your current governance coverage gaps relative to the described action.

Returns your current governance coverage gaps relative to the described action.

No input schema was published for this tool.

dry_run_attestPreview which compliance controls a proposed evidence record would earn — without writing

Preview which compliance controls a proposed evidence record would earn — without writing

No input schema was published for this tool.

check_gatesCheck the status of all configured governance gates for this workspace.

Check the status of all configured governance gates for this workspace.

No input schema was published for this tool.

list_evidenceList evidence records from the governance ledger, optionally filtered by system and time.

List evidence records from the governance ledger, optionally filtered by system and time.

No input schema was published for this tool.

list_systemsList all AI systems in this workspace with their registration status and evidence coverage.

List all AI systems in this workspace with their registration status and evidence coverage.

No input schema was published for this tool.

get_postureGet the current AI governance posture for this workspace. Returns per-framework

Get the current AI governance posture for this workspace. Returns per-framework

No input schema was published for this tool.

register_systemRegister an AI system in the Mima governance ledger. Creates an Art. 9 risk assessment

Register an AI system in the Mima governance ledger. Creates an Art. 9 risk assessment

No input schema was published for this tool.

suggest_gatesAnalyse the current governance posture and gate configuration, then return

Analyse the current governance posture and gate configuration, then return

No input schema was published for this tool.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

AI governance evidence for EU AI Act, ISO 42001, SOC 2, and NIST AI RMF.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-28 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.