set-agent-comm (tatargabor/set-agent-comm) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 6 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
6 days ago

set-agent-comm

Enables local agent-to-agent messaging between Claude Code sessions via file-based channels, with a registry, MCP tools and CLI for sending, reading, and tracking messages.

→ tatargabor/set-agent-comm· 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

tatargabor

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

Glama

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

// 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 1 credential: RELAY_SECRET
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.
configCLAUDE_CODE_SESSION_IDitself. The id comes from , which the MCP server process, the
configCLAUDE_PROJECT_DIR
configMCP_HOST
configMCP_PORT
configRELAY_DEVICE_TTL_DAYSWhat the device gets is a token good for 365 days () — long enough
configRELAY_HOSTonly variable you have to set. (default 0.0.0.0) binds the listener: set it to
configRELAY_LIMIT_JOINper minute: 10 joins per IP, 120 posts and 60 polls per device token (RELAY_LIMIT_JOIN / _POST / _POLL), answered with 429 and a retry-after. A long poll is one request for its whole 25 seconds, so a normal participant never comes near it
configRELAY_LIMIT_POLL
configRELAY_LIMIT_POST
configRELAY_MAX_ROOM_ENTRIES5000 entries and 64 MB per room (RELAY_MAX_ROOM_ENTRIES, RELAY_MAX_ROOM_MB), oldest first. Time-based retention alone is not a ceiling: at the post limit one valid token is half a gigabyte a minute, and this is all in memory
configRELAY_MAX_ROOM_MB5000 entries and 64 MB per room (RELAY_MAX_ROOM_ENTRIES, RELAY_MAX_ROOM_MB), oldest first. Time-based retention alone is not a ceiling: at the post limit one valid token is half a gigabyte a minute, and this is all in memory
configRELAY_RETENTION_HOURSown. The rest — , RELAY_DEVICE_TTL_DAYS, the RELAY_LIMIT_ and
🔐 secretRELAY_SECRET7-day retention by default — it is a transport, not an archive. Tokens are HMAC-signed and stateless, so a single one cannot be revoked; rotating RELAY_SECRET invalidates all of them and everyone re-joins. And it sees metadata (who, when, how much) even though it cannot read a word
configSET_AGENT_BUSY_MS
configSET_AGENT_COMM_DIRtests point at a mkdtemp directory (nothing touches your real bus); they
configSET_AGENT_DEVICE
configSET_AGENT_HEADLESSreal session with no watch armed. =10 forces it.
configSET_AGENT_INBOX_CHARSmoves the line; 0 turns it off.
configSET_AGENT_LONG_CHARSfar worse failure than a verbose one. (default 1500) is where "long" starts.
configSET_AGENT_NAMEThe agent's name comes from the project's directory name (override with ).
configSET_AGENT_OWNER_PID
configSET_AGENT_QUIET_MS
configSET_AGENT_ROOMaccepts a comma-separated list (-e SET_AGENT_ROOM=team,design) when one
configSET_AGENT_SAFETY_NEToff removes it.
configSET_AGENT_TRIAGETurn it off with =off (which then always wakes), point it elsewhere with
configSET_AGENT_TRIAGE_BIN/ SET_AGENT_TRIAGE_MODEL.
configSET_AGENT_TRIAGE_MODELSET_AGENT_TRIAGE_BIN / .
configSET_AGENT_TRIAGE_TIMEOUT_MS
configSET_AGENT_WATCH_MAX_HOURS
configXDG_DATA_HOME
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

6/6 tools missing one or more hints — agents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); focus (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); rooms (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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.

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 2 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/tatargabor/set-agent-comm)](https://m8ven.ai/mcp/tatargabor/set-agent-comm)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 0417704eae4e561addd511cdc28135048036c30d
code hash: d4866507b1ce8c6fa1e7d2c1f58765a5554a02e1d2aea6c68cf6aaa65c611f2d
verified: 9/4/2026, 4:54:06 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