WeAD MCP

A read-only MCP server for the WeAD ecosystem that allows AI agents to list applications, check system status, and retrieve or search public documents and abstracts.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-01Published by Kenneth Lee

MCP endpoint (Streamable HTTP)

https://wead.live/mcp

Vendor documentation

What you can do with it

List available WeAD applications
Get current system status
Search public documents
Retrieve specific document content

Source and maintenance

Community listingRegistry 1.0.0

mcp-registry: io.github.Kennethlee83/wead@1.0.0 Project website

Protocol and capabilities

Server: wead-live 1.0.0
MCP protocol: 2025-06-18
Tools: 5 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Read-only public information about WeAD and its apps. Use get_status before making claims about what is live.

Tools

5 advertised

list_apps

Advertised by the server during the last successful anonymous check.

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

list_apps input schema

{
  "type": "object",
  "properties": {
    "stage": {
      "type": "string",
      "description": "Optional filter: Live, Beta, Alpha or Coming 2027"
    }
  }
}

get_status

Advertised by the server during the last successful anonymous check.

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

get_status input schema

{
  "type": "object",
  "properties": {}
}

list_documents

Advertised by the server during the last successful anonymous check.

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

list_documents input schema

{
  "type": "object",
  "properties": {}
}

get_document

Advertised by the server during the last successful anonymous check.

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

get_document input schema

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    }
  }
}

search_documents

Advertised by the server during the last successful anonymous check.

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

search_documents input schema

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 516 ms
95th percentile latency: 516 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 1, 2026, 9:09 AM UTC · probe · passed · 516 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http wead-mcp https://wead.live/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add wead-mcp --url https://wead.live/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable wead-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "wead-mcp": {
      "url": "https://wead.live/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "wead-mcp": {
      "type": "streamableHttp",
      "url": "https://wead.live/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start wead-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "wead-mcp": {
      "type": "http",
      "url": "https://wead.live/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http wead-mcp https://wead.live/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "wead-mcp": {
      "url": "https://wead.live/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "wead-mcp": {
      "serverUrl": "https://wead.live/mcp"
    }
  }
}

Let your agent find its tools

Find servers like WeAD MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows