Report 01M7HXJJTN4Y7ETBZ377P89C1G · checks-v2
Agent Strace MCP server: automated checks
What HostedMCP checked on 16 Nov 2026, 10:13 UTC. Every result links to the public source it came from, so you can check it yourself.
8 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 16 Nov 2026, 10:13 UTC
- Commit
- —
- Package
- agent-strace · 0.112.0
- Methodology
- checks-v2
What to fix for a higher score
2 checks can earn more points. The next scan runs within a week, or right after the repository changes.
- Build provenance (Sigstore attestation) up to +10 pts
Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - OpenSSF Scorecard up to +15 pts
Add the OpenSSF Scorecard action (
ossf/scorecard-action) to the repository and fix the weakest checks it lists, such as branch protection, pinned dependencies and token permissions.
Origin
20 / 20 points- PassSource repository linked and reachable10 pts
siddhant-k-code/agent-trace is public and reachable
github.com/siddhant-k-code/agent-trace ↗ - PassPackage names this repository as its source5 pts
agent-strace name siddhant-k-code/agent-trace as source
pypi.org/project/agent-strace/ ↗ - Not checkedBuild provenance (Sigstore attestation)10 pts
No build attestation published for this release
How to fix: Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-11-16
github.com/siddhant-k-code/agent-trace ↗ - Not checkedOpenSSF Scorecard15 pts
How to fix: Add the OpenSSF Scorecard action (
ossf/scorecard-action) to the repository and fix the weakest checks it lists, such as branch protection, pinned dependencies and token permissions.
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from agent-strace
- PassNo critical advisory in the package or its dependencies15 pts
the package checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
8 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- PassDestructive tools are labelled5 pts
No tool named like delete, drop or exec
Endpoint
not checked- Not checkedRemote endpoint answers the MCP handshake5 pts
Starting the package
Listed its toolsWe installed agent-strace 0.112.0 in an isolated container that could reach only the package registry, started it with no network and no credentials, and asked for its tools on 16 Nov 2026.
It answered and listed its tools without any credentials. The list is below.
Tool definitions
Read by starting the package in an isolated container with no network and no credentials. Each new release is read again, and a definition that changes shows up here with the versions.
- Tools now
- 8
- Tracked since
- 16 Nov 2026
- Changes since then
- 1
- Version
- 0.111.1
16 Nov 2026ChangedreviewinputSchema0.111.0 → 0.111.1Show diffHide
inputSchema, before and after− { "properties": { "branch": { "default": "", "description": "Branch to link sessions by. Defaults to the CI source branch or the git branch of the server's working directory.", "type": "string" }, "commits": { "default": "", "description": "Git revision range to read Entire-Checkpoint and Agent-Logs-Url trailers from, such as origin/main..HEAD. Reported, not graded.", "type": "string" }, "config": { "default": "", "description": "Config file with a review block. Defaults to .agent-strace.yaml in the server's working directory if present.", "type": "string" }, "fail_on": { "description": "Comma-separated statuses that fail: missing, partial, inconclusive, or none (default: missing, or the config file).", "type": "string" }, "findings": { "description": "Comma-separated findings the threshold applies to: rationale, scope, validation, stewardship, evidence (default: all).", "type": "string" }, "format": { "default": "json", "description": "json (default) or markdown, same as the CLI formats.", "enum": [ "json", "markdown" ], "type": "string" }, "min_confidence": { "description": "Lowest confidence that can fail the check (default: medium).", "enum": [ "low", "medium", "high" ], "type": "string" }, "otel_logs": { "default": "", "description": "Path to a Claude Code OpenTelemetry logs export (OTLP JSON or JSON Lines) to read safety_event from. Relative paths resolve against the server's working directory. Reported, not graded.", "type": "string" }, "session_ids": { "default": [], "description": "Session IDs or prefixes to review (explicit link). Empty links sessions by branch, then head commit time, then latest.", "items": { "type": "string" }, "type": "array" } }, "type": "object" }+ { "properties": { "branch": { "default": "", "description": "Branch to link sessions by. Defaults to the CI source branch or the git branch of the server's working directory.", "type": "string" }, "commits": { "default": "", "description": "Git revision range to read Entire-Checkpoint and Agent-Logs-Url trailers and Copilot cloud agent authors and co-authors from, such as origin/main..HEAD. Reported, not graded.", "type": "string" }, "config": { "default": "", "description": "Config file with a review block. Defaults to .agent-strace.yaml in the server's working directory if present.", "type": "string" }, "fail_on": { "description": "Comma-separated statuses that fail: missing, partial, inconclusive, or none (default: missing, or the config file).", "type": "string" }, "findings": { "description": "Comma-separated findings the threshold applies to: rationale, scope, validation, stewardship, evidence (default: all).", "type": "string" }, "format": { "default": "json", "description": "json (default) or markdown, same as the CLI formats.", "enum": [ "json", "markdown" ], "type": "string" }, "min_confidence": { "description": "Lowest confidence that can fail the check (default: medium).", "enum": [ "low", "medium", "high" ], "type": "string" }, "otel_logs": { "default": "", "description": "Path to a Claude Code OpenTelemetry logs export (OTLP JSON or JSON Lines) to read safety_event from. Relative paths resolve against the server's working directory. Reported, not graded.", "type": "string" }, "session_ids": { "default": [], "description": "Session IDs or prefixes to review (explicit link). Empty links sessions by branch, then head commit time, then latest.", "items": { "type": "string" }, "type": "array" } }, "type": "object" }- 16 Nov 2026First read8 tools recorded as the baseline
Remote servers are read when they answer without sign-in or with a token from the maintainer; packages are started in an isolated container. Definitions are third-party text, shown as written.
What these checks do not cover
- Tools are listed but never called, and the server's logic is not audited.
- Results describe the repository and package on the date above; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.