LoopGrid MCP
PYPI · LOOPGRID-MCP · SCANNED SEP 21
MCP bridge for tamper-evident evidence around consequential AI and agent decisions.
Available components
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
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.
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
claude mcp add loopgridio-loopgrid-mcp -- uvx loopgrid-mcp
{
"mcpServers": {
"loopgridio-loopgrid-mcp": {
"command": "uvx",
"args": [
"loopgrid-mcp"
]
}
}
} {
"servers": {
"loopgridio-loopgrid-mcp": {
"command": "uvx",
"args": [
"loopgrid-mcp"
]
}
}
} codex mcp add loopgridio-loopgrid-mcp -- uvx loopgrid-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"loopgridio-loopgrid-mcp": {
"type": "local",
"command": [
"uvx",
"loopgrid-mcp"
],
"enabled": true
}
}
} openclaw mcp add loopgridio-loopgrid-mcp --command uvx --arg loopgrid-mcp
mcp_servers:
loopgridio-loopgrid-mcp:
command: "uvx"
args: ["loopgrid-mcp"] {
"McpServers": {
"loopgridio-loopgrid-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"loopgrid-mcp"
]
}
}
} assistant mcp add loopgridio-loopgrid-mcp -t stdio -c uvx -a loopgrid-mcp
{
"mcpServers": {
"loopgridio-loopgrid-mcp": {
"command": "uvx",
"args": [
"loopgrid-mcp"
]
}
}
} 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 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Sept 26 63
First indexed and scored.
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 Sept 2026 · Analysed pypi/loopgrid-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| include_payloads | boolean | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_id | string | – | – |
| decision_id | string | yes | – |
| details | – | – | – |
| external_reference | – | – | – |
| tool | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| agent_version | – | – | – |
| authority | – | – | – |
| context | – | – | – |
| decision_type | string | yes | – |
| idempotency_key | – | – | – |
| input_data | – | – | – |
| metadata | – | – | – |
| model | – | – | – |
| model_output | – | – | – |
| policy_id | – | – | – |
| privacy_mode | – | – | – |
| proposed_action | object | yes | – |
| service_name | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_id | string | – | – |
| decision_id | string | yes | – |
| details | – | – | – |
| external_reference | – | – | – |
| status | string | yes | – |
| verified_against | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| decision_id | string | yes | – |
| reason | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.