Bragproof

← Reports

@martinloop/mcp

Starts with no setup0.9.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 1 of 5 tools tried
Contacts while installing and starting: nothing

24tools listed
0hosts contacted
0files written
0.2 sto start
98dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y -p @martinloop/mcp@0.9.0 mcp

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 1 returned a result.

martin_statusNo usable answer tool reported an error: Tool error: Provide exactly one of loopJson, file, loopId, or latest. Suggestion: Choose exactly one status selector per call.
martin_list_runsReturned a result under 0.1 s · 413 characters
martin_get_attemptNo usable answer tool reported an error: Tool error: Provide exactly one of file or loopId. Suggestion: Choose exactly one run selector per call.
martin_get_verification_resultsNo usable answer tool reported an error: Tool error: Provide exactly one of file or loopId. Suggestion: Choose exactly one run selector per call.
martin_pr_summaryNo usable answer tool reported an error: Tool error: Provide exactly one of file, loopId, or latest. Suggestion: Choose exactly one run selector per call.

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

martin_run objective, workingDirectory, engine, model, fallbackEngines, maxUsd, maxIterations, maxTokens, verifyTimeoutMs, providerExecutionTimeoutMs, verificationPlan, allowedPaths, deniedPaths, workspaceId, projectId
Execute a governed MartinLoop coding run after MCP workflow admission is satisfied. Use when the user has authorized implementation, bug fixing, tests, or refactoring and doctor/estimate/plan/preflight receipts match this task. Do not use for question-only diagnosis or when policy, budget, credentials, or scope still need consent. Next: read martin_dossier and verifier evidence.
martin_inspect file, runsDir
Summarise Martin Loop run records from a saved loop file or run-store directory.
martin_status loopJson, file, loopId, runsDir, latest
Read the current budget, cost, remaining limits, and stop pressure for one MartinLoop run. Provide exactly one selector: loopJson for an inline record, file for a saved record, loopId for a run-store ID, or latest for the newest run; runsDir only changes the run-store root. Use for a compact budget check. Do not use for full events or artifacts; use martin_get_run or martin_run_dossier instead.
martin_doctor workingDirectory, runsDir, engine
Read-only environment, engine, workspace, and run-store diagnostics for MartinLoop. Use first for software work, fresh installs, suspicious state, or before retries. Do not use as proof that a task is complete. Next: call martin_estimate or martin_triage_runs depending on whether this is new work or failed prior work.
martin_plan objective, workingDirectory, context, policyPack, verificationPlan, allowedPaths, deniedPaths, maxUsd, maxIterations, maxTokens, maxMinutes, maxFilesChanged, maxCommands
Read-only planning step that turns an objective into bounded scope, verifier proposal, policy pack, and risk recommendation. Use for authorized software changes before preflight/run. Do not use to mutate files or replace the verifier. Next: call martin_preflight with the chosen scope, budget, and verifier.
19 more tools
martin_preflight objective, workingDirectory, engine, model, context, policyPack, maxUsd, maxIterations, maxTokens, maxMinutes, maxFilesChanged, maxCommands, verificationPlan, allowedPaths, deniedPaths, workspaceId, projectId
Read-only validation of the exact run contract before execution or spend. Use after planning and before martin_run to check engine, verifier, path scope, and budget. Do not use as execution or completion proof. Next: call martin_run if allowed, otherwise resolve the reported blocker.
martin_logs file, loopId, runsDir, latest, limit
Read recent MartinLoop events, ledger entries, operator control receipts, and reconciled executor control-application records for a single run. Use to observe live or completed run activity, diagnose stuck or failed runs, or audit operator actions. Do not use to check run completion status — use martin_get_status instead. Do not use to retrieve verification evidence — use martin_get_verification_results instead. This tool only reads persisted run files and does not execute commands, modify state, or contact GitHub.
martin_pause file, loopId, runsDir, latest, reason
Request a durable cooperative pause for one active MartinLoop run. The executor applies it at the next safe attempt boundary; it does not suspend or kill an in-flight provider. Provide exactly one selector: file, loopId, or latest. Use martin_status to distinguish requested from applied state; use martin_cancel to abandon work or martin_continue to release the applied pause.
martin_cancel file, loopId, runsDir, latest, reason
Publish the canonical durable cancellation signal for one active MartinLoop run. The active executor polls this signal, aborts its provider, restores governed workspace state, and records terminal evidence. Use the tool when work must stop; publication is not application proof, so use martin_status to observe terminal state or martin_pause for a reversible safe-boundary hold.
martin_continue file, loopId, runsDir, latest, reason
Release the exact pending cooperative pause for one active MartinLoop run. Continue is bound to that pause and does not grant approval, widen safety policy, or resume a terminal approval escalation.
martin_list_runs runsDir, limit, status, lifecycleState, adapterId, model, updatedAfter
List recent Martin runs from the run store with lightweight filters for status, lifecycle, engine metadata, and recency.
martin_triage_runs runsDir, limit, status, lifecycleState, adapterId, model, updatedAfter, includeHealthy
Read-only prioritization of saved Martin runs that need attention. Use when the user says a prior attempt failed, asks what to fix next, or resumes an interrupted session. Do not use for a brand-new objective with no relevant run history. Next: inspect the selected run or dossier before retrying.
martin_get_run file, loopId, runsDir, latest
Load one Martin run and return its budget, cost, verification, artifact, and canonical path summary.
martin_get_attempt file, loopId, runsDir, attemptIndex
Load one Martin attempt summary with artifact directory references for a canonical run.
martin_get_verification_results file, loopId, runsDir
Load structured verification evidence for a MartinLoop run — verifier commands, pass/fail outcomes, and contradiction signals — from stored loop events and ledger entries. Use after a run completes to confirm whether automated verifiers passed before merging or promoting the result. Do not use to get a merge-readiness grade — use martin_eval for a scored grade with six check dimensions. Do not use for live run status — use martin_get_status instead. This tool only reads persisted run files and does not execute commands, modify state, or contact GitHub.
martin_run_dossier file, loopId, runsDir, latest
Read the full structured execution dossier for one MartinLoop run, including attempts, events, artifacts, verification, integrity, cost, and related discovery surfaces. Provide exactly one selector: file, loopId, or latest; runsDir changes the run-store root. Use for comprehensive evidence review. Do not use for a compact state check; use martin_get_run, or use martin_dossier when formatted sharing output is required.
martin_dossier file, loopId, runsDir, latest, format
Read a formatted evidence summary for one MartinLoop run. Provide exactly one selector: file, loopId, or latest; runsDir changes the run-store root. Set format to json, md, or github-pr; json is the default. Use after martin_run, before merge or release claims, or when sharing what happened. Do not use as a substitute for missing verifier evidence; use martin_run_dossier for the full structured record. Next: review verification results, retry, or hand off the receipt.
martin_eval file, loopId, runsDir, latest
Grade a MartinLoop run across six dimensions — task completion, verifier health, diff discipline, regression risk, security risk, and reviewability — and return a scored merge-readiness verdict. Use after a governed run completes to decide whether the result is safe to merge or promote. Use before martin_pr_summary or martin_create_pr to confirm the run is merge-ready. Do not use to retrieve raw verification command output — use martin_get_verification_results for that. Do not use to review an existing PR body — use martin_review_pr instead. This tool reads saved run evidence and inspects local git signals; it does not modify state or contact GitHub.
martin_pr_summary file, loopId, runsDir, latest, format
Generate a GitHub-ready pull-request title and Markdown body from a completed MartinLoop run dossier, including its verification grade and score. Use after a governed run completes when you need PR copy without creating the PR. Use martin_create_pr instead to actually open the PR on GitHub. Use martin_review_pr to evaluate an existing PR body against run evidence. Use martin_eval first if you need a merge-readiness grade before generating the PR body. This tool only reads saved run evidence and does not modify the repository or contact GitHub.
martin_create_pr file, loopId, runsDir, latest, format, title, base, execute
Create or preview a GitHub PR with a MartinLoop dossier body. Use execute=true to actually call gh.
martin_review_pr file, loopId, runsDir, latest, format, prBody
Review a PR body or draft against the MartinLoop run dossier and evaluation evidence, and return a verdict with specific findings. Use when you have an existing PR body and want to check whether it accurately represents the governed run evidence. Supply prBody to review a specific body string; omit it to evaluate the auto-generated dossier body. Do not use to generate a PR body from scratch — use martin_pr_summary instead. Do not use to open or create a PR — use martin_create_pr instead. This tool only reads saved run evidence and does not modify the repository or contact GitHub.
martin_estimate objective, engine, budgetUsd, fileScope, workingDirectory
Read-only cost, route, and pre-work burn estimate for a software objective. Use before planning/preflight when a change may spend agent time or exceed budget. Do not use for casual questions or as permission to execute. Next: call martin_plan if the estimate is acceptable, or ask for consent if budget/risk is high.
martin_arcade
Open the presentation-only MartinLoop Arcade when the host supports MCP Apps. The Arcade cannot change governed execution or evidence.
martin_arcade_status loopId
Read the read-only evidence projection used by the Arcade view. Provide loopId for one exact run or omit it to load the latest run. Use only for Arcade rendering; use martin_status for budget pressure or martin_run_dossier for full evidence. This tool reads persisted evidence and never changes run state.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=20.0.0
Sourcegithub.com/Keesan12/martin-loop
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-jqXVJEjCqwRv4wLP2cAjSr2eJZy9hmddTYkPoG99alZwQxKNex7W60TTcHbF0k/J+4oxuMrBq/hMLpbqtloQxA==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@martinloop/mcp.svg)](https://bragproof.smaverk.com/r/%40martinloop/mcp)

New version out? Ask for a fresh report.