Skills/npm/infonetz-mcp

infonetz-mcp@2.3.1

CAUTION

Publisher claims: "Model Context Protocol (MCP) Server for Infonetz Multi-Tenant Media Network" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher asmuldev · publishing for 3 daysInstalls 835Last detonated 10 h ago
What would fix thisWatchDispute verdict

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
INFONETZ_API_TOKENConfiguration, not credentials: INFOGARUT_API_BASE_URL, INFONETZ_API_BASE_URL, INFONETZ_TENANT_ID, MCP_TRANSPORT
Where it talks to
infonetz.id (its own)
What the honeypot saw
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for INFONETZ_API_TOKEN and talks to infonetz.id. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind.

$vet-skills run --secrets INFONETZ_API_TOKEN=infonetz.id -- npx -y infonetz-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) on 2026-11-14 and scored it 77/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; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 26 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
5.9sprocessdependency install exit 0
26sclaimed14 tools: infonetz_whoami, infonetz_list_media, infonetz_get_categories, infonetz_search_posts, infonetz_upload_image, infonetz_create_post, infonetz_my_posts, infonetz_update_post, infonetz_delete_post, infonetz_get_network_stats, infonetz_login, infonetz_verify_login, infonetz_logout, infonetz_create_category
26stoolsd2e30aad7b048b5f
26stools354068aa4bdae838
26stools6c177976e7d7f0ed
26stools22b4471807033018
26stoolseae50638539c6af5
26stools714bc26f52421c24
26stoolse6891225a66dc6f2
26stoolsdfa67813bb1a57df
26stools5758292ee4b0e29e
26stools275908cfd1fc9f8e
26stools62669612fcdc676b
26stools94f770ddf3bd297a
26stools0016ff660d5c813e
26stools66d1bc414f4b8f41
26sprocessscript backend runs setup only
26sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packageindex.js:10 · npx invocation of non-well-known package — may execute untrusted code* npx @infonetz/mcp status -> Cek profil & media aktifFix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsindex.js:39 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// Muat fallback .env jika ada (quiet agar tidak merusak stdio JSON-RPC)Fix: 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 packageindex.js:11 · npx invocation of non-well-known package — may execute untrusted code* npx @infonetz/mcp logout -> Hapus kredensial lokalFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageindex.js:12 · npx invocation of non-well-known package — may execute untrusted code* npx @infonetz/mcp -> Jalankan MCP Server (Stdio Transport)Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsindex.js:40 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdotenv.config({ path: path.join(__dirname, '.env'), quiet: true });Fix: 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 packageindex.js:425 · npx invocation of non-well-known package — may execute untrusted codetext: '⚠️ MCP belum terautentikasi. Silakan jalankan `npx @infonetz/mcp login` untuk menghubungkan akun media Anda.',Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsindex.js:42 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdotenv.config({ path: path.join(__dirname, '..', 'backend', '.env'), quiet: true });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Auto-update or dynamic fetch configurationindex.js:670 · Auto-update or dynamic fetch configuration — agent may load new code at runtime// Auto-update existing draft on the same ID instead of creating duplicate draftsFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageindex.js:9 · npx invocation of non-well-known package — may execute untrusted code* npx @infonetz/mcp login -> Login akun SSO & pilih portal mediaFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈55 tok
1 file · 4 in bundle
Tool list per prompt
≈1,841 tok
14 tools · 132 per tool
Handshake
662 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 114

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 infonetz-mcp@2.3.1 as of 10 h ago. This is the package itself, not its dependencies.

What would make this Verified

3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim asmuldev: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. 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.
  3. Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  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 asmuldevPropose a patch to the maintainer