Server providing Argo CD integration for MCP clients.
Nothing to run from here
Nekoweb is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
289
downloads a day
local
runs on your machine
24
tools declared
What it does
Manage your Nekoweb website: browse, edit, upload and deploy files, and check site stats.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'NEKOWEB_API_KEY=${NEKOWEB_API_KEY}' --transport stdio nekoweb-mcp '--' npx -y nekoweb-mcp-server
# 2 — ask your agent for something these tools do
# nekoweb_list_folder, nekoweb_read_file, nekoweb_create and 21 more
It needs NEKOWEB_API_KEY: this reads it from your environment, so export it first.
Nekoweb costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Nekoweb as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads NEKOWEB_API_KEY (Your API key from https://nekoweb.org/api) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx NEKOWEB_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'NEKOWEB_API_KEY=${NEKOWEB_API_KEY}' --transport stdio nekoweb-mcp '--' npx -y nekoweb-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: NEKOWEB_API_KEY — Your API key from https://nekoweb.org/api. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
24 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the files and folders inside a folder of your Nekoweb site, sorted by path. Set recursive=true to walk subfolders too (up to max_depth levels; each subfolder costs one API request against the rate limit, capped at … per call). Results are paginated with limit/offset. Examples: - "What's…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | yes | — | |
| recursive | boolean | no | Also list the contents of subfolders |
| max_depth | integer | no | How many folder levels to descend when recursive=true |
| limit | integer | no | Maximum number of entries to return |
| offset | integer | no | Number of entries to skip, for pagination |
| response_format | yes | — |
Read the raw source of a file on your Nekoweb site (SSI directives in .html files are returned as written, not rendered). Text files are returned as text, paginated by character offset. Images up to … are returned as images. Other binaries return only their size. Examples: - "Show me my…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | yes | — | |
| offset | integer | no | Character offset to start reading from, for files longer than max_chars |
| max_chars | integer | no | Maximum characters of text to return |
Create a new empty file or a new folder on your Nekoweb site. Fails if something already exists at that path. To create a file with content in one step, use nekoweb_write_file instead. Examples: - "Make a blog folder" -> { path: "/mysite.nekoweb.org/blog", is_folder: true } - "Create an…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | yes | — | |
| is_folder | boolean | yes | true to create a folder, false to create an empty file |
Write text content to a file on your Nekoweb site, creating it or replacing its entire content. mode='create_or_overwrite' (default) uploads the file whether or not it exists; the parent folder must already exist (create it with nekoweb_create). mode='edit_existing' only changes a file that…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | yes | — | |
| content | string | yes | The complete new content of the file (UTF-8 text) |
| mode | string | no | 'create_or_overwrite' (default) writes the file whether or not it exists; 'edit_existing' fails if it doesn't |
Permanently delete a file or a folder (including everything inside it) from your Nekoweb site. This cannot be undone. Example: "Remove the old drafts folder" -> { path: "/mysite.nekoweb.org/drafts" }
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | yes | — |
Rename or move a file or folder on your Nekoweb site. Both are full paths from your file root; the destination's parent folder must exist. Examples: - "Rename about.html to about-me.html" -> { from: "/mysite.nekoweb.org/about.html", to: "/mysite.nekoweb.org/about-me.html" } - "Move logo.png…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | yes | — | |
| to | yes | — |
Get a Nekoweb site's title, domain, views, followers, update count and creation/update dates. Without 'site', returns the site that the configured API key belongs to. With 'site', looks up any public Nekoweb site (no API key needed). Examples: - "How many views does my site have?" -> {} -…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | Domain of another site, e.g. 'fairfruit.nekoweb.org'. Omit for your own site. |
| response_format | yes | — |
List every site on the Nekoweb account that owns the API key, with domain, title, views, followers, dates and the folder that holds each site's files. The main site is marked. Call this first to learn the folder to use in file paths, e.g. '/mysite.nekoweb.org'. Use nekoweb_get_site_info for a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| response_format | yes | — |
Show the account's current API rate limits: 'general' (most file operations), 'big_uploads' (chunked uploads over 95MB) and 'zip' (zip imports). Each limit has the maximum, how many requests remain, and when the counter resets. Call this before bulk operations or after a 429 error.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| response_format | yes | — |
Upload one or more files (any type, e.g. images, fonts, HTML) into a folder of your Nekoweb site. Existing files with the same name are overwritten. Provide files as local_paths (files on this machine) and/or as base64 'files'. Files over 95MB are sent automatically with Nekoweb's chunked…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| folder | string | no | Destination folder, e.g. '/mysite.nekoweb.org/images'; must already exist |
| local_paths | array | no | Absolute paths of local files; each keeps its file name |
| files | array | no | Files to upload from base64 content, each with a name |
Upload a .zip archive and extract it into a folder of your Nekoweb site, e.g. to deploy a whole site at once. Extracted files overwrite existing files with the same paths. The 'zip' rate limit is strict (often 1 import per period); check nekoweb_get_limits first when unsure. Example: "Deploy my…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| folder | string | no | Folder to extract into, e.g. '/mysite.nekoweb.org' |
| zip_local_path | string | no | Absolute path of a local .zip file |
| zip_base64 | no | The .zip file's bytes, base64-encoded |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nekoweb or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 1.1.0 · scanned 6 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 3 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest5bc50749e27efa9919ed284aba21205db063cae2f5b6ec3af130e180e0e5e676
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (24 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| nekoweb_list_folder | no tags | |
| nekoweb_read_file | sensitive-source | sensitive-source: keyword "read_file" |
| nekoweb_create | no tags | |
| nekoweb_write_file | file-write | file-write: keyword "write_file" in tool name |
| nekoweb_delete | no tags | |
| nekoweb_move | no tags | |
| nekoweb_list_followers | no tags | |
| nekoweb_get_tags | no tags | |
| nekoweb_add_tag | no tags | |
| nekoweb_remove_tag | no tags | |
| nekoweb_get_site_settings | no tags | |
| nekoweb_update_site_settings | no tags | |
| nekoweb_get_site_info | no tags | |
| nekoweb_list_sites | no tags | |
| nekoweb_get_limits | no tags | |
| nekoweb_list_following | no tags | |
| nekoweb_get_feed | untrusted-input | untrusted-input: keyword "rss" |
| nekoweb_get_global_feed | untrusted-input | untrusted-input: keyword "rss" |
| nekoweb_get_news | no tags | |
| nekoweb_search_sites | untrusted-input | untrusted-input: keyword "browse" |
| nekoweb_follow_site | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| nekoweb_get_stats_history | no tags | |
| nekoweb_upload_file | external-sink | external-sink: keyword "upload_file" |
| nekoweb_import_zip | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
nekoweb_get_feed → nekoweb_read_file → nekoweb_follow_site
A cross-tool exfiltration chain exists: nekoweb_get_feed → nekoweb_read_file → nekoweb_follow_site.
Supply chain and provenance
Integrityfirst-seen
Surface digest5bc50749e27efa99
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.0. Pin a release below and the command asks for exactly that one.
1.1.0
6 Nov 2026
latestNo release note was published with this version.
1.0.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Nekoweb can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.