operativa-mcp@0.1.5
VERIFIED· not startedPublisher claims: "Executive AI & Systems Consultant - MCP Server" 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
GITHUB_OAUTH_CLIENT_IDGITHUB_OAUTH_CLIENT_SECRETGOOGLE_OAUTH_CLIENT_IDGOOGLE_OAUTH_CLIENT_SECRETOPERATIVA_DATABASE_URLOPERATIVA_TOKENSESSION_SECRET_KEYConfiguration, not credentials: ADMIN_EMAIL, FLASK_ENV, OPERATIVA_ENCRYPTION_KEY, OPERATIVA_ENV, OPERATIVA_LOG_LEVEL, OPERATIVA_MCP_SERVER_PORT, OPERATIVA_MCP_SERVER_URL, OPERATIVA_WEBSITE_PORT, OPERATIVA_WEBSITE_URL- Where it talks to
- operativa.agency (its own)
- 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. It asks for GITHUB_OAUTH_CLIENT_ID, GITHUB_OAUTH_CLIENT_SECRET, GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, OPERATIVA_DATABASE_URL, OPERATIVA_TOKEN, SESSION_SECRET_KEY and talks to operativa.agency. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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-13 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
result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# Load environment variables from .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.MCP_SERVER_URL = os.getenv("OPERATIVA_MCP_SERVER_URL", "http://localhost:8001")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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 operativa-mcp@0.1.5 as of 15 h ago. This is the package itself, not its dependencies.