template-repo (AndrewAltimit/template-repo) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 13 tools. No publisher has claimed this listing.

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

template-repo

Agent orchestration & security template featuring MCP tool building, agent2agent workflows, mechanistic interpretability on sleeper agents, and agent integration via CLI wrappers

→ AndrewAltimit/template-repo· listed on github_topic

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

⚡ 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

AndrewAltimit

Source: github_topic

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
🚨
Secret credentials may flow to a network call
1 flow detected: COMPANY_API_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: GPU_API_KEY, API_KEY, COMPANY_API_TOKEN, DASHBOARD_ADMIN_PASSWORD
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.
configOPENCODE_BIN_PATH
configOPENCODE_TUI_BINARY
configREMOTE_MCP_URL
configSERVICE_NAME
configTIMEOUT
configGPU_API_URL
🔐 secretGPU_API_KEY
🔐 secretAPI_KEY
configMAX_TEXT_LENGTH
configMAX_SAMPLES
configRATE_LIMIT_REQUESTS
configRATE_LIMIT_WINDOW
configMAX_CONCURRENT_REQUESTS
configCORS_ALLOWED_ORIGINS
configGEMINI_MAX_OUTPUT_SIZE
configAPI_MODE
configAPI_VERSION
configTOOL_API_SPEC
configHOST
configGAEA_OFFICIAL_PROJECTS_DIR
configGAEA_USER_PROJECTS_DIR
configCOMPANY_API_BASE
configUSE_MOCK_API
configGEMINI_PROXY_PORT
configDEFAULT_TOOL_MODE
configMAX_TOOL_ITERATIONS
configMOCK_API_BASE
configFLASK_DEBUG
🔐 secretCOMPANY_API_TOKEN
configAGENT_CLIENT
configPRODUCTION
configLOG_LEVEL
configMODEL_ID
configAWS_REGION
configAUTH_DATABASE_PATH
🔐 secretDASHBOARD_ADMIN_PASSWORD
configUSE_MOCK_DATA
configDATABASE_PATH
configEVAL_DB_PATH
configEVAL_RESULTS_DIR
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

13/13 tools missing one or more hints — write (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); view (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bash (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.

Tool test coverage

9/13 tools referenced in tests (69%)

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

Secrets stay with their owner

1 secret sent to a request target we could not resolve (COMPANY_API_TOKEN → 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

1 secret value sent to logger.error

Redact or omit secret values from log output.

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/andrewaltimit/template-repo)](https://m8ven.ai/mcp/andrewaltimit/template-repo)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 95258cb42aa85924f4ec0820aa00e689ba2d5511
code hash: 353f7ea5cd2ff3cf882d6e22bd472197b4b96cee19a82c89d37b436704b7d468
verified: 9/2/2026, 11:32:02 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