mcp-server-tibet@1.0.2
VERIFIED· startup onlyPublisher claims: "TIBET MCP Server - Transaction/Interaction-Based Evidence Trail. Trust & provenance for AI systems." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
ASTERISK_AMI_SECRETConfiguration, not credentials: ASTERISK_AMI_PORT, ASTERISK_AMI_USER, ASTERISK_HOST, GOOGLE_LOCATION, GOOGLE_PROJECT_ID, GOOGLE_TTS_ENABLED- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for ASTERISK_AMI_SECRET and talks to its vendor. 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; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 94/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 · 40 s · 2 scenarios · 0 deviationsStatic findings
OLLAMA_URL = "http://192.168.4.85:11434"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.KIT_API_URL = "http://192.168.4.85:5000"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.KIT_URL = "http://192.168.4.85:11434"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.OOMLLAMA_URL = "http://192.168.4.85:11434/api/generate"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.TTS_URL = "http://192.168.4.85:5000/tts" # Kit APIFix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.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-server-tibet@1.0.2 as of 5d ago. This is the package itself, not its dependencies.