Archon (matthewkaya/Archon) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 27 tools. No publisher has claimed this listing.

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

Archon

→ matthewkaya/Archon· listed on github_code

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

matthewkaya

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
✅
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 5 credentials: GH_TOKEN, GITHUB_TOKEN, SUPABASE_SERVICE_KEY, OPENAI_API_KEY, LOGFIRE_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.
configARCHON_SERVER_PORTFor custom ports, ensure both and VITE_ARCHON_SERVER_PORT are set
configARCHON_UI_PORT
configDOCKER_ENV
configHOSTBy default, Archon uses localhost as the hostname. You can configure a custom hostname or IP address by setting the variable in your .env file:
configAGENT_WORK_ORDERS_PORT
configSERVICE_DISCOVERY_MODE
configARCHON_SERVER_URL
configARCHON_MCP_URL
configCORS_ORIGINS
🔐 secretGH_TOKEN
🔐 secretGITHUB_TOKEN
configSUPABASE_URLFor local Supabase: Set to http://host.docker.internal:8000 (unless you have an IP address set up). To get SUPABASE_SERVICE_KEY run supabase status -o env.
configMCP_SERVICE_URL
configARCHON_AGENTS_PORT
configARCHON_MCP_PORT
configDOCKER_CONTAINER
configARCHON_HOST
configMCP_REQUEST_TIMEOUT
configMCP_CONNECT_TIMEOUT
configMCP_READ_TIMEOUT
configMCP_WRITE_TIMEOUT
configMCP_POLLING_TIMEOUT
configMCP_POLLING_READ_TIMEOUT
configMCP_MAX_POLLING_ATTEMPTS
configMCP_POLLING_BASE_INTERVAL
configMCP_POLLING_MAX_INTERVAL
configENABLE_AGENT_WORK_ORDERS
configCLAUDE_CLI_PATH
configAGENT_WORK_ORDER_TIMEOUT
configAGENT_WORK_ORDER_COMMANDS_DIR
configAGENT_WORK_ORDER_TEMP_DIR
configLOG_LEVEL
configGH_CLI_PATH
configCLAUDE_CLI_VERBOSE
configCLAUDE_CLI_MAX_TURNS
configCLAUDE_CLI_MODEL
configCLAUDE_CLI_SKIP_PERMISSIONS
configENABLE_PROMPT_LOGGING
configENABLE_OUTPUT_ARTIFACTS
configWORKTREE_BASE_DIR
configBACKEND_PORT_START
configBACKEND_PORT_END
configFRONTEND_PORT_START
configFRONTEND_PORT_END
configSTATE_STORAGE_TYPE
configFILE_STATE_DIRECTORY
configDOCUMENT_AGENT_MODEL
configRAG_AGENT_MODEL
🔐 secretSUPABASE_SERVICE_KEYFor local Supabase: Set SUPABASE_URL to http://host.docker.internal:8000 (unless you have an IP address set up). To get run supabase status -o env.
configGITHUB_REPO
🔐 secretOPENAI_API_KEY
configTRANSPORT
configUSE_CONTEXTUAL_EMBEDDINGS
configUSE_HYBRID_SEARCH
configUSE_AGENTIC_RAG
configUSE_RERANKING
configENABLE_DOCKER_SOCKET_MONITORING
configMCP_HEALTH_CHECK_TIMEOUT
configLOGFIRE_ENABLED
🔐 secretLOGFIRE_TOKEN
configLLM_PROVIDER
configMODEL_CHOICE
configRERANKING_MODEL
configRERANKING_TOP_K
configCONTEXTUAL_EMBEDDINGS_MAX_WORKERS
configCODE_SUMMARY_MAX_WORKERS
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

27/27 tools missing one or more hints — health_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); session_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_project_features (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 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 test coverage

15/27 tools referenced in tests (56%)

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

Shell command execution

3 calls in production code run through a shell (archon-ui-main/vite.config.ts:73, archon-ui-main/vite.config.ts:152, archon-ui-main/vite.config.ts:238)

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 4 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/matthewkaya/archon)](https://m8ven.ai/mcp/matthewkaya/archon)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ecaece460c1924e9a81a409aebee692146f8a301
code hash: 34be54c376425b4e21205a0b0e799015ab07763948ea2d50034e041e6e37ffe1
verified: 9/1/2026, 5:39:19 PM
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