Basecamp (stefanoverna) MCP Server

basecamp-mcp npm v1.2.2

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

Model Context Protocol (MCP) server for Basecamp integration. Enables LLMs to interact with Basecamp projects, messages, todos, comments, people, and kanban boards.

Trust grade
B
83/100
Last scanned get badge →
Trust
B · 83/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
Critical
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
B Why this grade threat 94 − adoption risk = 83/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 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

2. Client adoption risk — 94 − 11 = 83. 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
−10 capability blast radius (critical) — 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 3

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

This server (without client built-ins) exposes a complete data-exfiltration chain: basecamp_download_blob → basecamp_list_uploads ⇒ basecamp_create_comment. Untrusted input is ingested, private data is read, and it can be sent to an external sink — and at least one leg is a direct schema wire (⇒), where a producer's output drops straight into a free-text parameter of the next tool, so the chain needs little agent cooperation. 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 basecamp_download_blob → basecamp_list_uploads → basecamp_create_comment

high Shell/command execution in server code (dist/utils/oauth.js)MTC-SRC-002

In the server's implementation (`dist/utils/oauth.js:1`): 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: ort { exec } from "node:child_process"; import { createServer, } from "node:http"; import { platform } from "node:os"; i

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/utils/oauth.js

medium Untrusted input concatenated into a command sink (dist/utils/oauth.js)MTC-SRC-009

In the server's implementation (`dist/utils/oauth.js:29`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: tart" : "xdg-open"; exec(`${cmd} "${url}"`); } async function exchangeCodeForTokens(code, clientId, clientSecret) {

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/utils/oauth.js

Tools 47

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

  • basecamp_create_commentnetwork egress
  • basecamp_download_blobingests untrusted input
  • basecamp_get_projectingests untrusted input
  • basecamp_list_campfire_messagesingests untrusted input
  • basecamp_list_recordingsingests untrusted input
  • basecamp_list_uploadsreads sensitive data
  • basecamp_complete_todono sensitive capability
  • basecamp_create_answerno sensitive capability
  • basecamp_create_documentno sensitive capability
  • basecamp_create_kanban_cardno sensitive capability
Show 37 more tools ↓
  • basecamp_create_messageno sensitive capability
  • basecamp_create_todono sensitive capability
  • basecamp_create_vaultno sensitive capability
  • basecamp_get_answerno sensitive capability
  • basecamp_get_documentno sensitive capability
  • basecamp_get_kanban_cardno sensitive capability
  • basecamp_get_meno sensitive capability
  • basecamp_get_messageno sensitive capability
  • basecamp_get_personno sensitive capability
  • basecamp_get_questionno sensitive capability
  • basecamp_get_questionnaireno sensitive capability
  • basecamp_get_todosetno sensitive capability
  • basecamp_get_uploadno sensitive capability
  • basecamp_get_vaultno sensitive capability
  • basecamp_list_answersno sensitive capability
  • basecamp_list_commentsno sensitive capability
  • basecamp_list_documentsno sensitive capability
  • basecamp_list_kanban_cardsno sensitive capability
  • basecamp_list_kanban_columnsno sensitive capability
  • basecamp_list_message_typesno sensitive capability
  • basecamp_list_messagesno sensitive capability
  • basecamp_list_peopleno sensitive capability
  • basecamp_list_projectsno sensitive capability
  • basecamp_list_questionsno sensitive capability
  • basecamp_list_todosno sensitive capability
  • basecamp_list_vaultsno sensitive capability
  • basecamp_loginno sensitive capability
  • basecamp_logoutno sensitive capability
  • basecamp_move_kanban_cardno sensitive capability
  • basecamp_uncomplete_todono sensitive capability
  • basecamp_update_commentno sensitive capability
  • basecamp_update_documentno sensitive capability
  • basecamp_update_kanban_cardno sensitive capability
  • basecamp_update_messageno sensitive capability
  • basecamp_update_todono sensitive capability
  • basecamp_update_vaultno sensitive capability
  • basecamp_whoamino 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 2

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.2.2 latest B 83/100 3 1.13.0 2026-09-07
v1.2.1 B 83/100 3 1.13.0 2026-09-06

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: B · 83/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/basecamp-mcp/badge.svg)](https://mcptrustchecker.com/registry/basecamp-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/basecamp-mcp"><img src="https://mcptrustchecker.com/registry/basecamp-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/basecamp-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 basecamp-mcp --online

Use the free API → How scoring works

Other implementations of Basecamp 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Productivity & Workflow