mcpbeat Sign in

Weft MCP Server

answering

Weft is answering right now. Last checked 13 min ago.

A shared Scrumban board for humans and AI agents: leases, receipts, verification, a review Inbox.

Uptime history 20 days of history · worst day 87%
20 days agonow
98.9%
Uptime 24h
91 of 92 checks
Tools
hidden behind auth
380 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Weft does not always answer

Over the last week it answered 98.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add weft --transport http https://letsweft.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "weft": {
      "url": "https://letsweft.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.weft]
url = "https://letsweft.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "weft": {
      "url": "https://letsweft.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "weft": {
      "url": "https://letsweft.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://letsweft.com/api/mcp streamable-http needs key 319 ms 13 min ago

Alternatives to Weft

same job, measured the same way
Agenticmail
by agenticmail

Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.

442 installs/wk local only
Tango
by applayer

Shared task queue for humans and AI agents: leases, handoffs, approvals and signed receipts.

81 tools answering
C
Vigil — an outside witness for AI agents
by vigilnotary

Agent leases, signed receipts, watchdogs, and optional paid source-verification evidence.

26 tools answering
N
Glyt
by glyt

Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.

6 tools answering
Machine Inbox
by machineinbox

Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.

11 tools answering
I
TookEffect
by tookeffect

Independent effect verification and signed receipts for consequential AI agent actions.

answering
Fairseal MCP Server
by ned-del

Verifiable entropy, provably-fair games, and receipt verification for AI agents (FairSeal API).

52 installs/wk local only
MCP Gera Verify
by gera

Verify UK businesses (FSA/CQC) + signed attestations, mandates & receipts for AI agents.

12 installs/wk local only

Weft — questions

Answers built from our own checks of this server.

Why is there no tool list for Weft?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.
Is Weft working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 380 ms. The bar chart above shows every period we have measured.
How do I connect Weft?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Weft?
No API key is involved. Weft answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Weft?
It answers our handshake in 380 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.