osidb-mcp@0.4.1
VERIFIED· not startedPublisher claims: "Model Context Protocol (MCP) server for OSIDB using osidb-bindings" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
JIRA_ACCESS_TOKENOSIDB_AUTHOSIDB_PASSWORDConfiguration, not credentials: AEGIS_URL, JIRA_API_EMAIL, JIRA_URL, OSIDB_BASE_URL, OSIDB_MCP_ACCESS_MODE, OSIDB_MCP_PROFILE, OSIDB_USER_AGENT, OSIDB_USERNAME- Where it talks to
- no vendor host named in the codeAlso redhat.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names redhat.com as well as its own vendor. The guard injects JIRA_ACCESS_TOKEN, OSIDB_AUTH, OSIDB_PASSWORD only into requests to the host you bind (and its subdomains) and refuses the rest.
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 ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
# Fallback: .env in the project root (two levels up from this file)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Best-effort .env loading; no-op when python-dotenv is absent.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.then falls back to a .env next to the installed package source so that theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.pkg_env = Path(__file__).resolve().parent.parent.parent / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.cwd_env = Path.cwd() / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for osidb-mcp@0.4.1 as of 7 h ago. This is the package itself, not its dependencies.