Is Inkog IO safe and trustworthy?

tashan scores Inkog IO on public evidence — tashan score 39.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, its declared dependencies reach: filesystem. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Inkog IO?

In Claude Code: run `claude mcp add inkog-io-mcp -- npx -y @inkog-io/mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Inkog IO

npm

Security co-pilot for AI agents. Scan for vulnerabilities, verify governance, audit MCP servers, and generate compliance reports — all from Claude, Cursor, or any MCP client.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Security — see all ranked ›

Work: Regulatory compliance · Security review

Who it is for: Legal / compliance · Security engineer

Install (Claude Code):

claude mcp add inkog-io-mcp -- npx -y @inkog-io/mcp

solid

“10 worked examples, 7 tools documented; short of deep on a stated limitation”

This grade is wrong ›

tashan score: 39.0
Instruction depth: 71.0 (solid — documents the job properly, with examples you could follow)
Adoption: 42/wk
Upkeep: 59.0
Freshness: 64.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: Apache-2.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 1.0.21 — this package, not its dependency tree

Reads and writes filesfrom declared dependencies

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-10 @inkog-io/mcp now reaches filesystem Its declared dependencies reach further into your machine than they did before.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 1 change to Inkog IO in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-inkog-io-mcp.svg)](https://tashan.sh/capability/pkg-inkog-io-mcp.html)

npm ↗ · source ↗ · pkg:@inkog-io/mcp

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?