Uplink
NPM · @UPLINK-CODE/MCP · SCANNED SEP 25
Automate a real, logged-in browser on your own device — no stored credentials, no bot detection.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 35 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3367 tokens (~187/item across 18 items; 15 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety25
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "never show it to the user", at byte 3382 of that field. See how to fix → Fail
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "uplink_run_script" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Uplink MCP server?
Uplink runs locally as an npm package, launched with npx -y @uplink-code/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @uplink-code/mcp
claude mcp add build-uplink-uplink -- npx -y @uplink-code/mcp
{
"mcpServers": {
"build-uplink-uplink": {
"command": "npx",
"args": [
"-y",
"@uplink-code/mcp"
]
}
}
} {
"servers": {
"build-uplink-uplink": {
"command": "npx",
"args": [
"-y",
"@uplink-code/mcp"
]
}
}
} codex mcp add build-uplink-uplink -- npx -y @uplink-code/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"build-uplink-uplink": {
"type": "local",
"command": [
"npx",
"-y",
"@uplink-code/mcp"
],
"enabled": true
}
}
} openclaw mcp add build-uplink-uplink --command npx --arg -y --arg @uplink-code/mcp
mcp_servers:
build-uplink-uplink:
command: "npx"
args: ["-y", "@uplink-code/mcp"] {
"McpServers": {
"build-uplink-uplink": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@uplink-code/mcp"
]
}
}
} assistant mcp add build-uplink-uplink -t stdio -c npx -a -y @uplink-code/mcp
{
"mcpServers": {
"build-uplink-uplink": {
"command": "npx",
"args": [
"-y",
"@uplink-code/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@uplink-code/mcp@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 35 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
uplink_await_network_request ~81
Wait for the next network request whose URL contains `url_pattern` (substring match). Returns method, URL, status, headers, and a body preview.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_ms | number | – | How long to wait. Default 15000, max 60000. |
| url_pattern | string | yes | Substring to match against the request URL |
No output schema declared.
No examples provided.
uplink_connect ~421
Start a new Uplink session for pairing a device via the Uplink Connect app. Call this before any other tool that drives the device. AFTER this returns, in the SAME response turn, IMMEDIATELY call uplink_wait_for_device — do NOT end your turn saying "let me know when you've paired" or wait for the user to confirm. wait_for_device is the pairing-detection mechanism; see its description for the timeout-and-refresh loop. Never poll uplink_session_status as a substitute. CRITICAL: Claude Code collapses ALL MCP tool output behind ctrl+o — the tool result is invisible unless expanded, so your response prose is the only thing the user sees. Render the pairing instructions in YOUR OWN prose, using the exact link and code from the tool result. Pairing hands off from the user's desktop to their phone, so LEAD WITH THE LINK: on iPhone, opening the link (or scanning a QR) launches the Connect App Clip and pairs instantly, no install. Give the 6-digit code as the SECONDARY path (Android, or when Connect is already open). Render roughly: ``` ^ Uplink session started! Pair your phone: • iPhone — open this link on your phone to pair instantly (Connect App Clip, no install): http://localhost:4100/link/s/<uuid> • Android / Connect already open — enter code 123-456 (expires in 30s) ``` If the tool result includes a "Link copied to your clipboard" line, surface it too — the user can paste the link onto their iPhone via Universal Clipboard. The user can also scan a QR — mention they can ask for one (only call uplink_get_qr if they explicitly ask). If the user mentions a custom SDK implementation, also include the JWT line from the tool result. Do not paraphrase or omit the link/code — print them verbatim.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | – | Uplink project ID. Defaults to the API key owner's Playground project. |
No output schema declared.
No examples provided.
uplink_evaluate_javascript ~68
Run a JS expression in the device's page context and return the result. Can take either a single expression (`document.title`) or a statement block (`const r = await fetch(...); return r.json()`).
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | JS expression or statement block to evaluate |
No output schema declared.
No examples provided.
uplink_get_command_result ~37
Fetch a single captured page command by id (the id from uplink_list_commands).
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Command id. |
No output schema declared.
No examples provided.
uplink_get_current_url ~22
Returns the current URL of the device's active page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
uplink_get_dom_snapshot ~45
Snapshot the DOM of the active device. Returns the body tree (formatted for LLM consumption) plus head metadata (title, base, meta tags, link rels).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
uplink_get_network_request ~38
Fetch a single captured network request by id (the id from uplink_search_network).
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Network request id. |
No output schema declared.
No examples provided.
uplink_get_qr ~159
Render the active session's pairing URL as an ASCII QR code. Opt-in: only call when the user explicitly asks to see a QR (e.g., 'show me a QR' / 'I want to scan'). CRITICAL: Claude Code collapses tool output behind ctrl+o. After calling this tool, you MUST paste the returned QR ASCII art VERBATIM into your own response prose — every line of unicode half-blocks, exactly as returned. Do not say 'scan above' or 'see the QR' — those refer to the collapsed tool output which the user cannot see. The user will only see what you write directly. Yes, this is verbose, but the user explicitly asked for the QR; render it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
uplink_list_commands ~74
List captured page commands (method, args, result/error, timing) emitted while uplink_run_script executed. Optional `method` filter and `limit`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Most-recent N entries. |
| method | string | – | Filter by page method name (e.g., "goto", "click"). |
No output schema declared.
No examples provided.
uplink_read_logs ~65
Return captured console logs from `uplink_run_script` invocations on the active session. Optional `level` filter and `limit`.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Filter by log level. |
| limit | number | – | Most-recent N entries. Defaults to all retained. |
No output schema declared.
No examples provided.
uplink_refresh_pairing_code ~111
Mint a fresh 6-digit pairing code for the active session. Use this if the previous code expired (30s TTL) before the user typed it — the session itself stays valid, only the OTP rotates. Surface the new code in YOUR OWN prose, same format as uplink_connect (XXX-XXX), e.g.: `New pairing code: 123-456 (expires in 30s)` Claude Code collapses tool output; the code must be visible in your prose.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
uplink_run_script ~90
Execute a script against the device. The script body has `page` and `console` bound. Returns counts of captured flows + logs plus any error.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JS source to execute. `page` and `console` are bound in scope. |
| wait_for_idle_ms | number | – | Settling window after script resolves; default 3000, max 10000. |
No output schema declared.
No examples provided.
uplink_search_network ~75
Search captured network requests by URL substring. Returns matches with method, URL, status, headers, and body previews. Use uplink_get_network_request to fetch a single entry by id.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Most-recent N matches. |
| url_pattern | string | yes | Substring to match against the request URL. |
No output schema declared.
No examples provided.
uplink_session_status ~25
Return whether a session is active and whether a device is paired to it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
uplink_wait_for_device ~273
Block until a device finishes pairing on the active session, then return its metadata (deviceModel, platform, platformVersion, deviceType). Resolves immediately if a device is already paired. Default timeout is intentionally short (25s, under the 30s OTP TTL) so each call returns control to you in time to refresh the code before it expires. When this errors with `pairing_timeout` and the user hasn't indicated they're done: 1. Call `uplink_refresh_pairing_code` to mint a fresh code. 2. Surface the new code in YOUR OWN prose (same XXX-XXX format as uplink_connect): `New pairing code: 123-456 (expires in 30s)` 3. Call `uplink_wait_for_device` again to keep waiting. Keep looping until either (a) the call returns successfully (device paired), (b) the user says to stop, or (c) the user says they've paired (still call wait_for_device once more — it returns immediately if the device is already there). This loop gives the user windows between iterations to interrupt or change approach.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_ms | number | – | How long to wait for a device to pair. Default 25000 (25s, intentionally under OTP TTL). Max 600000 (10 min). |
No output schema declared.
No examples provided.
What is the Uplink MCP server?
Uplink is an MCP server listed in the public MCP registry as build.uplink/uplink. Automate a real, logged-in browser on your own device, no stored credentials, no bot detection. This page covers its npm package (@uplink-code/mcp).
Is the Uplink MCP server safe to use?
Uplink scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Uplink MCP server expose?
Uplink exposes 15 tools: uplink_connect, uplink_refresh_pairing_code, uplink_get_qr, uplink_wait_for_device, uplink_session_status, and 10 more. Their descriptions and schemas cost roughly 1,584 tokens of context every time the server is loaded.
Is the Uplink MCP server still maintained?
Uplink is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Uplink MCP server under?
Uplink declares the proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.