Uplink
NPM · @UPLINK-CODE/MCP · SCANNED AUG 3
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 →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree. 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 40 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @uplink-code/mcp
claude mcp add build-uplink-uplink -- npx -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": {
"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.
- 2 Aug 26 +31
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- License: unverified → fail ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: proprietary functional
- 1 Aug 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −10
- Malware scan: pass → unverified ▼ security
- Schema quality: unverified → excellent ▲ functional
- 27 Jul 26 51
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@uplink-code/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 105 packages
105 packages in the resolved dependency tree · 101 deprecated · 31 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.