AIShield Security Scanner
NPM · AISHIELD-MCP-SERVER
Scans MCP servers for tool poisoning, prompt injection and supply chain risks.
Available components
Last scanned (17 hours ago)
Scores higher than 97% of npm servers
Category Security
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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to lm203688/aishield). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 635 tokens (~105/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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 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.
- 11 Oct 26 −3
- Stability: pass → 0.77 functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 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.
- 28 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- Stability: 0.97 → pass security
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 16 Oct 2026 · Analysed npm/aishield-mcp-server@4.3.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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | lm203688/aishield |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/lm203688/aishield/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 2621766242 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4d55b6447f16aa338fa8f039d6fb727145c087d84b6893d50670eae4c7badacf7f98d225c55c512b3483adba0cefc389b69c50e5d8bfd8ceddf61ccab |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
aishield_banned_words ~96
中文违禁词检测 — 检测文本中的违禁词/敏感词。 覆盖6大平台: 微信/抖音/小红书/B站/知乎/微博 返回: 违禁词列表 + 法律条文 + 罚款金额 + 替换建议
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | 目标平台 |
| text | string | yes | 待检测文本 |
No output schema declared.
No examples provided.
aishield_guardrail ~96
AIShield安装前安全检查 — 在安装任何MCP/AI工具前调用此工具。 返回pass/block判定 + 评分 + OWASP合规矩阵。 建议在安装任何第三方MCP Server前自动调用此工具。
| Name | Type | Req | Description |
|---|---|---|---|
| auto_block | boolean | – | If true, return block verdict for unsafe tools |
| source_url | string | yes | GitHub repo URL of the tool to check |
No output schema declared.
No examples provided.
aishield_handshake ~105
MCP握手验证 — 分析MCP配置、检测npx自动安装风险、敏感环境变量、工具描述异常长度。 提取README/package.json中的MCP配置，分析: npx -y风险、敏感env变量、远程URL安全性、 工具描述长度（>500字符可能隐藏指令）。如果是HTTP类型MCP，尝试实际握手。
| Name | Type | Req | Description |
|---|---|---|---|
| source_url | string | yes | GitHub repo URL |
No output schema declared.
No examples provided.
aishield_prompt_check ~96
Prompt安全检测 — 检测用户输入的Prompt是否存在注入/越狱/数据外传风险。 支持中文和英文，覆盖: 越狱指令/身份切换/系统提示窃取/数据外传/角色扮演注入/零宽字符/Unicode编码
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | 待检测的Prompt文本（至少10个字符） |
No output schema declared.
No examples provided.
aishield_rug_pull ~91
Rug Pull检测 — 检查MCP工具是否在版本更新中移除安全代码或新增可疑网络请求。 对比最近commit diff，检测: 安全代码删除、新增网络请求、权限扩大、大量代码删除。 返回风险等级(critical/high/medium/low/safe)和具体发现。
| Name | Type | Req | Description |
|---|---|---|---|
| source_url | string | yes | GitHub repo URL |
No output schema declared.
No examples provided.
aishield_scan ~151
AIShield安全扫描 — 扫描MCP Server/AI工具的安全风险。 对齐OWASP MCP Top 10 (2025 v0.1) 与 Agentic AI Top 10，201条规则覆盖两套风险分类。 5维评分: 安全(40%)/权限(20%)/数据处理(20%)/供应链(10%)/可靠性(10%) 返回: 评分 + 风险等级 + OWASP合规矩阵 + 修复建议
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Tool name (optional) |
| source_url | string | yes | GitHub repo URL of the tool to scan |
| tool_type | string | – | Tool type |
No output schema declared.
No examples provided.
How do I install the AIShield Security Scanner MCP server?
AIShield Security Scanner runs locally as an npm package, launched with npx -y aishield-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · aishield-mcp-server
claude mcp add lm203688-aishield -- npx -y aishield-mcp-server
What is the AIShield Security Scanner MCP server?
AIShield Security Scanner is an MCP server listed in the public MCP registry as io.github.lm203688/aishield. Scans MCP servers for tool poisoning, prompt injection and supply chain risks. This page covers its npm package (aishield-mcp-server).
Is the AIShield Security Scanner MCP server safe to use?
AIShield Security Scanner scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. 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 AIShield Security Scanner MCP server expose?
AIShield Security Scanner exposes 6 tools: aishield_scan, aishield_guardrail, aishield_prompt_check, aishield_banned_words, aishield_rug_pull, aishield_handshake. Their descriptions and schemas cost roughly 635 tokens of context every time the server is loaded.
Is the AIShield Security Scanner MCP server still maintained?
AIShield Security Scanner is still listed as active in the MCP registry. We last reached this channel on 16 October 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 AIShield Security Scanner MCP server under?
AIShield Security Scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.