C
Warning
74/100
14 hours ago

aide

A unified backend MCP server that aggregates and filters data from external services like Zaim, GitHub, Google, and Notion, providing cross-cutting views via MCP and REST API without heavy AI inference.

Warning. Serious findings were identified. Review the full report before connecting. 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

guchi-apps

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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
4 flows detected: AIDE_GITHUB_ISSUE_TOKEN, AIDE_OPS_DASHBOARD_TOKEN, AIDE_SUBSCRIPTIONS_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 8 credentials: AIDE_AUTH_PASSWORD, AIDE_GITHUB_ISSUE_TOKEN, AIDE_GITHUB_TOKEN, AIDE_INGEST_SECRET, AIDE_OPS_DASHBOARD_TOKEN, AIDE_READ_SECRET, AIDE_SUBSCRIPTIONS_TOKEN, ZAIM_PASSWORD
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.
configAIDE_AUTH_DISABLED認証 許可したGoogleアカウント(AIDE_STATUS_ALLOWED_EMAILS)。Supabase未設定の環境では AIDE_AUTH_PASSWORD。=1 なら素通しし、画面上で警告を出す
🔐 secretAIDE_AUTH_PASSWORD.env は Node 標準の --env-file-if-exists で読ませている。 が未設定だと
configAIDE_BASE_URL/status/auth/callback を登録しておく必要がある。
configAIDE_CACHE_DIR
🔐 secretAIDE_GITHUB_ISSUE_TOKEN(Issues: Read and write)を使う。フォールバックはしない
configAIDE_GITHUB_ORGguchi-apps
configAIDE_GITHUB_REPOSarchived を除き、直近 AIDE_GITHUB_ACTIVE_DAYS 日にpushがあったものを自動で拾う
🔐 secretAIDE_GITHUB_TOKENトークンを分ける。 取得用の はRead-onlyのままで、起票は
🔐 secretAIDE_INGEST_SECRET送信・受信の共通シークレット
configAIDE_INGEST_URLローカルのキャッシュへ直接書く(開発機) そのURLへHTTPで送る(本番)
🔐 secretAIDE_OPS_DASHBOARD_TOKEN取得を試みず「未設定」を返す Authorization: Bearer で認証する
configAIDE_OPS_DASHBOARD_URL
🔐 secretAIDE_READ_SECRET認証 Authorization: Bearer $
configAIDE_SIGNALY_WEBHOOK_URLAIDE_ の一部だけで、ZAIM_ と は含まれない)。サーバー側の
🔐 secretAIDE_SUBSCRIPTIONS_TOKEN取得を試みず「未設定」を返す Authorization: Bearer で認証する
configAIDE_SUBSCRIPTIONS_URL
configAIDE_WORKER_STATE_DIR
configHOSTデフォルトで 127.0.0.1:4747 を listen する。PORT / で変更可。
configZAIM_EMAILと ZAIM_PASSWORD の両方が設定されている環境でだけ有効になる。片方だけの設定は設定漏れとみなし、未設定として扱う。
🔐 secretZAIM_PASSWORDZAIM_EMAIL と の両方が設定されている環境でだけ有効になる。片方だけの設定は設定漏れとみなし、未設定として扱う。
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

5/5 tools missing one or more hints — aide_dev_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); aide_create_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); aide_money_summary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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.).

Tool test coverage

Only 0/5 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

2 child_process/subprocess calls in production code — runs shell commands (src/core/connectors/zaim/session.ts:79, src/core/connectors/zaim/session.ts:92)

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

Secrets stay with their owner

3 secret/sensitive values flow into network calls (AIDE_OPS_DASHBOARD_TOKEN → dynamic, AIDE_SUBSCRIPTIONS_TOKEN → dynamic) (1 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

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 Verified](https://m8ven.ai/badge/mcp/guchi-apps-aide-1jam0a?variant=verified)](https://m8ven.ai/mcp/guchi-apps-aide-1jam0a)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 1882eb30b7cd39fba2a646d4db41a34b84d48dcf
code hash: b126c3e60486ffb7d98f5802f9dc8bb4d8845ae592b7b66669b0a6a4bcb73864
verified: 8/19/2026, 3:05:41 AM
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