Devto (DevTo-AI) MCP Server
devto-mcp
npm
v0.7.3
Published by devto-ai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
DevTo MCP server — AI work management for Claude Code
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
high Shell/command execution in server code (dist/cli.js)MTC-SRC-002
In the server's implementation (`dist/cli.js:195`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: st { spawn } = require("child_process"); const platform = process.platform; if (platform === "darwin") {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli.js
medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003
In the server's implementation (`dist/index.js:13`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const res = await fetch("https://registry.npmjs.org/devto-mcp/latest", { signal: AbortSignal.timeout(5
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
Tools 44
Each tool and what it can reach — statically extracted from the published source.
add_commentno sensitive capabilityattach_fileno sensitive capabilitybulk_create_tasksno sensitive capabilitybulk_update_tasksno sensitive capabilityconfirm_planno sensitive capabilitycreate_epicno sensitive capabilitycreate_planno sensitive capabilitycreate_sprintno sensitive capabilitycreate_subtaskno sensitive capabilitycreate_taskno sensitive capability
Show 34 more tools ↓
create_versionno sensitive capabilitydelete_commentno sensitive capabilitydelete_issueno sensitive capabilityget_assignable_usersno sensitive capabilityget_backlogno sensitive capabilityget_commentsno sensitive capabilityget_componentsno sensitive capabilityget_custom_fieldsno sensitive capabilityget_epicno sensitive capabilityget_issue_linksno sensitive capabilityget_issue_typesno sensitive capabilityget_labelsno sensitive capabilityget_link_typesno sensitive capabilityget_prioritiesno sensitive capabilityget_project_summaryno sensitive capabilityget_statusno sensitive capabilityget_statusesno sensitive capabilityget_tasksno sensitive capabilityget_worklogno sensitive capabilitylink_issuesno sensitive capabilitylist_attachmentsno sensitive capabilitylist_epicsno sensitive capabilitylist_sprintsno sensitive capabilitylist_versionsno sensitive capabilitylog_workno sensitive capabilitymanage_sprintno sensitive capabilitymanage_watchersno sensitive capabilitymove_to_backlogno sensitive capabilitymove_to_sprintno sensitive capabilityrelease_versionno sensitive capabilitysearch_issuesno sensitive capabilityset_estimateno sensitive capabilityupdate_epicno sensitive capabilityupdate_taskno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (44 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.7.3 latest |
A 93/100 | 2 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan devto-mcp --onlineOther implementations of Devto 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
A Model Context Protocol (MCP) server for the DEV Community (Forem) API. Manage articles, comments, users, tags, and more through MCP-compatible clients.
DEV.to MCP — wraps the DEV Community API (free, no auth for public reads)
More in Productivity & Workflow
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互：发送消息、图片，等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.