krs-poland-mcp-server@1.6.0
VERIFIEDPublisher claims: "The MCP server for KRS Poland public API." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Server started and answered tools/list.- Tested
- MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with real credentials
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 ms.gov.pl — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- what the tools do when called with real credentials
Connect it under the guard; read the third-party hosts first. The code names ms.gov.pl as well as its own vendor. The guard pins the network to the hosts the honeypot saw.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.3.5
vet-skills diff krs-poland-mcp-server 1.3.5 1.6.0This version reaches for something 1.3.5 did not: 4 new tools (Check_KRS_Status, Check_KRS_Watchlist, Get_KRS_Entity_Profile, Get_KRS_Entry_History) · 2 rewritten tool descriptors (Get_Current_KRS_Record, Get_Full_KRS_Record). Compared from the two recorded runs, not from source.
- New tools
- Check_KRS_Status, Check_KRS_Watchlist, Get_KRS_Entity_Profile, Get_KRS_Entry_History
- Rewritten tool descriptors
- Get_Current_KRS_Record, Get_Full_KRS_Record
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-21 and scored it 95/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 37 s · 2 scenarios · 0 deviationsStatic findings
No findings across 2,147 lines in 5 files.
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.