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.

LoopGrid MCP

PYPI · LOOPGRID-MCP

MCP bridge for tamper-evident evidence around consequential AI and agent decisions.

Available components

+15 this week 90 Trust /100

Last scanned (19 hours ago)

Scores higher than 90% of PyPI 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to loopgridio/loopgrid-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 62 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 468 tokens (~78/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 8 Nov 26 −1
    • Stability: pass → 0.87 functional
  • 7 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
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 21 Nov 2026 · Analysed pypi/loopgrid-mcp@0.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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo loopgridio/loopgrid-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/loopgridio/loopgrid-mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 2893167785
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:4dbd1dd0976f9484b77a5c579afdd3f1c5eb9c098ac3cb2db1d0af65c77bd492

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 31 packages
Packages resolved 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~468 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
loopgrid.get_evidence ~54

Download a portable LoopGrid evidence ZIP for a decision to the configured local evidence directory. Raw disclosure payloads are excluded by default.

NameTypeReqDescription
decision_idstringyes–
include_payloadsboolean––

Structured output declared, but exposes no named fields.

No examples provided.

loopgrid.record_action ~80

Record evidence that an external tool/action executed. This does NOT call Stripe, Salesforce, ServiceNow, or any other business system; it only records execution evidence supplied by the integration.

NameTypeReqDescription
actor_idstring––
decision_idstringyes–
details–––
external_reference–––
toolstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

loopgrid.record_decision ~137

Capture a consequential AI/agent decision in LoopGrid. Optionally record model output and evaluate an existing LoopGrid policy. This records evidence only and does not execute the proposed action.

NameTypeReqDescription
agent_idstring––
agent_version–––
authority–––
context–––
decision_typestringyes–
idempotency_key–––
input_data–––
metadata–––
model–––
model_output–––
policy_id–––
privacy_mode–––
proposed_actionobjectyes–
service_namestring––

Structured output declared, but exposes no named fields.

No examples provided.

loopgrid.record_outcome ~81

Record an observed downstream outcome for a decision after execution evidence exists. The integration is responsible for obtaining the outcome from the real downstream system.

NameTypeReqDescription
actor_idstring––
decision_idstringyes–
details–––
external_reference–––
statusstringyes–
verified_againststringyes–

Structured output declared, but exposes no named fields.

No examples provided.

loopgrid.record_review ~66

Record a human approve/reject review in LoopGrid. Disabled by default. The operator must explicitly enable it and configure reviewer identity; the MCP host should require human confirmation.

NameTypeReqDescription
actionstringyes–
decision_idstringyes–
reasonstring––

Structured output declared, but exposes no named fields.

No examples provided.

loopgrid.verify_evidence ~50

Ask the connected LoopGrid service to verify the decision's signed workspace chain. For independent offline verification of an exported ZIP, use the standalone LoopGrid verifier.

NameTypeReqDescription
decision_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the LoopGrid MCP server?

LoopGrid MCP runs locally as a PyPI package, launched with uvx loopgrid-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · loopgrid-mcp

# add to Claude Code
claude mcp add loopgridio-loopgrid-mcp -- uvx loopgrid-mcp
Common questions

What is the LoopGrid MCP server?

LoopGrid MCP is listed in the public MCP registry as io.github.loopgridio/loopgrid-mcp. MCP bridge for tamper-evident evidence around consequential AI and agent decisions. This page covers its PyPI package (loopgrid-mcp).

Is the LoopGrid MCP server safe to use?

LoopGrid MCP scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 LoopGrid MCP server expose?

LoopGrid MCP exposes 6 tools: loopgrid.record_decision, loopgrid.record_review, loopgrid.record_action, loopgrid.record_outcome, loopgrid.get_evidence, loopgrid.verify_evidence. Their descriptions and schemas cost roughly 468 tokens of context every time the server is loaded.

Is the LoopGrid MCP server still maintained?

LoopGrid MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the LoopGrid MCP server under?

LoopGrid MCP 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.

What did VerifyMCP test on the LoopGrid MCP server?

VerifyMCP ran 16 checks on LoopGrid MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.