Skills/npm/anytype-mcp

anytype-mcp@2.0.3

VERIFIED· install only

Publisher claims: "Official MCP server for Anytype API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher anyproto · publishing for 541 daysInstalls 109KLast detonated 26 min ago
$claude mcp add anytype-mcp -- npx -y @anyproto/anytype-mcp
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
4 of 4 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it under the guard. Bundled scripts ran with no arguments; no agent task scenario for this bundle. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y @anyproto/anytype-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 2.0.2

vet-skills diff anytype-mcp 2.0.2 2.0.3

In the sandbox, this version reached for nothing 2.0.2 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: Node.js v22.23.5
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: Node.js v22.23.5
0.2sprocessbundled script run in the sandbox with no arguments
0.3sprocessexited 1: Node.js v22.23.5
0.3sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.4sprocessexited 1: Node.js v22.23.5
0.4sprocess4 of 4 bundled scripts run with no arguments
0.4sprocessscript backend runs setup only
0.4sprocessscript backend runs setup only
0.4sprocessno install scripts to re-run

Static findings

MEDIUM
File type combined with upload actionscripts/parse-openapi.ts:23 · File type combined with upload action — agent may exfiltrate local data filesconsole.log(`Successfully wrote parsed tools to ${outputFile}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
File permission modification commandscripts/build-cli.js:2 · File permission modification command — agent changes file ownership/permissionsimport { chmod } from "fs/promises";Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
HIGH
Collapsed <details> block carrying instructionsREADME.md:29 · Collapsed <details> block carrying instructions<summary>Alternative: Get API key via CLI</summary> You can also get your API key using the command line: ```bash npx -y @anyproto/anytype-mcp get-key ```Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

Cost to the agent

Instructions loaded
≈901 tok
2 files · 59 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.