ATMcp (MidCheck/ATMcp) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 29 tools. No publisher has claimed this listing.

C
Limited view
69/100

ATMcp

Enables multiple LLM agents across devices to form teams, share knowledge, memory, and tasks with live status via a web dashboard and distributed-systems reliability.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

MidCheck

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

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
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: ATMCP_TOKEN, ATMCP_API_KEY, ATMCP_ADMIN_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.
configATMCP_MCP_DNS_REBINDING
configATMCP_TEAM
🔐 secretATMCP_TOKEN
configATMCP_NAME
configATMCP_URL
configATMCP_MODEL
configATMCP_EXECUTOR
configATMCP_EXECUTOR_CMD
configATMCP_BASE_REPO
configATMCP_STATE_DIR
configATMCP_ALLOWED
configATMCP_PERMISSION_MODE
configATMCP_CLAUDE_ARGS
configATMCP_MAX_CONCURRENT
configATMCP_API_BASE
🔐 secretATMCP_API_KEY
configATMCP_MAX_STEPS
configATMCP_TOOL_TIMEOUT
configATMCP_OPENAI_TIMEOUT
configATMCP_WORKDIR
configATMCP_RESUME_SESSION
configATMCP_COST_BUDGET
configATMCP_TOKEN_BUDGET
configATMCP_MAX_RETRIES
configATMCP_RETRY_BACKOFF
🔐 secretATMCP_ADMIN_TOKENcp .env.example .env # set
configATMCP_SQLITE_PATHSee .env.example. Highlights: ATMCP_ADMIN_TOKEN, , ATMCP_REDIS_URL,
configATMCP_REDIS_URLSee .env.example. Highlights: ATMCP_ADMIN_TOKEN, ATMCP_SQLITE_PATH, ,
configATMCP_PUBLIC_URL, heartbeat TTL/interval (30/10s), lease TTL (90s), reaper interval
// 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

29/29 tools missing one or more hints — join_team (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); leave_team (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); heartbeat (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 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.

Tool inputs are validated

26/29 tool handlers declare input schemas (90%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 1/29 tool handlers wrap calls in try/catch (3%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 5 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/midcheck/atmcp)](https://m8ven.ai/mcp/midcheck/atmcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 204371d41e6f4e3b4751a6844a7b9fe3d7b80624
code hash: 690b47c54adc715a881104791fdf107da5a333f6ba42dd5b4930a3c159831313
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