Basecamp 2 MCP (thedistance/Basecamp-2-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Basecamp 2 MCP

Connects AI assistants to the Basecamp 2 API, enabling management of projects, todos, messages, and people directly through natural language.

→ thedistance/Basecamp-2-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

thedistance

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: BASECAMP_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: BASECAMP_ACCESS_TOKEN, BASECAMP_CLIENT_SECRET, BASECAMP_PASSWORD, BASECAMP_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretBASECAMP_ACCESS_TOKENOAuth 2 access token
configBASECAMP_ACCOUNT_ID2. Run the auth helper — it opens a browser, handles the redirect, exchanges the code for tokens, and prints your automatically:
configBASECAMP_CLIENT_ID3. The MCP server will automatically refresh the access token when it expires (~2 weeks) as long as BASECAMP_REFRESH_TOKEN, , and BASECAMP_CLIENT_SECRET are set.
🔐 secretBASECAMP_CLIENT_SECRET3. The MCP server will automatically refresh the access token when it expires (~2 weeks) as long as BASECAMP_REFRESH_TOKEN, BASECAMP_CLIENT_ID, and are set.
🔐 secretBASECAMP_PASSWORDYour Basecamp password (Basic Auth alternative)
🔐 secretBASECAMP_REFRESH_TOKEN3. The MCP server will automatically refresh the access token when it expires (~2 weeks) as long as , BASECAMP_CLIENT_ID, and BASECAMP_CLIENT_SECRET are set.
configBASECAMP_USERNAMEYour Basecamp email (Basic Auth alternative)
configOAUTH_PORTBy default npx basecamp-2-mcp-auth listens on port 3000. Set to change it (your registered redirect URI must match).
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

17/17 tools missing one or more hints — list_topics (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_message (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_message (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

1 call in production code run through a shell (src/oauth.ts:65)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

8 secret values sent to error/log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/thedistance/basecamp-2-mcp)](https://m8ven.ai/mcp/thedistance/basecamp-2-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 601adceaf4ff8808ac31eadac112bf9d4912a8c8
code hash: e401b380ae7b4147ac2f385f14618810c7984064c6d65382fff64ece4f2a2c49
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client