tlo-mcp@2.4.0
CAUTION· not startedPublisher claims: "MCP (Model Context Protocol) server for TeamLeader Orbit (TLO) - project management and time tracking." 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 tlo-mcp` 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 75/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: Base64 encoding combined with network call. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
`);let[t,n]=e.family===4?[`TCP4`,`0.0.0.0`]:[`TCP6`,`::`];return ur.encode(`PROXY ${t} ${lr(e)} ${n} ${e.port} 443\r\n`)},pr=(e,t)=>{let n=ur.encode(t),r=n.length>0&&n.length<=255?3+n.length:0,i=(e===Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.`);let[t,n]=e.family===4?[`TCP4`,`0.0.0.0`]:[`TCP6`,`::`];return ur.encode(`PROXY ${t} ${lr(e)} ${n} ${e.port} 443\r\n`)},pr=(e,t)=>{let n=ur.encode(t),r=n.length>0&&n.length<=255?3+n.length:0,i=(e===Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.`),e=>x.isNonEmpty(x.trim(e))&&e!==`Linked:`);return{header:t,board:n,...qe.getSomes({owner:O.findFirst(r,x.startsWith(`Owner: `)),description:O.findFirst(r,x.startsWith(`Description: `)),checklist:O.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.import{createRequire as e}from"node:module";import*as t from"@effect/platform-node/NodeRuntime";import*as n from"effect/Effect";import*as r from"effect/Option";import*as i from"effect/Schema";import*aFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.`),e=>x.isNonEmpty(x.trim(e))&&e!==`Linked:`);return{header:t,board:n,...qe.getSomes({owner:O.findFirst(r,x.startsWith(`Owner: `)),description:O.findFirst(r,x.startsWith(`Description: `)),checklist:O.Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.import{createRequire as e}from"node:module";import*as t from"@effect/platform-node/NodeRuntime";import*as n from"effect/Effect";import*as r from"effect/Option";import*as i from"effect/Schema";import*aFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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 @2digits/tlo-mcp@2.4.0 as of 7d ago. This is the package itself, not its dependencies.
What would make this Verified
5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim 2digits: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Obfuscated code≈ +5 on the totalRemove base64-assembled strings, eval of decoded text and minified blobs. Reviewers and scanners both treat unreadable code as hostile.
- Base64 encoding combined with network call≈ +4 on the totalPut hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.
- 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.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.