Devin Api MCP Server

@jsklan/devin-api-mcp npm v1.1.0

Published by @jsklan — 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.

MCP server for the Devin API — create, manage, and interact with Devin sessions

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

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:

PointsAdoption-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 1

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: get_attachment → list_secrets → send_message. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow get_attachment → list_secrets → send_message

Tools 40

Each tool and what it can reach — statically extracted from the published source.

  • get_attachmentingests untrusted input
  • list_secretsreads sensitive data
  • send_messagenetwork egress
  • add_session_tagsno sensitive capability
  • archive_sessionno sensitive capability
  • ask_questionno sensitive capability
  • create_knowledgeno sensitive capability
  • create_playbookno sensitive capability
  • create_scheduleno sensitive capability
  • create_secretno sensitive capability
Show 30 more tools ↓
  • create_sessionno sensitive capability
  • delete_knowledgeno sensitive capability
  • delete_playbookno sensitive capability
  • delete_scheduleno sensitive capability
  • delete_secretno sensitive capability
  • delete_sessionno sensitive capability
  • gather_sessionsno sensitive capability
  • generate_session_insightsno sensitive capability
  • get_messagesno sensitive capability
  • get_playbookno sensitive capability
  • get_scheduleno sensitive capability
  • get_sessionno sensitive capability
  • get_session_attachmentsno sensitive capability
  • get_session_insightsno sensitive capability
  • get_session_tagsno sensitive capability
  • get_setup_docsno sensitive capability
  • list_knowledgeno sensitive capability
  • list_playbooksno sensitive capability
  • list_schedulesno sensitive capability
  • list_session_insightsno sensitive capability
  • list_sessionsno sensitive capability
  • read_wiki_contentsno sensitive capability
  • read_wiki_structureno sensitive capability
  • replace_session_tagsno sensitive capability
  • terminate_sessionno sensitive capability
  • update_knowledgeno sensitive capability
  • update_playbookno sensitive capability
  • update_scheduleno sensitive capability
  • update_session_tagsno sensitive capability
  • upload_attachmentno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 3

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.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 93/100 1 1.13.0 2026-09-09
v1.0.0 A 94/100 1 1.12.1 2026-08-06
v0.6.0 A 94/100 1 1.12.1 2026-08-05

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/jsklan-devin-api-mcp/badge.svg)](https://mcptrustchecker.com/registry/jsklan-devin-api-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/jsklan-devin-api-mcp"><img src="https://mcptrustchecker.com/registry/jsklan-devin-api-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/jsklan-devin-api-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 @jsklan/devin-api-mcp --online

Use the free API → How scoring works

More in Developer Tools