io.github.liminalpepe/agent-guard-mcp
NPM · @LIMINALLABLIBS/AGENT-GUARD-MCP · SCANNED SEP 20
Verify-before-act safety checks for AI agents: packages, lockfiles, manifests, CI workflows.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 80 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 668 tokens (~167/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.liminalpepe/agent-guard-mcp server?
io.github.liminalpepe/agent-guard-mcp runs locally as an npm package, launched with npx -y @liminallablibs/agent-guard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @liminallablibs/agent-guard-mcp
claude mcp add liminalpepe-agent-guard-mcp -- npx -y @liminallablibs/agent-guard-mcp
{
"mcpServers": {
"liminalpepe-agent-guard-mcp": {
"command": "npx",
"args": [
"-y",
"@liminallablibs/agent-guard-mcp"
]
}
}
} {
"servers": {
"liminalpepe-agent-guard-mcp": {
"command": "npx",
"args": [
"-y",
"@liminallablibs/agent-guard-mcp"
]
}
}
} codex mcp add liminalpepe-agent-guard-mcp -- npx -y @liminallablibs/agent-guard-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"liminalpepe-agent-guard-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@liminallablibs/agent-guard-mcp"
],
"enabled": true
}
}
} openclaw mcp add liminalpepe-agent-guard-mcp --command npx --arg -y --arg @liminallablibs/agent-guard-mcp
mcp_servers:
liminalpepe-agent-guard-mcp:
command: "npx"
args: ["-y", "@liminallablibs/agent-guard-mcp"] {
"McpServers": {
"liminalpepe-agent-guard-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@liminallablibs/agent-guard-mcp"
]
}
}
} assistant mcp add liminalpepe-agent-guard-mcp -t stdio -c npx -a -y @liminallablibs/agent-guard-mcp
{
"mcpServers": {
"liminalpepe-agent-guard-mcp": {
"command": "npx",
"args": [
"-y",
"@liminallablibs/agent-guard-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.
- 18 Sept 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.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 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.
- 11 Sept 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.
- 9 Sept 26 −2
- Stability: pass → 0.80 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 7 Sept 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.
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 20 Sept 2026 · Analysed npm/@liminallablibs/agent-guard-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
check_package ~155
Pre-install supply-chain gate for a single npm or PyPI package. Call BEFORE running npm install, pip install, or adding a dependency to package.json. Returns OK | SUSPICIOUS | DANGER (DANGER ~= NO-GO) with typosquat/slopsquat/hallucination flags. Read-only: queries public registries only; does not install anything. Do NOT use for full lockfile audits (use verify_lockfile) or CVE-only scans (use npm audit/OSV). If verdict is SUSPICIOUS or DANGER, stop and ask the user before installing.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | – |
| name | string | yes | Package name, e.g. "huggingface-cli". |
No output schema declared.
No examples provided.
check_workflow ~151
Validate CI workflow YAML (GitHub Actions / GitLab CI) BEFORE merging a PR that touches .github/workflows or GitLab CI. Call when reviewing or authoring CI pipelines. Flags mutable action pins (@v1), known-compromised actions, untrusted owners, curl|bash fetch-exec, pull_request_target pwn-request patterns, and secret exposure. Returns risk 0-100 and PROCEED | REVIEW | BLOCK. Read-only. Do NOT use for dependency lockfiles (use verify_lockfile). Default platform: github-actions. CI-workflow coverage is unique to agent-guard.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | – |
| workflow_content | string | yes | Raw CI workflow YAML text. |
No output schema declared.
No examples provided.
score_manifest ~206
Score a third-party AI-agent extension manifest (skill/plugin manifest audit) BEFORE install. Call BEFORE installing a Cursor skill, Claude skill, MCP server package, or Smithery plugin. Detects poison/backdoor signatures, credential scope over-reach, and drift vs an approved baseline. Returns risk 0-100 and PROCEED | REVIEW | BLOCK. Supports manifest_type: cursor-skill | claude-skill | mcp-server | smithery-package. Read-only. Do NOT use for npm package names alone (use check_package). If BLOCK, refuse install until the user reviews findings. This skill/plugin coverage is unique to agent-guard.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_manifest | string | – | Optional previously-approved manifest for drift scoring. |
| declared_purpose | string | – | One-line stated purpose (for scope-overreach heuristics). |
| manifest_content | string | yes | Primary manifest text (SKILL.md, plugin.json, smithery.yaml, package.json). |
| manifest_type | string | yes | – |
No output schema declared.
No examples provided.
verify_lockfile ~156
Scan an entire lockfile (direct + transitive deps) BEFORE npm/pip/yarn/pnpm install. Call when the user pastes or generates a lockfile, or before trusting an LLM-written package-lock.json / yarn.lock / pnpm-lock.yaml / poetry.lock / requirements.txt. Returns per-package OK | SUSPICIOUS | DANGER counts and flagged names. Read-only; pass raw file text, not a filesystem path. Do NOT use for a single new package (use check_package) or CI YAML (use check_workflow).
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Optional; inferred from format. |
| format | string | yes | – |
| lockfile_content | string | yes | Raw lockfile text (not a path). |
No output schema declared.
No examples provided.
What is the io.github.liminalpepe/agent-guard-mcp server?
io.github.liminalpepe/agent-guard-mcp is listed in the public MCP registry as io.github.liminalpepe/agent-guard-mcp. Verify-before-act safety checks for AI agents: packages, lockfiles, manifests, CI workflows. This page covers its npm package (@liminallablibs/agent-guard-mcp).
Is the io.github.liminalpepe/agent-guard-mcp server safe to use?
io.github.liminalpepe/agent-guard-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.liminalpepe/agent-guard-mcp server expose?
io.github.liminalpepe/agent-guard-mcp exposes 4 tools: check_package, verify_lockfile, score_manifest, check_workflow. Their descriptions and schemas cost roughly 668 tokens of context every time the server is loaded.
Is the io.github.liminalpepe/agent-guard-mcp server still maintained?
io.github.liminalpepe/agent-guard-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.liminalpepe/agent-guard-mcp server under?
io.github.liminalpepe/agent-guard-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.