io.github.liminalpepe/agent-guard-mcp

NPM · @LIMINALLABLIBS/AGENT-GUARD-MCP · SCANNED AUG 3

Verify-before-act safety checks for AI agents: packages, lockfiles, manifests, CI workflows.

Available components

npm · @liminallablibs/agent-guard-mcp 63

+20 this week 63 63 Trust /100

Trust breakdown (6 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 →

Supply Chain Security86

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

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 32 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability70

AI-judged instruction clarity (excellent).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 Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

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

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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @liminallablibs/agent-guard-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add liminalpepe-agent-guard-mcp -- npx -y @liminallablibs/agent-guard-mcp

# add to Codex CLI

codex mcp add liminalpepe-agent-guard-mcp -- npx -y @liminallablibs/agent-guard-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "liminalpepe-agent-guard-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@liminallablibs/agent-guard-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add liminalpepe-agent-guard-mcp --command npx --arg -y --arg @liminallablibs/agent-guard-mcp

# ~/.hermes/config.yaml

mcp_servers:
  liminalpepe-agent-guard-mcp:
    command: "npx"
    args: ["-y", "@liminallablibs/agent-guard-mcp"]

// mcp.json

{
  "mcpServers": {
    "liminalpepe-agent-guard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@liminallablibs/agent-guard-mcp"
      ]
    }
  }
}

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.

2 Aug 26 +40
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 43

First indexed and scored.

Show 2 earlier entries Hide earlier entries

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 3 Aug 2026 · Analysed npm/@liminallablibs/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 4 exposed · ~668 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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug