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.

D
Caution
50/100

agent-harness-kit

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

⚡ 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

enmanuelmag

Source: github_repo_search

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 →

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.

// key findings
⚠️
Known vulnerabilities in dependencies: 8 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
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.
// tools this server exposes36 tools

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.list

List specification headers from docs/specs without loading bodies.

specs.get

Read one specification body by slug with an explicit offset and limit.

specs.related

List related specification headers and edges without their bodies.

specs.create

Create a validated specification in docs/specs from structured fields.

specs.update_metadata

Update validated metadata fields without hand-editing frontmatter.

specs.update_content

Replace a specification body while preserving its validated frontmatter.

specs.transition

Change a specification status while enforcing source approval rules.

specs.link

Create a bidirectional validated relationship between two specifications.

specs.unlink

Remove a relationship and its inverse from two specifications.

specs.validate

Validate all docs/specs frontmatter, links, and source references.

actions.start

Start a new action for a task. Returns an actionId.

actions.write

Record a section in an action. Standard sections: result, tools_used, blockers, next_steps.

actions.complete

Close an action with a one-line summary.

actions.get

Full task action history, including every action and section. Potentially large; use only for audit or diagnosis.

actions.list

Compact newest-first action index. Use to discover actions before reading a specific action or section.

actions.get_by_id

Get one action and a compact index of its sections; section contents are not included.

actions.sections.list

Compact newest-first section index for one action. Filter by section types without loading content.

actions.sections.get

Read one section content with an explicit character range. This is the only generic action reader that returns long text.

actions.handoff.write

Write a validated, recipient-directed, bounded handoff for a completed action to resume work without loading the full history.

actions.handoff.get

Get the newest completed canonical handoff addressed to a recipient. Returns HANDOFF_NOT_FOUND instead of falling back to history.

tasks.get

List tasks, optionally filtered by status. Excludes archived tasks by default.

tasks.claim

Atomically claim a pending task. Returns task_already_claimed if another agent got it first.

tasks.update

Change the status of a task.

docs.search

Search the project docs folder for content matching a query.

actions.record_file

Record 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.update

Mark an acceptance criterion as met. Use the criterion id from tasks.get.

tasks.acceptance.get

Given 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.add

Create 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_tool

Record 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.edit

Edit an existing task (title, description, acceptance criteria). Omitted fields keep their current values.

tasks.archive

Archive a task. Archived tasks are hidden from default views (CLI and dashboard).

tasks.unarchive

Unarchive a previously archived task, restoring it to default views.

permissions.check

Check 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.snapshot

Snapshot current package.json dependencies to .harness/deps-lock.json

deps.check

Compare current package.json against .harness/deps-lock.json and report changes

ahk.doctor

Check lib version, agent files, and harness skills sync status. Returns structured JSON.

// known CVEs in dependencies8 high22 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@hono/node-server@1.13.0GHSA-wc8c-qw6v-h7f6

@hono/node-server has authorization bypass for protected static paths via encoded slashes in Serve Static Middleware

high@modelcontextprotocol/sdk@1.10.2GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.10.2GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.10.2GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highhono@4.6.0GHSA-3vhc-576x-3qv4

Hono JWK Auth Middleware has JWT algorithm confusion when JWK lacks "alg" (untrusted header.alg fallback)

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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

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.

// 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 Verified](https://m8ven.ai/badge/mcp/enmanuelmag/agent-harness-kit?variant=verified)](https://m8ven.ai/mcp/enmanuelmag/agent-harness-kit)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b9d71c17592645b878f2c680db9e16030bf99c92
code hash: 53f5cb8f255c77178d346ecea08c31ebdaea0275eba1ca58fb6813f0ea12fec7
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