webEmbedding
REMOTE · WEBEMBEDDING-JONGKOS-MCP.VERCEL.APP · 2 COMPONENTS
Clone any web page from a URL into a verified offline HTML copy, embed, or rebuild.
Available components
Last scanned (21 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 485 tokens (~69/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 69
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 4 Nov 2026 · Probed https://webembedding-jongkos-mcp.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of webembedding-jongkos-mcp.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://webembedding-jongkos-mcp.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://webembedding-jongkos-mcp.vercel.app/mcp | HTTPS enforced | 308 | https://webembedding-jongkos-mcp.vercel.app/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
classify_clone_mode Classify Clone Mode ~71
Decide whether a reference should be embedded, sourced, locally captured, bounded-rebuilt, or blocked before reproduction.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | – |
| exact_requested | boolean | – | – |
| license_text | string | – | – |
| site_profile | object | – | – |
| source_signals | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
detect_runtime_capabilities Detect Hosted Runtime Capabilities ~32
Report hosted Apps SDK readiness, read-only runtime capabilities, unsupported capture behavior, and the local stdio command.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
discover_embed_candidates Discover Embed Candidates ~46
Extract likely embed, preview, viewer, remix, and source URLs from a public or user-authorized page.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_seconds | integer | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
generate_embed_snippet Generate Embed Snippet ~52
Generate an iframe snippet for a known frameable and authorized URL. Does not verify frameability by itself.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | – |
| title | string | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
inspect_url Inspect URL Reuse Route ~54
Fetch a public or user-authorized URL and inspect title, metadata, frame policy, and likely source/embed candidates. Does not capture screenshots or persist artifacts.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_seconds | integer | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
plan_reproduction_path Plan Reproduction Path ~77
Create a source-first plan that separates exact embed/source reuse from local capture and bounded rebuild work.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | – |
| capture_bundle | object | – | – |
| exact_requested | boolean | – | – |
| license_text | string | – | – |
| site_profile | object | – | – |
| source_signals | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the webEmbedding MCP server?
webEmbedding is a hosted endpoint at https://webembedding-jongkos-mcp.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · webembedding-jongkos-mcp.vercel.app
claude mcp add --transport http jongko54-web-embedding 'https://webembedding-jongkos-mcp.vercel.app/mcp'
What is the webEmbedding MCP server?
webEmbedding is an MCP server listed in the public MCP registry as io.github.jongko54/web-embedding. Clone any web page from a URL into a verified offline HTML copy, embed, or rebuild. This page covers its hosted endpoint (https://webembedding-jongkos-mcp.vercel.app/mcp).
Is the webEmbedding MCP server safe to use?
webEmbedding scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the webEmbedding MCP server expose?
webEmbedding exposes 6 tools: detect_runtime_capabilities, inspect_url, discover_embed_candidates, classify_clone_mode, generate_embed_snippet, plan_reproduction_path. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.
Does the webEmbedding MCP server require authentication?
No. We connected to webEmbedding without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the webEmbedding MCP server still maintained?
webEmbedding is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.