agent-harness-kit (enmanuelmag/agent-harness-kit) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 36 tools. No publisher has claimed this listing.
A provider-agnostic scaffolding kit for running structured multi-agent workflows in your codebase.
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
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
enmanuelmag
Source: github_repo_search
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 →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
specs.listList specification headers from docs/specs without loading bodies.
specs.getRead one specification body by slug with an explicit offset and limit.
specs.relatedList related specification headers and edges without their bodies.
specs.createCreate a validated specification in docs/specs from structured fields.
specs.update_metadataUpdate validated metadata fields without hand-editing frontmatter.
specs.update_contentReplace a specification body while preserving its validated frontmatter.
specs.transitionChange a specification status while enforcing source approval rules.
specs.linkCreate a bidirectional validated relationship between two specifications.
specs.unlinkRemove a relationship and its inverse from two specifications.
specs.validateValidate all docs/specs frontmatter, links, and source references.
actions.startStart a new action for a task. Returns an actionId.
actions.writeRecord a section in an action. Standard sections: result, tools_used, blockers, next_steps.
actions.completeClose an action with a one-line summary.
actions.getFull task action history, including every action and section. Potentially large; use only for audit or diagnosis.
actions.listCompact newest-first action index. Use to discover actions before reading a specific action or section.
actions.get_by_idGet one action and a compact index of its sections; section contents are not included.
actions.sections.listCompact newest-first section index for one action. Filter by section types without loading content.
actions.sections.getRead one section content with an explicit character range. This is the only generic action reader that returns long text.
actions.handoff.writeWrite a validated, recipient-directed, bounded handoff for a completed action to resume work without loading the full history.
actions.handoff.getGet the newest completed canonical handoff addressed to a recipient. Returns HANDOFF_NOT_FOUND instead of falling back to history.
tasks.getList tasks, optionally filtered by status. Excludes archived tasks by default.
tasks.claimAtomically claim a pending task. Returns task_already_claimed if another agent got it first.
tasks.updateChange the status of a task.
docs.searchSearch the project docs folder for content matching a query.
actions.record_fileRecord one or more files touched during an action, atomically (all-or-nothing). This is the only way to populate the files-touched count shown in the dashboard. Batch every file from a step of work into a single call — a single-element array is correct when only one file was touched.
tasks.acceptance.updateMark an acceptance criterion as met. Use the criterion id from tasks.get.
tasks.acceptance.getGiven a taskId, returns all acceptance criteria for that task with their id, task_id, criterion text, and met status. Use the returned id values to call tasks.acceptance_update(criterionId).
tasks.addCreate a new task in the harness. Use this when the user describes work in natural language. Infer slug, title, description, and acceptance criteria from the conversation. Ask for missing critical info before calling.
actions.record_toolRecord one or more tool calls made during an action, atomically (all-or-nothing). This is the only way to populate the Tools dashboard. Batch every tool call from a step of work into a single call — a single-element array is correct when only one call was made.
tasks.editEdit an existing task (title, description, acceptance criteria). Omitted fields keep their current values.
tasks.archiveArchive a task. Archived tasks are hidden from default views (CLI and dashboard).
tasks.unarchiveUnarchive a previously archived task, restoring it to default views.
permissions.checkCheck that a .claude/agents/*.md definition file exists for every role. Returns { in_sync, agents } where each agent is { ok } or { ok: false, reason: "missing_file" }. Agent file CONTENTS are never inspected — they are meant to be customised freely — so this never reports drift, only absence. Run `…
deps.snapshotSnapshot current package.json dependencies to .harness/deps-lock.json
deps.checkCompare current package.json against .harness/deps-lock.json and report changes
ahk.doctorCheck lib version, agent files, and harness skills sync status. Returns structured JSON.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@hono/node-server has authorization bypass for protected static paths via encoded slashes in Serve Static Middleware
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
Hono JWK Auth Middleware has JWT algorithm confusion when JWK lacks "alg" (untrusted header.alg fallback)
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
36/36 tools missing one or more hints — specs.list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); specs.get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); specs.related (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +33 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
12/36 tools referenced in tests (33%)
Write tests that reference each tool by name so every tool has at least one test.
Production dependencies are patched
0 critical, 8 high severity in production deps — @hono/node-server@1.13.0 (high), @modelcontextprotocol/sdk@1.10.2 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dependency freshness
1/15 production deps stale: cli-table3@2024-05-12 (2.3y)
Domain consistency
npm scope @cardor doesn't match GitHub owner enmanuelmag
Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.
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.
[](https://m8ven.ai/mcp/enmanuelmag/agent-harness-kit)?variant=verified from the URL.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