io.github.leochong/visus-mcp
NPM · VISUS-MCP · SCANNED SEP 20
Security-first web access for Claude. Sanitizes pages, blocks injection, redacts PII.
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 Security99
- 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
- 41 of 198 dependencies flagged as unhealthy (1 deprecated). 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 144 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 426 tokens (~106/item across 4 items; 4 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 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 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.leochong/visus-mcp server?
io.github.leochong/visus-mcp runs locally as an npm package, launched with npx -y visus-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 · visus-mcp
claude mcp add leochong-visus-mcp -- npx -y visus-mcp
{
"mcpServers": {
"leochong-visus-mcp": {
"command": "npx",
"args": [
"-y",
"visus-mcp"
]
}
}
} {
"servers": {
"leochong-visus-mcp": {
"command": "npx",
"args": [
"-y",
"visus-mcp"
]
}
}
} codex mcp add leochong-visus-mcp -- npx -y visus-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"leochong-visus-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"visus-mcp"
],
"enabled": true
}
}
} openclaw mcp add leochong-visus-mcp --command npx --arg -y --arg visus-mcp
mcp_servers:
leochong-visus-mcp:
command: "npx"
args: ["-y", "visus-mcp"] {
"McpServers": {
"leochong-visus-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"visus-mcp"
]
}
}
} assistant mcp add leochong-visus-mcp -t stdio -c npx -a -y visus-mcp
{
"mcpServers": {
"leochong-visus-mcp": {
"command": "npx",
"args": [
"-y",
"visus-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.
- 20 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 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.
- 13 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.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 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.
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/visus-mcp@0.6.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 198 packages
| Packages resolved | 198 |
|---|---|
| Deprecated | 1 |
| Stale | 41 |
| 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 →
visus_fetch Fetch Web Page (Sanitized) ~118
Fetch and sanitize web page content. Returns clean, injection-free content in markdown or text format. SECURITY: All content passes through prompt injection sanitization (43 pattern categories) and PII redaction BEFORE reaching the LLM. This ensures safe consumption of untrusted web content.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: markdown (default) or plain text |
| timeout_ms | number | – | Request timeout in milliseconds (default: 10000) |
| url | string | yes | The URL to fetch (must be http:// or https://) |
No output schema declared.
No examples provided.
visus_fetch_structured Fetch Structured Data (Sanitized) ~125
Fetch a web page and extract structured data according to a schema. SECURITY: All extracted fields pass through prompt injection sanitization (43 pattern categories) and PII redaction BEFORE being returned to the LLM. Each field is independently sanitized to ensure safe consumption of untrusted web content.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | object | yes | Field extraction schema: { fieldName: "field description", ... } |
| timeout_ms | number | – | Request timeout in milliseconds (default: 10000) |
| url | string | yes | The URL to fetch (must be http:// or https://) |
No output schema declared.
No examples provided.
visus_read Read Web Page (Reader Mode + Sanitized) ~100
Extracts clean article content from a web page using Mozilla Readability, stripping navigation, ads, and boilerplate. Full prompt injection sanitization and PII redaction applied before content reaches the LLM. Optimized for context-efficient, safe web reading in Claude Desktop.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_ms | number | – | Request timeout in milliseconds (default: 10000) |
| url | string | yes | The URL to fetch (must be http:// or https://) |
No output schema declared.
No examples provided.
visus_search Search the Web (Sanitized) ~83
Searches the web via DuckDuckGo and returns sanitized results with prompt injection and PII removed before reaching the LLM. Use before visus_fetch or visus_read to safely discover and then read pages.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | number | – | Maximum number of results to return (default: 5, max: 10) |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
What is the io.github.leochong/visus-mcp server?
io.github.leochong/visus-mcp is listed in the public MCP registry as io.github.leochong/visus-mcp. Security-first web access for Claude. Sanitizes pages, blocks injection, redacts PII. This page covers its npm package (visus-mcp).
Is the io.github.leochong/visus-mcp server safe to use?
io.github.leochong/visus-mcp scores 84 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.leochong/visus-mcp server expose?
io.github.leochong/visus-mcp exposes 4 tools: visus_fetch, visus_fetch_structured, visus_read, visus_search. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.
Is the io.github.leochong/visus-mcp server still maintained?
io.github.leochong/visus-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.leochong/visus-mcp server under?
io.github.leochong/visus-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.