WeAD

io.github.Kennethlee83Published by GitHub account Kennethlee83v1.0.0Updated Oct 25, 2026

Read-only info on WeAD apps, status, abstracts and public documents.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

A read-only remote MCP server that gives an assistant access to public WeAD information: app listings, live-versus-roadmap status, and open research documents.

What you can do
List WeAD apps with their stage (Live, Beta, Alpha, Coming 2027) and link, and read the status surface showing what is live versus early or roadmap. List the open WeAD research documents, such as theoretical abstracts, the mission map, the pact and the verification guide. Read a single open document by name, and search the open documents for a word or phrase to get matching passages.
When to use it
Useful when an assistant needs to answer questions about WeAD, its apps or its published research, and should ground claims about what is actually live in the server's status data rather than guesswork.
Requirements
A remote streamable HTTP endpoint at wead.live; no packages, environment variables or headers are declared, and no authentication is declared.
Before you install
The server is read-only and exposes only public material, so no writes or deletions are involved. Content comes from a third party, so treat app stages and document text as the provider's own claims rather than verified fact.

Installation

In SourceWeft

  1. Open WeAD 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.Kennethlee83%2Fwead/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": {
    "wead": {
      "type": "http",
      "url": "https://wead.live/mcp"
    }
  }
}

Tools

5

list_apps

List every WeAD app with its stage (Live, Beta, Alpha, Coming 2027) and link.

Parametersstage

get_status

WeAD's truth surface: what is actually live versus early or roadmap. Read this before making claims about WeAD.

Takes no parameters.

list_documents

List the open WeAD research documents (theoretical abstracts, mission map, the pact, verification guide).

Takes no parameters.

get_document

Read one open WeAD document by name, as returned by list_documents.

Parametersnamerequired

search_documents

Search the open WeAD documents for a word or phrase; returns matching passages.

Parametersqueryrequired

Version history

1
  1. v1.0.0LatestOct 25, 2026

Score

83% 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
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.