Skills/PyPI/mcp-osiris

mcp-osiris@0.1.0

CAUTION· static only

Publisher claims: "OSIRIS — context engine cache-aware pour agents IA (serveur MCP local, provider-agnostic)." Observed in sandbox: static analysis only — behavior not yet observed.

Registry PyPI (MCP server)Publisher mlkblk-it · publishing for 14 daysInstalls 0Last detonated 6d ago
What would fix thisWatchDispute verdict

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Before you give it your token

It will ask for
OSIRIS_BYSTANDER_BELOW_TOKENSOSIRIS_COMPACT_BELOW_TOKENSOSIRIS_EXTERNALIZE_MIN_TOKENSOSIRIS_FULL_PAYLOAD_TOKENSOSIRIS_MANIFEST_MIN_TOKENSOSIRIS_PRUNE_THRESHOLD_TOKENSOSIRIS_SCHEMA_ACCESS_TOKENSConfiguration, not credentials: OSIRIS_ADAPTIVE, OSIRIS_BENCH_RECALL_BUDGET, OSIRIS_CACHE_TTL_S, OSIRIS_DASHBOARD_DB, OSIRIS_DATA_DIR, OSIRIS_DISPATCH_ONLY, OSIRIS_HOME, OSIRIS_LOG_LEVEL, OSIRIS_MAX_FILE_BYTES, OSIRIS_PHASE_BUDGETS, OSIRIS_PRUNE_MODE, OSIRIS_PYTHON, OSIRIS_ROOTS
Where it talks to
no vendor host named in the codeAlso python.org, astral.sh — not the publisher's domain; check what for before connecting.
What the honeypot saw
nothing has run yet
What we could not test
everything: the server has not run yet

Run it before you trust it. Nothing has run yet: the code was read, the server was not. `vet-skills try` runs this exact version in the honeypot in about a minute.

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-08 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

MEDIUM
Python subprocess execution detectedsrc/osiris/cli.py:107 · Python subprocess execution detectedproc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detecteddashboard/server.py:617 · Python subprocess execution detectedproc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedtests/test_mcp_tools.py:555 · Python subprocess execution detectedout = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

Cost to the agent

Instructions loaded
≈1,455 tok
2 files · 65 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for mcp-osiris@0.1.0 as of 6d ago. This is the package itself, not its dependencies.

What would make this Verified

15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim mlkblk-it: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  3. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim mlkblk-itPropose a patch to the maintainer