Sentrik
NPM · SENTRIK · SCANNED SEP 28
Governance runtime for AI-generated code. Enforce compliance and security standards.
Available components
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 Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 71 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the Sentrik MCP server?
Sentrik runs locally as an npm package, launched with npx -y sentrik. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sentrik
claude mcp add maxgerhardson-sentrik -- npx -y sentrik
{
"mcpServers": {
"maxgerhardson-sentrik": {
"command": "npx",
"args": [
"-y",
"sentrik"
]
}
}
} {
"servers": {
"maxgerhardson-sentrik": {
"command": "npx",
"args": [
"-y",
"sentrik"
]
}
}
} codex mcp add maxgerhardson-sentrik -- npx -y sentrik
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"maxgerhardson-sentrik": {
"type": "local",
"command": [
"npx",
"-y",
"sentrik"
],
"enabled": true
}
}
} openclaw mcp add maxgerhardson-sentrik --command npx --arg -y --arg sentrik
mcp_servers:
maxgerhardson-sentrik:
command: "npx"
args: ["-y", "sentrik"] {
"McpServers": {
"maxgerhardson-sentrik": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"sentrik"
]
}
}
} assistant mcp add maxgerhardson-sentrik -t stdio -c npx -a -y sentrik
{
"mcpServers": {
"maxgerhardson-sentrik": {
"command": "npx",
"args": [
"-y",
"sentrik"
]
}
}
} 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
- 23 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 22 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 28 Sept 2026 · Analysed npm/sentrik@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node install.js |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the Sentrik MCP server?
Sentrik is an MCP server listed in the public MCP registry as io.github.maxgerhardson/sentrik. Governance runtime for AI-generated code. Enforce compliance and security standards. This page covers its npm package (sentrik).
Is the Sentrik MCP server safe to use?
Sentrik scores 35 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 28 September 2026. 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.
Is the Sentrik MCP server still maintained?
Sentrik is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.