Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ExtractEdge

REMOTE · EXTRACTEDGE.LASTUNMIHAI1986.WORKERS.DEV · SCANNED SEP 20

Any web page -> clean markdown. Firecrawl-lite, 0.001 USDC/extract (x402, Base), free demo.

18 Trust /100
Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the ExtractEdge MCP server?

ExtractEdge is a hosted endpoint at https://extractedge.lastunmihai1986.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 · extractedge.lastunmihai1986.workers.dev

# add to Claude Code
claude mcp add --transport http vasilicasijarvis-extractedge 'https://extractedge.lastunmihai1986.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "vasilicasijarvis-extractedge": {
      "url": "https://extractedge.lastunmihai1986.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vasilicasijarvis-extractedge": {
      "type": "http",
      "url": "https://extractedge.lastunmihai1986.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.vasilicasijarvis-extractedge]
url = "https://extractedge.lastunmihai1986.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vasilicasijarvis-extractedge": {
      "type": "remote",
      "url": "https://extractedge.lastunmihai1986.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vasilicasijarvis-extractedge --url 'https://extractedge.lastunmihai1986.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  vasilicasijarvis-extractedge:
    url: "https://extractedge.lastunmihai1986.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vasilicasijarvis-extractedge": {
      "Transport": "http",
      "Url": "https://extractedge.lastunmihai1986.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add vasilicasijarvis-extractedge -t streamable-http -u 'https://extractedge.lastunmihai1986.workers.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "vasilicasijarvis-extractedge": {
      "type": "http",
      "url": "https://extractedge.lastunmihai1986.workers.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 −42
    • Endpoint reachability: reachable → not serving MCP security
    • HTTPS: fail → unverified security
    • Stability: 0.07 → unverified security
    • Tool safety: pass → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 18 Sept 26 +1
    • Stability: unverified → 0.03 functional
  • 17 Sept 26 59

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://extractedge.lastunmihai1986.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=lastunmihai1986.workers.dev CN=YE2,O=Let's Encrypt,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA384 68ab07d6d9076a6736c3a53c00e510ab4c1
SANs: *.lastunmihai1986.workers.dev, lastunmihai1986.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of extractedge.lastunmihai1986.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 404
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://extractedge.lastunmihai1986.workers.dev/mcp HTTP error 404
http (plaintext) http://extractedge.lastunmihai1986.workers.dev/mcp Inconclusive 404
MCP tools · 1 exposed · ~133 tokens

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 →

Tool Tokens
extract ~133

Extract clean markdown (or plain text) content from any public web page URL. Firecrawl-lite: fetches the page, strips ads/nav/scripts, converts the main content to markdown with metadata (title, description, links). Paid via x402 USDC on Base (0.001 USDC/extract) — or free with {demo: true} (limited to 3000 chars).

NameTypeReqDescription
demobooleanSet true for a free capped preview (3000 chars)
formatstringOutput format (default markdown)
urlstringyesThe http(s) URL of the page to extract

No output schema declared.

No examples provided.

Common questions

What is the ExtractEdge MCP server?

ExtractEdge is an MCP server listed in the public MCP registry as io.github.vasilicasijarvis/extractedge. Any web page -> clean markdown. Firecrawl-lite, 0.001 USDC/extract (x402, Base), free demo. This page covers its hosted endpoint (https://extractedge.lastunmihai1986.workers.dev/mcp).

Is the ExtractEdge MCP server safe to use?

ExtractEdge scores 18 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 ExtractEdge MCP server expose?

ExtractEdge exposes 1 tool: extract. Their descriptions and schemas cost roughly 133 tokens of context every time the server is loaded.

Does the ExtractEdge MCP server require authentication?

No. We connected to ExtractEdge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ExtractEdge MCP server still maintained?

ExtractEdge is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.