Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/bayinl/dida-mcp/dida365)<a href="https://agentmods.dev/mcp/bayinl/dida-mcp/dida365"><img src="https://agentmods.dev/badge/mcp/bayinl/dida-mcp/dida365.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
dida365 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"dida365": {
"type": "stdio",
"command": "uv",
"args": [
"--directory",
"/Users/YOUR_USERNAME/dida365-mcp-server",
"run",
"python",
"-m",
"src.server"
],
"env": {
"DIDA365_CLIENT_ID": "your_client_id_here",
"DIDA365_CLIENT_SECRET": "your_client_secret_here",
"DIDA365_REDIRECT_URI": "http://127.0.0.1:8080/callback",
"DIDA365_BASE_URL": "https://api.dida365.com/open/v1",
"TOKEN_FILE": "/Users/YOUR_USERNAME/dida365-mcp-server/.token-oauth"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 21 lines scan A 404a3c410fca
dida365 is an MCP server published in the GitHub repository BayInl/Dida-MCP (8 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
amazing-marvin-complete-mcp
MCP server for Amazing Marvin with complete public-API coverage (34 tools). Runs locally from the amazing-marvin-complete-mcp Python package. Needs 3 environment variables to run.
megaplan
MCP server for Megaplan — tasks, deals, project management (Russia). Runs locally from the @theyahia/megaplan-mcp npm package. Needs 2 environment variables to run.
jira-product-discovery-mcp
MCP server for Jira Cloud REST APIs, native Jira Product Discovery Insights, and supporting attachments. Runs locally from the @enterpret/jira-product-discovery-mcp npm package.
autonomous-sdlc-command-center
MCP server "autonomous-sdlc-command-center" as configured in Senpai-Sama7/autonomous-sdlc-command-center. Runs locally from the autonomous-sdlc-command-center Python package.
mcp-server-rt
MCP server for RT (Request Tracker). Runs locally from the mcp-server-rt npm package. Needs 2 environment variables to run.
taskmarket
MCP server "taskmarket" as configured in Codecraft-Ops/taskmarket-mcp. Launched with https://github.com/Codecraft-Ops/taskmarket-mcp/releases/download/v0.1.0/taskmar.