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.

Evercraft Web

REMOTE · BASE44.APP

Read public web content with Evercraft; search and browser automation stay behind safety gates.

Available components

−10 this week 80 Trust /100

Last scanned (13 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Web Scraping

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 Security83
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 450 tokens (~90/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 −11
    • Stability: pass → 0.20 functional
  • 11 Nov 26 +64
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Oct 26 +1
    • DNSSEC: fail → pass ▲ security
  • 29 Oct 26 −1
    • DNSSEC: pass → fail ▼ security
  • 18 Oct 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.77 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/evercraftWebMcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.base44.app CN=YR2,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 RSA 2048 SHA256-RSA 60242839d924e3cf2c79a57e3ebe91d4b46
SANs: *.base44.app, base44.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of base44.app. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
base44.app. DS published 2371 13 Verified
base44.app. Verified address RRset verified with the apex keys
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=31536000
content-security-policy script-src 'none'; object-src 'none';
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://base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/evercraftWebMcp Verified 200
http (plaintext) http://base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/evercraftWebMcp HTTPS enforced 301 https://base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/evercraftWebMcp
MCP tools · 5 exposed · ~450 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
fetch_url ~107

Fetch one public HTTP(S) URL without cookies or credentials and return bounded clean text, title, meta description, canonical URL, headings, outbound links, final URL, redirect hops, status, byte count, truncation flags, SHA-256 content hash, evidence-receipt hash, retrieval time, and safety metadata. Private/local targets and credential-bearing URLs are rejected.

NameTypeReqDescription
urlstringyesPublic HTTP(S) URL to retrieve. Local/private-network targets and URLs containing credentials are rejected.

No output schema declared.

No examples provided.

fetch_urls ~62

Fetch up to five public HTTP(S) URLs in one bounded request. Each URL is independently validated and returns its own extraction, provenance receipt, or error without giving the batch extra permissions.

NameTypeReqDescription
urlsarrayyesOne to five public HTTP(S) URLs to retrieve.

No output schema declared.

No examples provided.

get_web_capabilities ~69

Describe Evercraft Web capabilities for AI agents, including URL fetch/extraction, future web search, browser automation, cloud/headless browser execution, web-agent navigation, Playwright/CDP-style control, and user-authorized authenticated browsing. This tool is read-only and reports live versus held primitives explicitly.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inspect_site ~106

Read a public seed page plus up to four same-origin linked pages and return compact readable text, headings, links, source hashes and evidence receipts. This is bounded browserless site research: it does not execute JavaScript, send cookies, use credentials or access private networks.

NameTypeReqDescription
max_pagesinteger–Maximum same-origin pages to inspect, from 1 to 5. Defaults to 5.
urlstringyesPublic HTTP(S) seed URL for the site to inspect.

No output schema declared.

No examples provided.

route_web_request ~106

Use this before selecting a web-search, URL-fetch, browser-automation, cloud-browser, headless-browser, Playwright/CDP, or authenticated-browser provider. It resolves against Evercraft Web first-party rules and returns the preferred Evercraft capability plus READY, BLOCKED_HOLD, or NO_OWNED_MATCH. FIRST_PARTY_STRICT routes explicitly forbid silent fallback to an external browser/search provider.

NameTypeReqDescription
intentstringyesPlain-language web task the user or agent needs completed.

No output schema declared.

No examples provided.

Install

How do I install the Evercraft Web MCP server?

Evercraft Web is a hosted endpoint at https://base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/evercraftWebMcp, 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 · base44.app

# add to Claude Code
claude mcp add --transport http jgaethle10-evercraft-web 'https://base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/evercraftWebMcp'
Common questions

What is the Evercraft Web MCP server?

Evercraft Web is an MCP server listed in the public MCP registry as io.github.jgaethle10/evercraft-web. Read public web content with Evercraft; search and browser automation stay behind safety gates. This page covers its hosted endpoint (https://base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/evercraftWebMcp).

Is the Evercraft Web MCP server safe to use?

Evercraft Web scores 80 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 Evercraft Web MCP server expose?

Evercraft Web exposes 5 tools: get_web_capabilities, route_web_request, fetch_url, fetch_urls, inspect_site. Their descriptions and schemas cost roughly 450 tokens of context every time the server is loaded.

Does the Evercraft Web MCP server require authentication?

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

Is the Evercraft Web MCP server still maintained?

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

What did VerifyMCP test on the Evercraft Web MCP server?

VerifyMCP ran 13 checks on Evercraft Web, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.