api-anything@0.4.0
VERIFIED· startup onlyPublisher claims: "Learn reusable operations from a website's browser traffic and call them from a CLI, library or MCP server." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
API_ANYTHING_TOKENConfiguration, not credentials: API_ANYTHING_ALLOW_IMPORT, API_ANYTHING_BROWSER, API_ANYTHING_BROWSER_ROOTS, API_ANYTHING_HOME, API_ANYTHING_KEY, API_ANYTHING_PACE, API_ANYTHING_PLAINTEXT, CODEX_HOME, DBUS_SESSION_BUS_ADDRESS, HERMES_HOME, NODE_TEST_CONTEXT, PATHEXT, XDG_RUNTIME_DIR- Where it talks to
- no vendor host named in the codeAlso site.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names site.com as well as its own vendor. The guard injects API_ANYTHING_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 80/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 · 29 s · 2 scenarios · 0 deviationsStatic findings
* Whether an entry is the npx one setup writes, pinned or not: only such an entry may have its pinFix: Pin versions and sources; vendor anything fetched at install time.lines.push("npx -y api-anything setup", REPO);Fix: Pin versions and sources; vendor anything fetched at install time.* Whether an entry is the npx one setup writes, pinned or not: only such an entry may have its pinFix: Pin versions and sources; vendor anything fetched at install time./** The npx entry, unpinned (`npx` fetches the newest release at each start) or pinned to this version. */Fix: Pin versions and sources; vendor anything fetched at install time./** The entry for agents that start from the user's shell (Claude Code, Codex) and so find npx on PATH. */Fix: Pin versions and sources; vendor anything fetched at install time.// pinned: npx fetches exactly this version at each start, not the newest releaseFix: Pin versions and sources; vendor anything fetched at install time.--pin with --print-config: the npx form pinned to this version (api-anything@<version>)Fix: Pin versions and sources; vendor anything fetched at install time.* last request of an hour. The slots are kept in pace.json and the counts in sends.json, both underFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* The entry for a GUI app (Cursor, Claude Desktop, VS Code). It starts with a minimal PATH, where npx from nvm orFix: Pin versions and sources; vendor anything fetched at install time.* runs through `npx -y api-anything` and so is always the latest release while a copy is not:Fix: Pin versions and sources; vendor anything fetched at install time.Connects the MCP server (npx -y api-anything mcp) to the agents you choose: Claude Code, Codex,Fix: Pin versions and sources; vendor anything fetched at install time.* Homebrew is not found: so the npx setup would run, by its absolute path, with node's directory on PATHFix: Pin versions and sources; vendor anything fetched at install time.--pin with --print-config: the npx form pinned to this version (api-anything@<version>)Fix: Pin versions and sources; vendor anything fetched at install time.next = { ...cur, ...(r.args ? { args: r.args } : {}), ...(r.path ? { env: { ...env, PATH: r.path } } : {}) };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.next = { ...cur, ...(r.args ? { args: r.args } : {}), ...(r.path ? { env: { ...env, PATH: r.path } } : {}) };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./** The npx entry, unpinned (`npx` fetches the newest release at each start) or pinned to this version. */Fix: Pin versions and sources; vendor anything fetched at install time.// pinned: npx fetches exactly this version at each start, not the newest releaseFix: Pin versions and sources; vendor anything fetched at install time.* The entry for a GUI app (Cursor, Claude Desktop, VS Code). It starts with a minimal PATH, where npx from nvm orFix: Pin versions and sources; vendor anything fetched at install time.? `${out} (api-anything is a CLI: run it in your shell, as npx -y api-anything when the command is not installed; with no shell, ask the user)`Fix: Pin versions and sources; vendor anything fetched at install time.? `${out} (api-anything is a CLI: run it in your shell, as npx -y api-anything when the command is not installed; with no shell, ask the user)`Fix: Pin versions and sources; vendor anything fetched at install time.* `added`: connected now. `unchanged`: already exactly this. `updated`: setup's npx entry, its pin movedFix: Pin versions and sources; vendor anything fetched at install time.* runs through `npx -y api-anything` and so is always the latest release while a copy is not:Fix: Pin versions and sources; vendor anything fetched at install time./** The entry for agents that start from the user's shell (Claude Code, Codex) and so find npx on PATH. */Fix: Pin versions and sources; vendor anything fetched at install time.lines.push("npx -y api-anything setup", REPO);Fix: Pin versions and sources; vendor anything fetched at install time.Connects the MCP server (npx -y api-anything mcp) to the agents you choose: Claude Code, Codex,Fix: Pin versions and sources; vendor anything fetched at install time.* last request of an hour. The slots are kept in pace.json and the counts in sends.json, both underFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for api-anything@0.4.0 as of 5d ago. This is the package itself, not its dependencies.