mnki-mcp

MCPattested
v0.3.0io.github.MNKIAgentOSApache-2.0Updated 14d agonpmGitHub

mnki-mcp — a local MCP proxy that verifies every tools/call against Agent Trust before it reaches the server (observe → warn → require_approval → enforce). Installed by `mnki protect`.

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
592Downloads/wk
1GitHub stars
14d agoLast update
Needs 1 credential before it runs
  • MNKI_API_KEYAPI keyrequired

    Agent Trust API key with the verify scope (console → Settings → API keys).

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.MNKIAgentOS
LicenseApache-2.0
Version0.3.0
Sourcenpm+mcp-registry
npmmnki-mcp
GitHubMNKIAgentOS/agent-trust
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+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)+5/5
—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
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 0662245
Dependencies✓ 2 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.3.0 · 14d agoHow well does this scan work?
EvalsNone
IndexedSep 18, 2026

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

Tools

No tool declarations found in the source14d ago

Forge read 18 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

mnki-mcp — a local MCP proxy that verifies every tools/call against Agent Trust before it reaches the server (observe → warn → require_approval → enforce). Installed by `mnki protect`.

Keywords
ai-agentsagent-securityauthorizationdelegationspiffewimseauthzenmcpa2ajwsdpopmnki
Alternatives
Comparing tool surfaces…

Dependency tree

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

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

Topics

Related in security