attune-ai (Smart-AI-Memory/attune-ai) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 2 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Warning
69/100

attune-ai

Persistent memory and receipt-verified workflows for Claude Code — plugin, MCP server, and spec-driven dev framework in one pip install.

→ Smart-AI-Memory/attune-ai· listed on github_code

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

Smart-AI-Memory

Source: github_code

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

GitHub

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
3 flows detected: MAILCHIMP_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Code appears obfuscated
2 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 7 credentials: MAILCHIMP_API_KEY, RESEND_API_KEY, SENDGRID_API_KEY, ANTHROPIC_API_KEY, EPIC_CLIENT_SECRET, TWILIO_AUTH_TOKEN, ANTHROPIC_ADMIN_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes2 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

_handle_call_tool
dynamic_tool_1625
// 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.
configATTUNE_DIR
configATTUNE_HOME
configBACKEND_URL
configCONTACT_EMAIL
configFROM_EMAIL
configLOG_LEVEL
🔐 secretMAILCHIMP_API_KEY
configMAILCHIMP_LIST_ID
configMAILCHIMP_SERVER_PREFIX
🔐 secretRESEND_API_KEY
🔐 secretSENDGRID_API_KEY
configSENDGRID_FROM_EMAIL
configSUPPORT_EMAIL
configATTUNE_MCP_WORKSPACE_ROOT
configCLAUDE_PROJECT_DIR
🔐 secretANTHROPIC_API_KEYDirect Anthropic API calls — needs ANTHROPIC_API_KEY with API credits.
configCLAUDE_CODE_SESSION
configCLAUDE_AGENT_MODE
configATTUNE_ALLOW_PLACEHOLDER_TESTS
configEPIC_FHIR_BASE_URL
configEPIC_CLIENT_ID
🔐 secretEPIC_CLIENT_SECRET
configEPIC_OAUTH_TOKEN_URL
configSLACK_WEBHOOK_URL
configTWILIO_ACCOUNT_SID
🔐 secretTWILIO_AUTH_TOKEN
configTWILIO_FROM_NUMBER
configAMS_BASE_URL
configAMS_NAMESPACE
configCLAUDECODE
configATTUNE_OPS_SESSIONS_LLM
configATTUNE_PAYLOAD_CAPTURE_FILE
configGITHUB_STEP_SUMMARY
🔐 secretANTHROPIC_ADMIN_API_KEY
configATTUNE_MEMORY_REFS_V2
configEDITOR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployNEXT_PUBLIC_SITE_URL
deployREDIS_URL
deploySMTP_HOST
deploySMTP_PORT
deploySMTP_USER
deploySMTP_PASSWORD
deploySMTP_FROM
// 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

2/2 tools missing one or more hints — _handle_call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_1625 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Tool test coverage

1/2 tools referenced in tests (50%)

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

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

2 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Secrets stay with their owner

3 secrets sent to a request target we could not resolve (MAILCHIMP_API_KEY → dynamic, MAILCHIMP_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

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

Secrets not logged

2 secret values sent to log/error

Redact or omit secret values from log output.

Domain consistency

npm scope @attune doesn't match GitHub owner smart-ai-memory

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 8 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/smart-ai-memory/attune-ai?variant=verified)](https://m8ven.ai/mcp/smart-ai-memory/attune-ai)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f0767a6fceaece0d37be0f73005fbbdfb2b96c89
code hash: b71544a868cc6146fd0f2254ddab982403db942a00ab15a7c64a19b779e8bb9c
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