fritzos8-mcp@0.2.0
CAUTION· not startedPublisher claims: "Platform MCP server for AVM FRITZ!Box with FRITZ!OS 8 (TR-064 + /api/v0 REST) with tiered write safety" 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: Caution 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso telegram.org, cloudflare.com, breitbandmessung.de, ieee.org — 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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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-15 and scored it 75/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Auto-update or dynamic fetch configuration; Telegram Bot API URL; Auto-update or dynamic fetch configuration. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
"auto_update_mode": last.get("NewX_AVM-DE_AutoUpdateMode") or None,Fix: Pin versions and sources; vendor anything fetched at install time.url = f"https://api.telegram.org/bot{self.tg_token}/sendMessage"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.details = {"auto_update_mode": mode or None}Fix: Pin versions and sources; vendor anything fetched at install time.Demo: network doctor, security check and the plan → token → execute safety modelFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct."firmware_auto_update": "System > Update > Auto-Update: 'Neue Versionen automatisch installieren' wählen.",Fix: Pin versions and sources; vendor anything fetched at install time.def serve_http(server: MCPServer, settings: HttpSettings) -> None: # pragma: no cover - blocking, uvicornFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.def build_http_app(server: MCPServer, settings: HttpSettings, *, json_response: bool = False) -> ASGIApp: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 fritzos8-mcp@0.2.0 as of 2 h ago. This is the package itself, not its dependencies.
What would make this Verified
5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim tomwellnitz: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Telegram Bot API URL≈ +4 on the totalReplace encoded or assembled strings with plain literals and remove undeclared network calls.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.