WebUplink — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Web browsing and session interaction through WebUplink MCP

What we know

Web browsing and session interaction through WebUplink MCP. Published by the owner of npm package @webuplink/mcp. Give any MCP client the ability to browse and interact with the web via WebUplink.

Maintenance / activity evidence

186 npm downloads, 2026-09-09 to 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high_for_identity_and_metrics_medium_for_verified_package_description.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions. Reported action classes: Web session navigation or form submission. Complete write authority is not verified.
WebUplink account or session authorization; exact scope in upstream docs
Sensitive access: Service account information and data accessible by supplied credentials

Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 186 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @webuplink/mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has @webuplink/mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions.

Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
WebUplink account or session authorization; exact scope in upstream docs
Reviewed write actions: Web session navigation or form submission
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

186 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/@webuplink/mcp

Exact implementation source: https://www.npmjs.com/package/@webuplink/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@webuplink/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
@webuplink/mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Use publisher-documented stdio MCP client configuration; HTTP launch is an alternative server transport, not client registration.
Configure / authenticate
MCP100 setup guide
WEBUPLINK_API_KEY required. Local HTTP option must be secured; package README warns not to expose HTTP listener directly to untrusted networks.
Environment variables referenced by this route (respect the alternatives above): WEBUPLINK_API_KEY
Alternative HTTP template; replace the recorded secret placeholder and secure the listener: WEBUPLINK_API_KEY=<configured secret> npx --yes --package @webuplink/mcp webuplink-mcp-http
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Web browsing and session interaction through WebUplink MCP. Published by the owner of npm package @webuplink/mcp. Give any MCP client the ability to browse and interact with the web via WebUplink.

Capability: Browser Automation
Resource type: MCP Server
Best fit: Web browsing and session interaction through WebUplink MCP

Representative uses

Web browsing and session interaction through WebUplink MCP

Limitations

Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: WebUplink account or session authorization; exact scope in upstream docs
Permissions: Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions.
Data handling: Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions.

Access scope and cautions

Write actions: Not verified Web session navigation or form submission
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: high
Security notes: Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: WebUplink account or session authorization; exact scope in upstream docs

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Web session navigation or form submission. Recorded permission context: Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions.

What data-handling boundary should I consider?

Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

Remote web browser sessions may access authenticated pages and trigger actions; protect credentials and require approval for form submissions. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.