mcp-core-auth@0.6.1
CAUTION· not startedPublisher claims: "Auth, billing, and logging infrastructure for MCP-first servers." 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try mcp-core-auth` runs it now and prints the full answer.
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-07 and scored it 65/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: Access to sensitive file paths; document.cookie access; References a credential file in the home directory. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
`tests/live/` needs `.env.live` (gated live tests; do not run them as part of the default suite).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.document.cookie = hintCookieString(formatHint(sub), hintDomainFor(window.location.hostname, hintDomain), window.location.protocol === "https:");Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.# LOGTO_SSH_KEY path to ssh private key (default: ~/.ssh/id_rsa)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "==> Ensuring .env exists on server (only generated on first deploy)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# - .env file with LOGTO_DOMAIN, LOGTO_ENDPOINT, LOGTO_ADMIN_ENDPOINT,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.print("\n=== paste into .env files ===\n")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.SSH_KEY="${LOGTO_SSH_KEY:-$HOME/.ssh/id_rsa}"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# LOGTO_SSH_KEY path to ssh private key (default: ~/.ssh/id_rsa)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.each product's .env.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if [ ! -f .env ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const readHint = () => (hintOn() ? parseHint(readHintCookie(document.cookie)) : { kind: "unknown", raw: null });Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.# POSTGRES_PASSWORD set (see .env.example; generated below if missing)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Only a dev-bypass server with no Logto configured may pass tokens unverified.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Pinned: `latest` moves without notice. Bump deliberately via LOGTO_IMAGE in .env.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.chmod 600 .envFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts."""Dev bypass token -> auth + billing + logging all work."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./** document.cookie that keeps name=value pairs and honours Domain (any), Max-Age=0. */Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.out = subprocess.check_output(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.py logto_config.py apply --env-file <path/.env.prod> [--yes]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.py logto_config.py plan --env-file <path/.env.prod>Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.py logto_config.py import --env-file <path/.env.prod>Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.py logto_config.py snapshot --env-file <path/.env.prod>Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.fastapi_mcp_server.mount_sse(mount_path=mount_path_legacy)Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.env_file = pathlib.Path(__file__).parent.parent / ".env.live"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Gated by RUN_LIVE_TESTS=1. Requires tests/.env.live with real credentials.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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-core-auth@0.6.1 as of 49 min ago. This is the package itself, not its dependencies.
What would make this Verified
15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim swapp1990: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- document.cookie access≈ +4 on the totalReplace encoded or assembled strings with plain literals and remove undeclared network calls.
- References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.