Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agent Runtime Proof

MCPB · AGENT-RUNTIME-PROOF_1.1.0.MCPB

Verify whether a local Agent or MCP runtime matches an approved artifact.

−3 this week 61 Trust /100

Last scanned (40 minutes ago)

Scores higher than 95% of MCPB servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to fantasyce/agent-runtime-proof). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 70 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 328 tokens (~109/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed mcpb/https://github.com/fantasyce/agent-runtime-proof/releases/download/v1.1.0/agent-runtime-proof_1.1.0.mcpb@1.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem mcpb
Reason Verified
Discovered via GitHub artifact attestations
Source repo fantasyce/agent-runtime-proof
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/fantasyce/agent-runtime-proof/.github/workflows/release.yml@refs/tags/v1.1.0
Rekor log index 2613021810
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:420112637853aecf0a3bb3dcb7a5accf3e07ed88c34a9e29d8491262ee8db9a8

Background: How many MCP packages publish verified provenance →

MCP tools · 3 exposed · ~328 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
inspect_local_runtimes ~106

Use this when you have an explicit local PID, host binding, or bounded current-user inventory and need observation Proofs. Do not use it to claim an approved artifact match; use verify_local_runtime with an expectation for that decision.

NameTypeReqDescription
allboolean–inspect a bounded current-user inventory
binding_idstring–optional host binding identifier
limitinteger–inventory limit when all is true
pidinteger–positive local process identifier
NameTypeReqDescription
proofsnull|arrayyes–

No examples provided.

list_local_runtime_candidates ~93

Use this when the local PID or host binding is unknown and you need bounded, safe candidate summaries without artifact hashing. Do not use it to claim that a runtime matches an approved artifact or to request an exhaustive system inventory.

NameTypeReqDescription
binding_idstring–optional host binding identifier
host_idstring–optional host profile identifier
limitinteger–maximum number of current-user processes to inspect
NameTypeReqDescription
candidatesnull|arrayyes–

No examples provided.

verify_local_runtime ~129

Use this when you need to verify an explicit local PID or host binding against one declared local artifact expectation. Do not use it without an expectation, for remote processes, or to modify, stop, repair, or upgrade a runtime.

NameTypeReqDescription
binding_idstring–optional host binding identifier
expectationnull|object–inline expectation with absolute or home-relative roots
expectation_pathstring–local expectation JSON file
known_prior_digestsnull|array–directly known prior artifact SHA-256 values
pidinteger–optional positive local process identifier
NameTypeReqDescription
proofobjectyes–

No examples provided.

Install

How do I install the Agent Runtime Proof MCP server?

Agent Runtime Proof ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

mcpb · agent-runtime-proof_1.1.0.mcpb

Download bundle

The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.

Common questions

What is the Agent Runtime Proof MCP server?

Agent Runtime Proof is an MCP server listed in the public MCP registry as io.github.fantasyce/agent-runtime-proof. Verify whether a local Agent or MCP runtime matches an approved artifact. This page covers its MCPB bundle (https://github.com/fantasyce/agent-runtime-proof/releases/download/v1.1.0/agent-runtime-proof_1.1.0.mcpb).

Is the Agent Runtime Proof MCP server safe to use?

Agent Runtime Proof scores 61 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Agent Runtime Proof MCP server expose?

Agent Runtime Proof exposes 3 tools: inspect_local_runtimes, list_local_runtime_candidates, verify_local_runtime. Their descriptions and schemas cost roughly 328 tokens of context every time the server is loaded.

What licence is the Agent Runtime Proof MCP server under?

Agent Runtime Proof declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.