Skills/npm/mcp-server

mcp-server@0.0.5

CAUTION· startup only

Publisher claims: "Model Context Protocol (MCP) server for Paystack API integration" Observed in sandbox: calls raw.githubusercontent.com only, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher paystack · publishing for 247 daysInstalls 334Last detonated 4d ago
What would fix thisWatchDispute verdict

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
Needs
PAYSTACK_TEST_SECRET_KEY, --api-key — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

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
PAYSTACK_TEST_SECRET_KEYConfiguration, not credentials: PAYSTACK_SKILL_URL, USER_AGENT
Where it talks to
paystack.co, paystack.com (its own)Also githubusercontent.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · reached only raw.githubusercontent.com
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 githubusercontent.com as well as its own vendor. The guard injects PAYSTACK_TEST_SECRET_KEY only into requests to paystack.co (and its subdomains) and refuses the rest.

$vet-skills run --secrets PAYSTACK_TEST_SECRET_KEY=paystack.co -- npx -y @paystack/mcp-server

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-10 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Stripe-like API key pattern detected. Summary: calls raw.githubusercontent.com only, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 53 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
12sprocessdependency install exit 0
32sprocessrelaunched with a decoy PAYSTACK_TEST_SECRET_KEY (tagged; nothing real)
52sfilesystemread ~/.paystack-mcp/skill-cache.md outside project
52snetworkCONNECT tcp://raw.githubusercontent.com:443 · not in the allow-list, refused
52sclaimedstartup only: exited before answering, asking for PAYSTACK_TEST_SECRET_KEY, --api-key (a decoy value was refused)
52sprocessscript backend runs setup only
52sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagebuild/index.js:62 · npx invocation of non-well-known package — may execute untrusted codePAYSTACK_TEST_SECRET_KEY=sk_test_... npx @paystack/mcp-serverFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagebuild/index.js:61 · npx invocation of non-well-known package — may execute untrusted codenpx @paystack/mcp-server --api-key sk_test_1234567890abcdefFix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsbuild/config.js:9 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// Load environment variables from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
npx invocation of non-well-known packagebuild/index.js:51 · npx invocation of non-well-known package — may execute untrusted codenpx @paystack/mcp-server --api-key <your-test-secret-key>Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Stripe-like API key pattern detectedbuild/index.js:61 · Stripe-like API key pattern detected — possible hardcoded or harvested keynpx @paystack/mcp-server --api-key sk_test_1234567890abcdefFix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03

Cost to the agent

Instructions loaded
≈53 tok
1 file · 38 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 @paystack/mcp-server@0.0.5 as of 4d ago. This is the package itself, not its dependencies.

What would make this Verified

2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim paystack: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
  3. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. Stripe-like API key pattern detected≈ +4 on the totalNever read or enumerate credential locations; accept a documented environment variable instead.
  5. npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim paystackPropose a patch to the maintainer