awesome-harness-primitives (paulasilvatech/awesome-harness-primitives) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 85 tools. No publisher has claimed this listing.

Emerging

74/100

8 days ago

awesome-harness-primitives

Item: awesome-harness-primitives
Rating: 74
Author: M8ven

→ paulasilvatech/awesome-harness-primitives · 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

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

paulasilvatech

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, NAMECHEAP_API_KEY, OPENROUTER_API_KEY, MSSQL_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.

configCOPILOT_AGENT_SESSION_ID

configCOPILOT_CLI_PATH

configCOPILOT_HOME

configCOPILOT_WORKSPACE_BRANCH

🔐 secretGH_TOKEN

configGITHUB_REPOSITORY

🔐 secretGITHUB_TOKEN

configSESSION_ID

configSystemRoot

configWEBMCP_BASE_URL

configWINDIR

configWORKSHOP_DESK_AGENT

configWORKSHOP_DESK_PROFILE

configWORKSHOP_LOCAL_DELEGATION_PREFERENCE

configPLAYWRIGHT_BROWSERS_PATH

configMINI_CONTEXT_GRAPH_DATA_DIR

configMINI_CONTEXT_GRAPH_WIKI_DIR

configATTESTER_BASE_URL

configATTESTER_IMPORT_CHECK_NO_CACHE

configATTESTER_MODE

configNAMECHEAP_API_USER

🔐 secretNAMECHEAP_API_KEY

configBACKSTAGE_EXPERT_HOOK_MODE

configOPEN_HORIZONS_HOOK_MODE

configMINI_CONTEXT_GRAPH_BASE

configWORKSPACE_KIT_PACKAGE_ROOT

🔐 secretOPENROUTER_API_KEY

configSKILL_ROOT

configRHDH_LOCAL_SETUP_DIR

configMSSQL_USER

🔐 secretMSSQL_PASSWORD

// 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

85/85 tools missing one or more hints — get_state (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); move_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); refresh_issues (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +82 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

Only 6/85 tools referenced in tests (7%)

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

No eval / new Function

2 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

1 call in production code run through a shell (harness/claude-code/plugins/site-studio/extensions/site-studio/extension.mjs:411)

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 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/paulasilvatech/awesome-harness-primitives)](https://m8ven.ai/mcp/paulasilvatech/awesome-harness-primitives)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: 123973e46be6d60c60b4b7d3a0599a7ab36e53eb

code hash: 22f20f3cd86ba4eb3130b54bc33868da552ab907dcafcf48fc005cefbc13aa80

verified: 9/2/2026, 6:49:58 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