AgentSecurityLens MCP Security Trust Check
NPM · AGENT-SECURITY-LENS · SCANNED SEP 25
MCP security trust-check for agents before installing MCPs, Skills or tools.
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 (Apache-2.0).Pass
- Actively maintained (last published 80 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 752 tokens (~68/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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 AgentSecurityLens MCP Security Trust Check server?
AgentSecurityLens MCP Security Trust Check runs locally as an npm package, launched with npx -y agent-security-lens. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agent-security-lens
claude mcp add professor2k8-agent-security-lens -- npx -y agent-security-lens
{
"mcpServers": {
"professor2k8-agent-security-lens": {
"command": "npx",
"args": [
"-y",
"agent-security-lens"
]
}
}
} {
"servers": {
"professor2k8-agent-security-lens": {
"command": "npx",
"args": [
"-y",
"agent-security-lens"
]
}
}
} codex mcp add professor2k8-agent-security-lens -- npx -y agent-security-lens
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"professor2k8-agent-security-lens": {
"type": "local",
"command": [
"npx",
"-y",
"agent-security-lens"
],
"enabled": true
}
}
} openclaw mcp add professor2k8-agent-security-lens --command npx --arg -y --arg agent-security-lens
mcp_servers:
professor2k8-agent-security-lens:
command: "npx"
args: ["-y", "agent-security-lens"] {
"McpServers": {
"professor2k8-agent-security-lens": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"agent-security-lens"
]
}
}
} assistant mcp add professor2k8-agent-security-lens -t stdio -c npx -a -y agent-security-lens
{
"mcpServers": {
"professor2k8-agent-security-lens": {
"command": "npx",
"args": [
"-y",
"agent-security-lens"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- 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 25 Sept 2026 · Analysed npm/agent-security-lens@0.1.12
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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_component ~64
Check ASL online intelligence for a component and return an agent-readable install decision.
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | – | – |
| component_type | string | – | – |
| install_command | string | – | – |
| manifest | object|string | – | – |
| source_url | string | – | – |
No output schema declared.
No examples provided.
discover_workspace ~36
Discover Agent, MCP and Skill environments under a workspace path.
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | number | – | – |
| workspace_path | string | yes | – |
No output schema declared.
No examples provided.
get_install_policy ~38
Return the ASL machine-readable policy an autonomous agent should follow before installing MCPs, Skills, tools, prompt bundles, workflows or memory components.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_intelligence_status ~32
Return whether ASL MCP is using online cloud intelligence or local fallback, and whether the cloud API is reachable.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_research_status ~43
Check whether an unknown component submitted to ASL has been collected, scanned, reviewed, published, archived or is still pending.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_id | string | yes | – |
No output schema declared.
No examples provided.
recommend_alternatives ~62
Return safer alternatives and a safe install plan for a component.
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | – | – |
| component_type | string | – | – |
| install_command | string | – | – |
| manifest | object|string | – | – |
| source_url | string | – | – |
No output schema declared.
No examples provided.
report_install_outcome ~97
Report what happened after an agent followed an ASL decision. Use this to improve ASL adoption metrics and recommendation quality.
| Name | Type | Req | Description |
|---|---|---|---|
| alternative_used | string | – | – |
| component_name | string | – | – |
| component_type | string | – | – |
| decision | string | – | – |
| error_summary | string | – | – |
| outcome | string | – | – |
| restriction_applied | boolean | – | – |
| source_url | string | – | – |
No output schema declared.
No examples provided.
review_before_install ~178
Query ASL intelligence before an autonomous agent installs or enables an MCP, Skill, tool, prompt bundle, workflow, memory component or install command.
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | – | Component name, package name or display name. |
| component_type | string | – | – |
| install_command | string | – | Command the agent plans to run, such as npx/uvx/docker. |
| manifest | object|string | – | MCP/Skill manifest or config snippet. |
| planned_use | string | – | What the agent wants to use this component for. |
| requested_permissions | array | – | Permissions the agent expects this component to need, such as shell, filesystem, network or browser. |
| source_url | string | – | GitHub, registry, npm, Docker or documentation URL. |
| submit_if_unknown | boolean | – | Queue unknown components for ASL research. |
No output schema declared.
No examples provided.
scan_workspace ~46
Discover and assess every Agent, MCP and Skill environment under a workspace path. Use this for local context only.
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | number | – | – |
| workspace_path | string | yes | – |
No output schema declared.
No examples provided.
submit_decision_feedback ~84
Submit feedback about whether an ASL decision was useful, wrong, missing an alternative, or too strict. Do not include secrets or private code.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | – |
| component_name | string | – | – |
| component_type | string | – | – |
| decision | string | – | – |
| feedback_type | string | – | – |
| rating | number | – | – |
No output schema declared.
No examples provided.
submit_unknown_component ~72
Submit public metadata for an unknown component to the ASL research queue. Do not submit private file contents or secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | – | – |
| component_type | string | – | – |
| install_command | string | – | – |
| manifest | object|string | – | – |
| source_url | string | – | – |
No output schema declared.
No examples provided.
What is the AgentSecurityLens MCP Security Trust Check server?
AgentSecurityLens MCP Security Trust Check is listed in the public MCP registry as io.github.professor2k8/agent-security-lens. MCP security trust-check for agents before installing MCPs, Skills or tools. This page covers its npm package (agent-security-lens).
Is the AgentSecurityLens MCP Security Trust Check server safe to use?
AgentSecurityLens MCP Security Trust Check scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 AgentSecurityLens MCP Security Trust Check server expose?
AgentSecurityLens MCP Security Trust Check exposes 11 tools: get_install_policy, get_intelligence_status, review_before_install, check_component, recommend_alternatives, and 6 more. Their descriptions and schemas cost roughly 752 tokens of context every time the server is loaded.
Is the AgentSecurityLens MCP Security Trust Check server still maintained?
AgentSecurityLens MCP Security Trust Check is still listed as active in the MCP registry. We last reached this channel on 25 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 AgentSecurityLens MCP Security Trust Check server under?
AgentSecurityLens MCP Security Trust Check declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.