creden-mcp@0.1.0
VERIFIED· not startedPublisher claims: "Enables AI agents to retrieve Thai company data from data.creden.co in a single lookup by Thai/English name or 13-digit juristic ID, returning company profiles, multi-year financial statements, directors, shareholder percentages, and authorized signers. Supports optional credential-based access for gated fields with automatic session re-login." 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
CREDEN_PASSWORDDOCKER_HUB_TOKENConfiguration, not credentials: CREDEN_BASE_URL, CREDEN_DEFAULT_LANG, CREDEN_EMAIL, CREDEN_REQUEST_DELAY, CREDEN_SESSION_FILE, MCP_TRANSPORT- Where it talks to
- creden.co (its own)
- 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. It asks for CREDEN_PASSWORD, DOCKER_HUB_TOKEN and talks to creden.co. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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-13 and scored it 84/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
cwd_env = Path.cwd() / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."ต้องตั้ง CREDEN_EMAIL/CREDEN_PASSWORD ใน .env "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose..env; without them, financials/profile still work fine. Auth dataFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.chmod 700 "${DOCKER_CONFIG}/docker-credential-centermcp"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts."CREDEN_EMAIL and CREDEN_PASSWORD must be set in environment or .env file"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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.