mcp-kyvos-server@2.4.0
VERIFIED· not startedPublisher claims: "mcp-kyvos-server is a server implementation that integrates the Kyvos platform with the Model Context Protocol (MCP). It enables users to query Kyvos semantic models using natural language, translating prompts into executable queries and returning results from Kyvos. The server supports Streamable HTTP, SSE and STDIO communication modes and allows secure authentication using user-provided Kyvos credentials (basic and OAuth2.0)." 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try mcp-kyvos-server` runs it now and prints the full answer.
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-08 and scored it 82/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
"or pass credentials via the Authorization request header."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.LOADING_DEFAULT_ENV = "Attempting to load environment from default .env file"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load environment variables from file if specified, otherwise try default .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.MCP_SERVER_URL = " The URL where the user wants the MCP server to run. (http://your_url.com:8000)"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.ENV_FILE_DESCRIPTION = "The path to a `.env` file containing environment-specific configurations such as KYVOS_USERNAME, KYVOS_PERSONAL_ACCESS_TOKEN, KYVOS_URL, TRANSPORT, and other parameters. You caFix: 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 mcp-kyvos-server@2.4.0 as of 7d ago. This is the package itself, not its dependencies.