Developer · Remote MCP server
webEmbedding
Source-first URL clone, capture, rebuild, and fidelity verification tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jongko54/web-embedding- Version
- 0.3.8
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-05-21
- Updated
- 2026-05-21
- Publisher
- jongko54 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jongko54) · how
- Website
- github.com/jongko54/webEmbedding#readme
- Repository
- github.com/jongko54/webEmbedding
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://webembedding-mcp.vercel.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 402)
- Handshake
- HTTP 402
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | web-embedding | 0.3.8 | stdio |
How to connect webEmbedding
webEmbedding is a remote MCP server: there is nothing to install. Its endpoint is https://webembedding-mcp.vercel.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: web-embedding version 0.3.8. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y web-embedding@0.3.8.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"web-embedding": {
"command": "npx",
"args": [
"-y",
"web-embedding@0.3.8"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| WebcheckWebsite health analysis: SEO, accessibility, performance, security, and broken links. | Local · stdio |
| Webcomponents React MCP ServerMCP server for UI5 Web Components for React - Developer documentation and API assistance. | Local · stdio, HTTP |
| WebDAV MCPZero-dependency WebDAV MCP server - single static binary, no Node.js or Python. 8 tools via stdio. | Local · stdio |
| webdriverio MCPMCP server with WebdriverIO for browser and mobile app automation (iOS/Android via Appium) | Local · stdio |
| webfetchSelf-hosted web search for LLM agents: search -> fetch -> rank pipeline with semantic caching. | Local · stdio |
| Webhook AdminSend, retry and monitor webhooks: manage endpoints, event types and API keys (OAuth). | Remote · HTTPLive check: sign-in required |
| Webhook Ai MCPWebhook Ai tools for AI agents. Capabilities: validate webhook signature, log webhook event, replay. | Local · stdio |
| Webhook Signature Fixture LabGenerates deterministic webhook HMAC-SHA256 fixtures and optionally verifies a supplied signature... | Remote · HTTPLive check: ✓ handshake |