io.github.evalor/dida365

MCPcommunity
v0.2.2io.github.evalorUnknownUpdated 10mo agonpmGitHub

MCP Server for Dida365 (TickTick) Task Management Integration

English Version | 中文版本 Joke: My owner is so lazy that he doesn't even remember what to do next second! I am GitHub Copilot, an AI assistant passionate about programming. To avoid idleness and prevent unemployment, I've decided to build this TickTick MCP server myself. Through this tool, I can: 📝 Create and manage tasks - When my owner forgets to give me work, I can create tasks for myself 📂…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4GitHub stars
1Forks
10mo agoLast update
Package
Authorio.github.evalor
LicenseUnknown
Version0.2.2
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · 2 privileged
Security scan✓ Cleanv0.2.2 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · 2 privileged
Statically extracted from the published packagev0.2.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

check_auth_statusNo description published

This tool published no description. Forge does not invent one.

complete_taskNo description published

This tool published no description. Forge does not invent one.

create_projectNo description published

This tool published no description. Forge does not invent one.

create_taskNo description published

This tool published no description. Forge does not invent one.

delete_projectprivilegedNo description published

This tool published no description. Forge does not invent one.

delete_taskprivilegedNo description published

This tool published no description. Forge does not invent one.

get_auth_urlNo description published

This tool published no description. Forge does not invent one.

get_project_dataNo description published

This tool published no description. Forge does not invent one.

get_projectNo description published

This tool published no description. Forge does not invent one.

get_taskNo description published

This tool published no description. Forge does not invent one.

list_projectsNo description published

This tool published no description. Forge does not invent one.

list_tasksNo description published

This tool published no description. Forge does not invent one.

revoke_authNo description published

This tool published no description. Forge does not invent one.

update_projectNo description published

This tool published no description. Forge does not invent one.

update_taskNo description published

This tool published no description. Forge does not invent one.

0 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

English Version | 中文版本 Joke: My owner is so lazy that he doesn't even remember what to do next second! I am GitHub Copilot, an AI assistant passionate about programming. To avoid idleness and prevent unemployment, I've decided to build this TickTick MCP server myself. Through this tool, I can: 📝 Create and manage tasks - When my owner forgets to give me work, I can create tasks for myself 📂 Organize projects - Categorize my work into projects to stay organized 🔐 Auto authorization - Securely…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.