Skills/npm/apono-mcp

apono-mcp@0.2.53

CAUTION· startup only

Publisher claims: "Apono MCP server for Claude Code, Claude Desktop, and Cursor" Observed in sandbox: sends data to apono-agentic-releases.s3.amazonaws.com.

Registry npm (MCP server)Publisher apono-io · publishing for 237 daysInstalls 8,405Last detonated 11 h ago

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: Caution 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 codeAlso amazonaws.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · contacted apono-agentic-releases.s3.amazonaws.com (undeclared)
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Find out what these hosts are first. In the honeypot it contacted apono-agentic-releases.s3.amazonaws.com, which nothing in the package names as its own. If that is the vendor's service, fine; if you cannot place it, do not connect it.

$vet-skills run --net apono-agentic-releases.s3.amazonaws.com -- npx -y @apono-io/apono-mcp

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-14 and scored it 72/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: sends data to apono-agentic-releases.s3.amazonaws.com.

Behavior trace

Honeypot run · 20 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
20snetworkCONNECT tcp://apono-agentic-releases.s3.amazonaws.com:443 · not in the allow-list, refused
20sclaimedstartup only: exited (0) before answering · Downloading Apono CLI v0.2.53... (node:3354) [UNDICI-EHPA] Warning: EnvHttpProxyAgent is experimental, expect them to change at any time. (Use `node --trace-warnings ...` to show where the warning was created) Error: Failed to establish tunnel to apono-agentic-releases.s3.amazonaws.com:443 via http://127.0.0.1:33305: HTTP/1.1 403 Egress blocked by sandbox
20sprocessscript backend runs setup only
20sprocessno install scripts to re-run

Static findings

No findings across 467 lines in 6 files.

Cost to the agent

Instructions loaded
≈52 tok
1 file · 6 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 @apono-io/apono-mcp@0.2.53 as of 7d ago. This is the package itself, not its dependencies.

What would make this Verified

8 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
  2. Unclaimed publisher≈ +8 on the totalClaim apono-io: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim apono-ioPropose a patch to the maintainer