register-mcp@0.7.0
VERIFIED· not startedPublisher claims: "MCP Server for the Swiss commercial register (Zefix), with a company-UID join to the official gazettes (SHAB + cantonal Amtsblätter)" 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_TOKENMCP_API_KEYConfiguration, not credentials: GAZETTE_MAX_RETRIES, GAZETTE_RETRY_BACKOFF, GAZETTE_TOTAL_BUDGET, GITHUB_OUTPUT, LEGAL_FORMS_TTL, MCP_ALLOWED_HOSTS, MCP_RATE_LIMIT, MCP_RATE_WINDOW, MCP_TRANSPORT, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_SERVICE_NAME, OTEL_SERVICE_VERSION, RUBRICS_TTL- Where it talks to
- no vendor host named in the codeAlso amtsblattportal.ch, shields.io, admin.ch — 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 amtsblattportal.ch, shields.io, admin.ch as well as its own vendor. The guard injects GITHUB_TOKEN, MCP_API_KEY 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-15 and scored it 87/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
pytest tests/ -m live -v --junitxml=live-report.xml 2>&1 | tee live-output.txtFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.res = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.done = subprocess.run(call, capture_output=True, text=True, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(["git", "init", "-q", str(self.root)], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(["git", "-C", str(root), "add", "kladde.txt"], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(["rm", "-rf", str(self.tmp / "origin")], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.lauf = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.await client.get("http://169.254.169.254/latest/meta-data/")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.r = subprocess.run(["git", "-C", str(root), *args], capture_output=True, text=True, timeout=120)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.MCP_API_KEY: ${MCP_API_KEY:?set MCP_API_KEY in your shell or .env}Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# uv pinned via its official image to avoid pulling a curl|sh install script.Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(["git", "-C", str(self.root), "add", rel], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."""`MCPServer` lehnt einen unbekannten Schluessel schon im Konstruktor ab;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.subprocess.run(["git", "init", "-q", str(root)], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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
Not checked against OSV yet; the weekly check has not reached this version.