io.github.Rererr/amenbo
NPM · AMENBO · SCANNED SEP 20
Japanese-web-native MCP server for low-impact, token-efficient web collection
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
- 5 of 45 dependencies flagged as unhealthy. 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 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 391 tokens (~130/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.Rererr/amenbo MCP server?
io.github.Rererr/amenbo runs locally as an npm package, launched with npx -y amenbo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · amenbo
claude mcp add rererr-amenbo -- npx -y amenbo
{
"mcpServers": {
"rererr-amenbo": {
"command": "npx",
"args": [
"-y",
"amenbo"
]
}
}
} {
"servers": {
"rererr-amenbo": {
"command": "npx",
"args": [
"-y",
"amenbo"
]
}
}
} codex mcp add rererr-amenbo -- npx -y amenbo
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rererr-amenbo": {
"type": "local",
"command": [
"npx",
"-y",
"amenbo"
],
"enabled": true
}
}
} openclaw mcp add rererr-amenbo --command npx --arg -y --arg amenbo
mcp_servers:
rererr-amenbo:
command: "npx"
args: ["-y", "amenbo"] {
"McpServers": {
"rererr-amenbo": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"amenbo"
]
}
}
} assistant mcp add rererr-amenbo -t stdio -c npx -a -y amenbo
{
"mcpServers": {
"rererr-amenbo": {
"command": "npx",
"args": [
"-y",
"amenbo"
]
}
}
} 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.
- 18 Sept 26 −3
- Stability: pass → 0.77 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 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.
- 14 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.
- 12 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.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 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 20 Sept 2026 · Analysed npm/amenbo@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 45 packages
| Packages resolved | 45 |
|---|---|
| Stale | 5 |
| 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 →
fetch Fetch a web page as Markdown ~215
Fetch a web page (Japanese-web-native) as low-impact, token-efficient Markdown. Built-in robots.txt compliance, rate limiting, and caching. mode: auto (default; quality score picks Markdown or screenshot) / markdown / outline (heading summary) / screenshot. Refetching a cached URL returns cache: unchanged, or diff (changed sections only), to save tokens. PDF URLs are handled automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| force_full | boolean | – | Default false. If true, disables diff responses (unchanged/diff) and boilerplate-block removal (pagination by max_tokens still applies) |
| max_tokens | integer | – | Approximate token budget per page (default 8000) |
| mode | string | – | Default: auto |
| page | integer | – | Page number (default 1) |
| section | string | – | Section ID obtained from outline mode; returns only that section's Markdown |
| selector | string | – | CSS selector to narrow the content |
| url | string | yes | Target URL (http/https only; PDF supported) |
No output schema declared.
No examples provided.
links List links from a page (sitemap/RSS-first) ~57
Low-impact link discovery: prefers sitemap.xml / RSS / Atom feeds when available, otherwise extracts in-page links.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Substring match against URL/link text, or a glob using * |
| url | string | yes | Starting URL |
No output schema declared.
No examples provided.
screenshot Capture a tiled screenshot of a web page ~119
For explicit visual inspection. Renders the page with a headless browser and returns tiled PNG screenshots. Built-in robots.txt compliance, rate limiting, and caching.
| Name | Type | Req | Description |
|---|---|---|---|
| fullPage | boolean | – | Default true. If false, captures only the first viewport (1 tile) |
| scale | number | – | Resolution scale (0.5-1.0, default 1.0); lower reduces image tokens |
| url | string | yes | Target URL (http/https only) |
| width | integer | – | Tile width in px (default 1280) |
No output schema declared.
No examples provided.
What is the io.github.Rererr/amenbo MCP server?
io.github.Rererr/amenbo is an MCP server listed in the public MCP registry as io.github.Rererr/amenbo. Japanese-web-native MCP server for low-impact, token-efficient web collection. This page covers its npm package (amenbo).
Is the io.github.Rererr/amenbo MCP server safe to use?
io.github.Rererr/amenbo scores 83 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.Rererr/amenbo MCP server expose?
io.github.Rererr/amenbo exposes 3 tools: fetch, links, screenshot. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.
Is the io.github.Rererr/amenbo MCP server still maintained?
io.github.Rererr/amenbo 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.Rererr/amenbo MCP server under?
io.github.Rererr/amenbo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.