sktime-mcp@0.1.1
VERIFIED· not startedPublisher claims: "MCP (Model Context Protocol) layer for sktime - Registry-Driven for LLMs" 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
SKTIME_MCP_MAX_RESPONSE_TOKENSConfiguration, not credentials: SKTIME_MCP_AUTO_FORMAT, SKTIME_MCP_JOB_CLEANUP_INTERVAL, SKTIME_MCP_JOB_MAX_AGE_HOURS, SKTIME_MCP_LOG_LEVEL, SKTIME_MCP_LOG_PATH, SKTIME_MCP_MAX_DATA_HANDLES- Where it talks to
- no vendor host named in the codeAlso githubusercontent.com — 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 githubusercontent.com as well as its own vendor. The guard injects SKTIME_MCP_MAX_RESPONSE_TOKENS 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-18 and scored it 93/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
No findings across 12,393 lines in 60 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
No advisories in OSV for sktime-mcp@0.1.1 as of 26 min ago. This is the package itself, not its dependencies.