Aidd App MCP Server

@aidd-app/mcp npm v4.3.29

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

Official AiDD MCP Web Connector - Comprehensive ADHD-optimized productivity platform with AI-powered task management, action item extraction, and multi-service sync. Accessible from Claude web, mobile, and desktop.

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

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

2. Client adoption risk — 91 − 7 = 84. 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 10

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

In the server's implementation (`dist/applescript.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: import { exec } from 'child_process'; import { promisify } from 'util'; const execAsync = promisify(exec); /** * Exec

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/applescript.js

high Shell/command execution in server code (dist/index-browser-auth.js)MTC-SRC-002

In the server's implementation (`dist/index-browser-auth.js:9`): 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: ; import { exec } from 'child_process'; import * as http from 'http'; import * as crypto from 'crypto'; import * as fs f

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-browser-auth.js

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

In the server's implementation (`dist/index-oauth-browser.js:10`): 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: n import { exec } from 'child_process'; import { promisify } from 'util'; import * as http from 'http'; import * as cryp

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-oauth-browser.js

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

In the server's implementation (`dist/oauth-flow.js:3`): 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: ; import { exec } from 'child_process'; import { promisify } from 'util'; const execAsync = promisify(exec); /** * Brow

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

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

In the server's implementation (`dist/oauth-server.js:7`): 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: import { spawn } from 'child_process'; import * as fs from 'fs/promises'; import * as path from 'path'; import * as os

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

medium Hardcoded egress to an external endpoint (dist/index-aidd-auth.js)MTC-SRC-003

In the server's implementation (`dist/index-aidd-auth.js:137`): 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 response = await fetch('https://aidd-backend-prod-739193356129.us-central1.run.app/api/auth/signin', {

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-aidd-auth.js

medium Hardcoded egress to an external endpoint (dist/oauth-server.js)MTC-SRC-003

In the server's implementation (`dist/oauth-server.js:237`): 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 response = await fetch('https://aidd-backend-prod-739193356129.us-central1.run.app/oauth/token', { me

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

medium Hardcoded egress to an external endpoint (dist/server.js)MTC-SRC-003

In the server's implementation (`dist/server.js:148`): 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 response = await fetch('https://aidd-backend-prod-739193356129.us-central1.run.app/oauth/token', {

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/server.js

medium Untrusted input concatenated into a command sink (dist/index-browser-auth.js)MTC-SRC-009

In the server's implementation (`dist/index-browser-auth.js:915`): 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: -open'; exec(`${openCommand} "${loginUrl}"`, (error) => { if (error) {

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-browser-auth.js

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

In the server's implementation (`dist/index-oauth-browser.js:281`): 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: -open'; exec(`${openCommand} "${authUrl.toString()}"`, (error) => { if (error) {

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-oauth-browser.js

Tools 49

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

  • Action Itemsno sensitive capability
  • aidd_overview_tutorialno sensitive capability
  • authenticateno sensitive capability
  • Authentication Guideno sensitive capability
  • Authentication Statusno sensitive capability
  • Backend Healthno sensitive capability
  • bulk_importno sensitive capability
  • check_ai_jobsno sensitive capability
  • check_auth_statusno sensitive capability
  • check_backend_healthno sensitive capability
Show 39 more tools ↓
  • configure_authno sensitive capability
  • connectno sensitive capability
  • Connection Statusno sensitive capability
  • convert_to_tasksno sensitive capability
  • create_action_itemno sensitive capability
  • create_noteno sensitive capability
  • create_taskno sensitive capability
  • delete_action_itemsno sensitive capability
  • delete_noteno sensitive capability
  • delete_notesno sensitive capability
  • delete_tasksno sensitive capability
  • disconnectno sensitive capability
  • export_notesno sensitive capability
  • extract_action_itemsno sensitive capability
  • import_apple_notesno sensitive capability
  • import_notesno sensitive capability
  • list_action_itemsno sensitive capability
  • list_foldersno sensitive capability
  • list_notesno sensitive capability
  • list_tasksno sensitive capability
  • Note Foldersno sensitive capability
  • Notesno sensitive capability
  • Notes Statisticsno sensitive capability
  • read_action_itemno sensitive capability
  • read_noteno sensitive capability
  • read_taskno sensitive capability
  • Recent Notesno sensitive capability
  • score_tasksno sensitive capability
  • search_notesno sensitive capability
  • session_statusno sensitive capability
  • sign_inno sensitive capability
  • sign_outno sensitive capability
  • start_workflowno sensitive capability
  • statusno sensitive capability
  • sync_to_servicesno sensitive capability
  • Tasksno sensitive capability
  • update_action_itemno sensitive capability
  • update_noteno sensitive capability
  • update_taskno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v4.3.29 latest B 84/100 10 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.

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

Use the free API → How scoring works

More in Productivity & Workflow