mcp@1.22.0
VERIFIED· startup onlyPublisher claims: "Reference implementation of the KYA-OS protocol for Model Context Protocol servers: identity, delegation, proofs, sessions, and verifiable audit trails" 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
DELEGATION_CREDENTIAL_TYPEConfiguration, not credentials: KYA_OS_CARD_META_KEY, KYA_OS_CARD_WELL_KNOWN_PATH, KYA_OS_DID_META_KEY- Where it talks to
- kya-os.org (its own)Also w3id.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
- 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, and read the third-party hosts first. The code names w3id.org as well as its own vendor. The guard injects DELEGATION_CREDENTIAL_TYPE only into requests to kya-os.org (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; startup only; authenticated tool behavior not tested) on 2026-11-11 and scored it 90/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 · 34 s · 2 scenarios · 0 deviationsStatic findings
/** Attach the W3C Bitstring Status List revocation entry (the post-issuance kill switch). */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* fail-closed because the summary now carries the `revocation` kill switch and `delegationRef`Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell./** Attach the W3C Bitstring Status List revocation entry (the post-issuance kill switch). */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* (`delegationRef` proves the `responsibleParty` claim; `revocation` is the kill switch). CarryingFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell./** W3C Bitstring Status List revocation entry (the post-issuance kill switch). */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."changie": "npx --yes [email protected]",Fix: Pin versions and sources; vendor anything fetched at install time.* directly — fail-closed because the summary carries the `revocation` kill switch andFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* directly — fail-closed because the summary carries the `revocation` kill switch andFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* `revocation` (the post-issuance kill switch) — so the projection stays self-verifiable and canFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 @kya-os/mcp@1.22.0 as of 3d ago. This is the package itself, not its dependencies.