AgentShield MCP Inspector Lite
by Turkeyz1
README.md
# AgentShield MCP Inspector Lite
Free public edition of AgentShield for basic MCP tool-metadata security inspection.
**Publisher:** Mahmoud Hisham
**Edition:** Lite
**Version:** 0.1.0-lite.1
**Runtime:** Node.js 20+
## What Lite does
AgentShield Lite analyzes MCP tool names, descriptions, and input schemas and returns explainable verdicts:
- `SAFE`
- `REVIEW`
- `HIGH RISK`
Lite includes a deliberately limited starter ruleset for:
- Shell / OS command execution
- Destructive file operations
- Filesystem reads
- External network access
- Secrets / credential access
It supports static JSON scanning and also runs as an MCP server exposing the `analyze_tools` tool.
## What is reserved for AgentShield Pro
The paid Pro edition is being developed separately and is not included in this public repository. Planned Pro capabilities include:
- Direct stdio MCP discovery
- Expanded security rules
- Allowlist / blocklist policy files
- Trusted-domain policy
- Better network classification
- CI/CD exit codes and security gates
- Scan history and scan diff
- SARIF / advanced reporting
- Source and package inspection
- Remote MCP scanning
- Advanced evidence and policy controls
## Install
```bash
npm install
```
## Test
```bash
npm test
```
## Try the sample
```bash
npm run scan:sample
```
## Scan tool metadata from JSON
```bash
node src/cli.js scan-json examples/sample-tools.json --md-out report.md --json-out report.json
```
## Run Lite as an MCP server
```bash
node src/index.js
```
The Lite MCP server exposes:
- `analyze_tools`
## Security note
AgentShield performs heuristic metadata/schema inspection. A SAFE verdict is not proof that software is safe.
## Pro
AgentShield Pro is kept outside this public repository. A purchase link will be added when the first Pro release is ready.
## Ownership
Copyright © 2026 Mahmoud Hisham. All rights reserved. See `LICENSE.txt`.
TDQS
A3.7/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is zero risk of an agent confusing it with another. The tool's purpose is clearly defined.
Naming Consistency5/5
The single tool uses a clear verb_noun pattern ('analyze_tools'), and with only one name there is no inconsistency to evaluate.
Tool Count3/5
A single tool is at the lower boundary of acceptable scope. It may be intentional for a 'Lite' edition, but the set feels very thin.
Completeness4/5
The tool covers the core inspection task (names, descriptions, schemas) without execution, but lacks any auxiliary operations like listing, comparing, or exporting results—though these may be outside the Lite scope.
Maintenance
ActivityMaintained
ResponsivenessNo issues