mcp@2.8.20

VERIFIED

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

Registry npm (MCP server)Publisher microlink · publishing for 144 daysInstalls 2,938Last detonated 8 min ago
$claude mcp add mcp -- npx -y @microlink/mcp
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 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
MICROLINK_API_KEYConfiguration, not credentials: MICROLINK_CONNECT_TIMEOUT_MS, MICROLINK_DASHBOARD_URL
Where it talks to
microlink.io (its own)
What we saw when it ran
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 MICROLINK_API_KEY and talks to microlink.io. 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 MICROLINK_API_KEY=microlink.io -- npx -y @microlink/mcp

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

What changed since 2.8.18

vet-skills diff mcp 2.8.18 2.8.20

This version reaches for something 2.8.18 did not: 1 new install script (node scripts/postinstall.js). Compared from the two recorded runs, not from source.

New install scripts
node scripts/postinstall.js

Tool descriptor hashes were not recorded for both runs; renamed or added tools are compared, rewritten descriptions are not.

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 (3 scenarios) on 2026-11-21 and scored it 90/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 26 s · 3 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
5.7sprocessdependency install exit 0
26sclaimed24 tools: microlink_list_plans, microlink_create_checkout_session, microlink_get_checkout_session, microlink_docs, microlink_metadata, microlink_logo, microlink_markdown, microlink_html, microlink_text, microlink_screenshot, microlink_pdf, microlink_embed, microlink_video, microlink_audio, microlink_links, microlink_images, microlink_videos, microlink_audios, microlink_emails, microlink_technologies, microlink_lighthouse, microlink_search, microlink_function, microlink_extract
26stoolsd33c13275b5801c9
26stools165e179e562845fe
26stoolsb3b66ddfe44b979d
26stoolsde959939fc1d4d2a
26stools165b324a2f069915
26stools286e3b203bbd76f8
26stools9c8d586bf05cf6c6
26stoolse09c634088015468
26stools7f0951efd41bd425
26stools689212159fc484e2
26stoolsb838d37d236495ff
26stoolsb2c0835764979b36
26stoolsa1bfb398b7e0e272
26stools5a9bab32e63606af
26stools990fe7b437d4b4c2
26stools7376551912916d20
26stools8cb3c26cd45fb462
26stoolse15021f516355144
26stools303ceef7ccbc2cf7
26stoolsc378dc506a966027
26stools2c2097ab76b7120e
26stools4f5dd0beb11508fe
26stools8277f920286ca391
26stools6c731bd2add8a550
26sprocessscript backend runs setup only
26sprocesssecond launch, clock +45 days, CI unset

Static findings

HIGH
Credential pass-through configurationsrc/index.js:20 · Credential pass-through configuration — agent relays sensitive credentials`Without an API key, requests use the free endpoint (${KEYLESS_REQUESTS_PER_DAY} requests/day); a free API key gives ${FREE_PLAN_REQUESTS_PER_DAY} requests/day. Pass apiKey or set MICROLINK_API_KEY.`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02

No other findings across 2,707 lines in 39 files.

Cost to the agent

Instructions loaded
≈42 tok
1 file · 39 in bundle
Tool list per prompt
≈25,197 tok
24 tools · 1050 per tool
Handshake
2562 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 133

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

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