io.github.yofor/ovanek-mcp
NPM · @OVANEK/MCP · 2 COMPONENTS · SCANNED OCT 9
Ovanek MCP: Model Context Protocol server for Ovanek platform tools; writes are dry-run by default.
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 →
No category breakdown is available for this channel yet.
How do I install the io.github.yofor/ovanek-mcp server?
io.github.yofor/ovanek-mcp runs locally as an npm package, launched with npx -y @ovanek/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ovanek/mcp
claude mcp add yofor-ovanek-mcp -- npx -y @ovanek/mcp
{
"mcpServers": {
"yofor-ovanek-mcp": {
"command": "npx",
"args": [
"-y",
"@ovanek/mcp"
]
}
}
} {
"servers": {
"yofor-ovanek-mcp": {
"command": "npx",
"args": [
"-y",
"@ovanek/mcp"
]
}
}
} codex mcp add yofor-ovanek-mcp -- npx -y @ovanek/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yofor-ovanek-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@ovanek/mcp"
],
"enabled": true
}
}
} openclaw mcp add yofor-ovanek-mcp --command npx --arg -y --arg @ovanek/mcp
mcp_servers:
yofor-ovanek-mcp:
command: "npx"
args: ["-y", "@ovanek/mcp"] {
"McpServers": {
"yofor-ovanek-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ovanek/mcp"
]
}
}
} assistant mcp add yofor-ovanek-mcp -t stdio -c npx -a -y @ovanek/mcp
{
"mcpServers": {
"yofor-ovanek-mcp": {
"command": "npx",
"args": [
"-y",
"@ovanek/mcp"
]
}
}
} 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.
We have not recorded any changes for this component yet
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 9 Oct 2026 · Analysed npm/@ovanek/mcp@1.0.0
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 91 packages
| Packages resolved | 91 |
|---|---|
| Stale | 17 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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. This package has not been through a sandbox run yet.