Evercraft Web

io.github.jgaethle10Published by GitHub account jgaethle10v0.1.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant read public web content, with search and browser automation held behind safety gates.

What you can do
Read public web content through the Evercraft gateway, so an assistant can pull in material from the open web while answering or working on a task. Search and browser automation are described as staying behind safety gates, so those capabilities may be limited or unavailable depending on how the service is configured. No tool list is published, so the exact set of actions an assistant can take is not documented here.
When to use it
Worth considering when an assistant mainly needs to read public web pages and you want a hosted endpoint rather than a local package. Less suitable if you need documented search or browser-control tools, since those are gated and unspecified.
Requirements
A remote streamable HTTP connection to the provider's endpoint at base44.app. No packages, environment variables, headers or authentication are declared, and no account setup is documented.
Before you install
The endpoint is hosted by a third party, so any content the assistant reads passes through that service. Search and browser automation are gated, and the gate conditions are not described. No tool list or privacy details are published, so review the provider's terms before relying on it.

Installation

In SourceWeft

  1. Open Evercraft Web in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.jgaethle10%2Fevercraft-web/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "evercraft-web": {
      "type": "http",
      "url": "https://base44.app/api/apps/692b4178919afe7d08c4d2b8/functions/evercraftWebMcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v0.1.1LatestSep 25, 2026
  2. v0.1.0Sep 24, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.