mcp-handler — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Fetch-compatible HTTP adapter for MCP server definitions: Does one handler preserve stateless discovery and legacy Streamable HTTP compatibility across supported frameworks?

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

Best fit

Developers embedding MCP endpoints in Fetch-compatible JavaScript/TypeScript frameworks.

What we know

A framework-agnostic Request/Response adapter for hosting Streamable HTTP MCP endpoints in web frameworks.

Maintenance / activity evidence

mcp-handler 2.2.0 published 2026-09-18T19:13:33.818Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Application-defined tool scope. Writes: Whatever registered tools can do.
Optional app-defined bearer auth
Sensitive access: Application data exposed by tools

A public MCP route can expose arbitrary application authority if authentication and tool scoping are omitted.

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

Popularity

682 repository stars · 4.8M package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

Does one handler preserve stateless discovery and legacy Streamable HTTP compatibility across supported frameworks?

The bounded review of the publisher's documented Fetch-compatible HTTP adapter for MCP server definitions and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

A public MCP route can expose arbitrary application authority if authentication and tool scoping are omitted.
Application-defined tool scope.
Optional app-defined bearer auth
Requests/tool data pass through the host application.
Reviewed write actions: Whatever registered tools can do
Sensitive access: Application data exposed by tools
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Authorization is application-defined and not enabled automatically.
The package is an adapter, not a hosted service.

Original activity observations

mcp-handler 2.2.0 published 2026-09-18T19:13:33.818Z

Technical identity

npm/mcp-handler

Exact implementation source: https://www.npmjs.com/package/mcp-handler ↗
Reviewed resource type: Gateway
Repository identity: vercel-labs/mcp-handler
Package identity: npm:mcp-handler
Service endpoint: Application-defined route

Evidence & Sources

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

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

Package registry ↗
mcp-handler
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
vercel-labs/mcp-handler
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No runtime server process, Docker setup, OAuth or credentials were executed during this research.
Retain SDK/integration classification. No standalone run command; do not invent an mcpServers stdio config.
Install documentation is not a guarantee of current package/runtime compatibility.
Verified MCP route handler library for applications; it is NOT a separate MCP server installed into Claude/Cursor. Requires Node.js 20+, MCP server SDK v2, Zod v4.
2026-10-13 targeted publisher npm README plus official repository/docs where specified; static research, not runtime test.
Never paste real credentials into a documentation example.
No live install, OAuth, paid calls, third-party mutation or credential revocation executed.
Some host removal commands are MCP100-composed based on chosen registration name, not publisher-authored.

Install / configure gateway or CLI
Publisher instructions
Publisher installation/integration method, not a generic MCP server.
Publisher setup example · Publisher instructions
npm install mcp-handler@^2 @modelcontextprotocol/server@^2 zod@^4
Configure / authenticate
MCP100 setup guide
Developer framework for mounting Streamable HTTP MCP handler in your application; implement route and auth; not a standalone server to add by name.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: Implement a framework application route using createMcpHandler according to the mcp-handler 2.x Quick Start; deploy/run the route, then connect MCP-capable clients to YOUR route URL using client-specific HTTP settings. No universal server spawn command exists.
Previously reviewed configuration / prerequisites: Requires Node.js 20+, MCP server SDK v2, Zod v4.
Check connection
Suggested check
Start your app and use MCP Inspector or client against your implemented endpoint; package install alone provides no endpoint.
Remove / uninstall / revoke
MCP100 setup guide
This is a framework / integration component, not a standalone server. Remove the app SDK/package or gateway config using the matching package manager; stop deployed processes separately. For the method installed globally, use `npm uninstall mcp-handler`.
The supplied npm uninstall command removes the project dependency (no -g flag). The source wording about a global install does not make this a global uninstall command.
Conditional host / package cleanup · MCP100 composed guide
npm uninstall mcp-handler

Official Documentation & Sources

What it does

A framework-agnostic Request/Response adapter for hosting Streamable HTTP MCP endpoints in web frameworks.

Capability: Developer Tools
Resource type: Gateway
Industry: Software & Technology
Best fit: Developers embedding MCP endpoints in Fetch-compatible JavaScript/TypeScript frameworks.

Representative uses

Mount MCP in Next.js/Nuxt/SvelteKit/Hono
Expose tools over Streamable HTTP
Add bearer verification
Publish protected-resource metadata

Limitations

Authorization is application-defined and not enabled automatically.
The package is an adapter, not a hosted service.

Reviewed access

Access & risk

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

Authentication: Optional app-defined bearer auth
Permissions: Application-defined tool scope.
Data handling: Requests/tool data pass through the host application.
Cost: free
Risk and cautions: A public MCP route can expose arbitrary application authority if authentication and tool scoping are omitted.

Access scope and cautions

Write actions: Whatever registered tools can do
Sensitive access: Application data exposed by tools
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Mount MCP in Next.js/Nuxt/SvelteKit/Hono; Expose tools over Streamable HTTP; Add bearer verification; Publish protected-resource metadata.

What setup and authentication are documented?

Recorded installation/entrypoint step: npm install mcp-handler@^2 @modelcontextprotocol/server@^2 zod@^4. Recorded transport: streamable_http. Prerequisites: Node.js 20+; Fetch-compatible framework. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Optional application-defined bearer verification via withMcpAuth.

Can it modify data or perform write operations?

Documented write actions include: Whatever registered tools can do. Recorded permission boundary: Application-defined tool scope.

What data-handling boundary should I consider?

Requests/tool data pass through the host application. Recorded sensitive-access context: Application data exposed by tools.

What limitations and risks should I check before use?

A public MCP route can expose arbitrary application authority if authentication and tool scoping are omitted. Authorization is application-defined and not enabled automatically. The package is an adapter, not a hosted service. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Vercel is listed as First-party MCP in MCP100’s current evidence.