codex-inter-agent-messaging (omrijsharon/codex-inter-agent-messaging) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Caution
74/100
13 days ago

codex-inter-agent-messaging

→ omrijsharon/codex-inter-agent-messaging· listed on github_code

Caution. Specific findings reduced this grade. They are listed on the page. 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

omrijsharon

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

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

// key findings
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
✅
18 tools verified — handlers match their declared behaviour
4 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: PHASE0_APP_SERVER_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.
configBRIDGE_AGENT_IDunset Metadata-absent CLI fallback only
configBRIDGE_BOOTSTRAP_REASON
configBRIDGE_LAST_RECOVERY_RESULT
configPHASE0_AGENT_ID
configPHASE0_AGENT_REGISTRY
🔐 secretPHASE0_APP_SERVER_TOKEN
configPHASE0_APP_SERVER_URL
configPHASE0_BUSY_POLL_MS
configPHASE0_BUSY_WAIT_MS
// quality suggestions

Tool annotations

5/18 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

13/18 tools missing one or more hints — list_agents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ask_agent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_request_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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

14/18 tools referenced in tests (78%)

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

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (src/cli/main.ts:55)

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

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/omrijsharon-codex-inter-agent-messaging-4j3dg4?variant=verified)](https://m8ven.ai/mcp/omrijsharon-codex-inter-agent-messaging-4j3dg4)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0a6280e8ab58d64b862d25b2ff48f5f21395bbd8
code hash: 2060481b2635af65d06b95ace9b11cecc95f84c26a5b697aa1faea5abfcc2023
verified: 8/18/2026, 9:13:17 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