@mcp-b/webmcp-ts-sdk — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

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

Best fit

Expose browser WebMCP tools via a TypeScript MCP v2 adapter

What we know

Thin WebMCP-to-MCP v2 browser adapter with native Chrome tool mirroring Expose browser WebMCP tools via a TypeScript MCP v2 adapter.

Maintenance / activity evidence

npm downloads 376408 in 2026-09-08..2026-10-07

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Complete write authority is not verified.
Web application integration rather than standalone server
Browser tools and origin-bound context

SDK / adapter, not an independent installed MCP Server. Browser origins and exposed tool permissions depend on embedding application.

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

Popularity

· 376.4k package downloads / 30 days

Downloads observed Oct 9, 2026.

Exact npm package @mcp-b/webmcp-ts-sdk; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Has @mcp-b/webmcp-ts-sdk changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

SDK / adapter, not an independent installed MCP Server. Browser origins and exposed tool permissions depend on embedding application.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Web application integration rather than standalone server
Browser tools and origin-bound context
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.
No exhaustive advisory or runtime review performed; never infer installation safety.
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.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
npm package downloads explicitly observed

Original activity observations

npm downloads 376408 in 2026-09-08..2026-10-07

Technical identity

npm/@mcp-b/webmcp-ts-sdk

Exact implementation source: https://www.npmjs.com/package/@mcp-b/webmcp-ts-sdk ↗
Reviewed resource type: SDK
Package identity: npm:@mcp-b/webmcp-ts-sdk

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

Package registry ↗
@mcp-b/webmcp-ts-sdk
Recorded package identity, distribution or download evidence.

Setup · Watchlist

SDK setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install SDK / application integration
Publisher instructions
Developer library/integration. Install in an application; not a plug-and-play MCP Server. Review publisher README. Not a standalone local MCP server; application integration required.
publisher documented install or connect · Publisher instructions
pnpm add @mcp-b/webmcp-ts-sdk @mcp-b/transports
Configure / authenticate
MCP100 setup guide
WebMCP TypeScript SDK is an application/library dependency; requires browser context and transports.
Check connection
Suggested check
Use a secure-origin browser test to initialize WebMCP adapter and inspect registered tools; not a standalone server. SDK/plugin validation means app import/initialization or feature availability, not an MCP client tools/list test unless the consuming app actually exposes a server.
Remove / uninstall / revoke
MCP100 setup guide
Remove the TypeScript WebMCP SDK via `pnpm remove @mcp-b/webmcp-ts-sdk`; remove application imports and registration handlers. Keep `@mcp-b/transports` if another project feature needs it.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: SDK itself has no vendor account credential; not applicable.
Package / application cleanup · matching installation environment · MCP100 composed guide
pnpm remove @mcp-b/webmcp-ts-sdk

Official Documentation & Sources

What it does

Thin WebMCP-to-MCP v2 browser adapter with native Chrome tool mirroring Expose browser WebMCP tools via a TypeScript MCP v2 adapter.

Capability: Developer Tools
Resource type: SDK
Best fit: Expose browser WebMCP tools via a TypeScript MCP v2 adapter

Representative uses

Embed MCP interfaces into a web or AI app
Register or adapt tool definitions
Connect framework-side MCP transport
Expose browser WebMCP tools via a TypeScript MCP v2 adapter

Limitations

SDK / adapter, not an independent installed MCP Server. Browser origins and exposed tool permissions depend on embedding application.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
npm package downloads explicitly observed

Reviewed access

Access & risk

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

Authentication: Web application integration rather than standalone server
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Browser tools and origin-bound context
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: SDK / adapter, not an independent installed MCP Server. Browser origins and exposed tool permissions depend on embedding application.

Access scope and cautions

Write actions: Not verified
Risk level: moderate
Security notes: SDK / adapter, not an independent installed MCP Server. Browser origins and exposed tool permissions depend on embedding application.

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-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Embed MCP interfaces into a web or AI app; Register or adapt tool definitions; Connect framework-side MCP transport; Expose browser WebMCP tools via a TypeScript MCP v2 adapter.

What setup and authentication are documented?

Recorded installation/entrypoint step: npm install @mcp-b/webmcp-ts-sdk. Prerequisites: Compatible development runtime. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Web application integration rather than standalone server

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Browser tools and origin-bound context

What limitations and risks should I check before use?

SDK / adapter, not an independent installed MCP Server. Browser origins and exposed tool permissions depend on embedding application. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. npm package downloads explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.