org.echoempire/web-tools
REMOTE · ECHOEMPIRE-WEB-TOOLS-MCP.ECHOEMPIRE-IN-CO.WORKERS.DEV
Web extraction MCP: page content, metadata, articles, contacts, email checks, URL probes.
Available components
Last scanned (9 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 805 tokens (~134/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
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 7 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-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Server version: 1.0.0 → 1.1.0 functional
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 63
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 5 Nov 2026 · Probed https://echoempire-web-tools-mcp.echoempire-in-co.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=echoempire-in-co.workers.dev | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ee68b0f3c65cc8301301b27d36b56800 |
| SANs: echoempire-in-co.workers.dev, *.echoempire-in-co.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of echoempire-web-tools-mcp.echoempire-in-co.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://echoempire-web-tools-mcp.echoempire-in-co.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://echoempire-web-tools-mcp.echoempire-in-co.workers.dev/mcp | Inconclusive | 405 |
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 →
extract_article extract article ~125
Extract structured article data: title, author, published date, clean body text, word count and content hash. Failed URLs are not billed. Runs Apify Actor skilled_glee/article-text-extractor on YOUR Apify account (pay-per-event $0.001/article, billed by Apify).
| Name | Type | Req | Description |
|---|---|---|---|
| apify_token | string | – | Optional Apify API token if your MCP client cannot send the Authorization / X-Apify-Token header. |
| articleUrls | array | yes | Static article URLs (duplicates processed once). |
| maxChars | integer | – | Max content characters per article. |
No output schema declared.
No examples provided.
extract_contact_details extract contact details ~121
Extract emails (incl. mailto), North American phone numbers, LinkedIn/X/Facebook/Instagram/YouTube links and contact/about/team page links from web pages. Runs Apify Actor skilled_glee/contact-details-extractor on YOUR Apify account (pay-per-event $0.0015/page, billed by Apify).
| Name | Type | Req | Description |
|---|---|---|---|
| apify_token | string | – | Optional Apify API token if your MCP client cannot send the Authorization / X-Apify-Token header. |
| pageUrls | array | yes | Web page URLs to extract contact details from. |
No output schema declared.
No examples provided.
extract_web_metadata extract web metadata ~118
Extract title, meta description, Open Graph, Twitter Card, JSON-LD structured data, canonical URL, language and H1s from web pages as JSON. Runs Apify Actor skilled_glee/web-metadata-extractor on YOUR Apify account (pay-per-event $0.001/page, billed by Apify).
| Name | Type | Req | Description |
|---|---|---|---|
| apify_token | string | – | Optional Apify API token if your MCP client cannot send the Authorization / X-Apify-Token header. |
| pageUrls | array | yes | Web page URLs to extract metadata from. |
No output schema declared.
No examples provided.
extract_website_content extract website content ~139
Fetch web pages and return clean readable text (boilerplate, nav and ads stripped), title, description, word count and language. Deterministic, no AI, no browser. Runs Apify Actor skilled_glee/website-content-extractor on YOUR Apify account (pay-per-event $0.002646/page, billed by Apify).
| Name | Type | Req | Description |
|---|---|---|---|
| apify_token | string | – | Optional Apify API token if your MCP client cannot send the Authorization / X-Apify-Token header. |
| maxChars | integer | – | Max content characters per page. |
| pageUrls | array | yes | Web page URLs to extract readable content from. |
No output schema declared.
No examples provided.
probe_urls probe urls ~138
Check URLs with HEAD or GET: HTTP status, final URL after redirects, redirect count, Content-Type and timing. No page body is read. Runs Apify Actor skilled_glee/http-url-probe on YOUR Apify account (pay-per-event $0.0004/URL, billed by Apify).
| Name | Type | Req | Description |
|---|---|---|---|
| apify_token | string | – | Optional Apify API token if your MCP client cannot send the Authorization / X-Apify-Token header. |
| followRedirects | boolean | – | – |
| method | string | – | – |
| timeoutSecs | integer | – | – |
| urls | array | yes | Absolute http(s) URLs to probe. |
No output schema declared.
No examples provided.
verify_emails verify emails ~127
Check email addresses without sending mail: syntax, MX, null MX, disposable domains, role accounts, free providers and common typos, with a pass/risky/fail verdict and reason codes. Runs Apify Actor skilled_glee/email-verifier on YOUR Apify account (pay-per-event $0.001/email, billed by Apify).
| Name | Type | Req | Description |
|---|---|---|---|
| apify_token | string | – | Optional Apify API token if your MCP client cannot send the Authorization / X-Apify-Token header. |
| emails | array | yes | Email addresses to check (max 100 per call via MCP). |
No output schema declared.
No examples provided.
How do I install the org.echoempire/web-tools MCP server?
org.echoempire/web-tools is a hosted endpoint at https://echoempire-web-tools-mcp.echoempire-in-co.workers.dev/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 · echoempire-web-tools-mcp.echoempire-in-co.workers.dev
claude mcp add --transport http org-echoempire-web-tools 'https://echoempire-web-tools-mcp.echoempire-in-co.workers.dev/mcp'
What is the org.echoempire/web-tools MCP server?
org.echoempire/web-tools is an MCP server listed in the public MCP registry as org.echoempire/web-tools. Web extraction MCP: page content, metadata, articles, contacts, email checks, URL probes. This page covers its hosted endpoint (https://echoempire-web-tools-mcp.echoempire-in-co.workers.dev/mcp).
Is the org.echoempire/web-tools MCP server safe to use?
org.echoempire/web-tools scores 66 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 org.echoempire/web-tools MCP server expose?
org.echoempire/web-tools exposes 6 tools: extract_website_content, extract_web_metadata, extract_article, extract_contact_details, verify_emails, probe_urls. Their descriptions and schemas cost roughly 768 tokens of context every time the server is loaded.
Does the org.echoempire/web-tools MCP server require authentication?
No. We connected to org.echoempire/web-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the org.echoempire/web-tools MCP server still maintained?
org.echoempire/web-tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.