WeInc MCP Server

io.github.umairalisadaqat/weinc

answering

WeInc is answering right now. Last checked 3 min ago.

Manage WeInc AI website builder orgs: projects, publishing, custom domains, and previews.

Uptime history 27 hours of history

27 hours agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

623 ms

Response time

average over 24h

API key or OAuth

Access

streamable-http

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add weinc --transport http https://my.we.inc/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "weinc": {
      "url": "https://my.we.inc/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.weinc]
url = "https://my.we.inc/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "weinc": {
      "url": "https://my.we.inc/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "weinc": {
      "url": "https://my.we.inc/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

URL	Transport	State	Latency	Checked
https://my.we.inc/api/mcp	streamable-http	needs key	870 ms	3 min ago

Alternatives to WeInc

same job, measured the same way

WebCake Storefront

io.github.vuluu2k/webcake-storefront-mcp

Build pages and manage products, orders, and content on the WebCake/StoreCake storefront builder.

42 installs/wk answering

Lindo AI

io.github.lindoai/mcp-server

Create and manage Lindo AI websites, pages, blogs, clients, and credits from any MCP client.

40 installs/wk answering

Shipyard

app.goshipyard/shipyard

Ship, discover and review vibe-coded projects on Shipyard, the invite-only feed for AI-built apps.

9 tools answering

SocialBu MCP

io.github.usamaejaz/socialbu-mcp

Manage SocialBu posts, scheduling, publishing, automations, and analytics from MCP clients.

answering

Project Management Validation

io.github.antnewman/pm-validate

Validate project data against NISTA standards, scheduling best practices, and custom rules

110 installs/wk local only

Productised

io.github.Writehand-AI/productised

Build and publish AI products for coaching practices from inside Claude. 16 live tools.

local only

Power Automate MCP Server by Flow Studio

io.github.ninihen1/flowstudio-mcp

Debug, build, and manage Power Automate cloud flows with AI agents

33 tools answering

Kiosk Builder

io.github.pirumpi/kiosk-builder

Build and manage airline self-service kiosk apps — styling, pages, CMS, and CUSS2.

answering

WeInc — questions

Answers built from our own checks of this server.

Why is there no tool list for WeInc?

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: 100.0% of checks in the last 24 hours got a reply.

Is WeInc working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 623 ms. The bar chart above shows every period we have measured.

How do I connect WeInc?

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 will need your own key or an OAuth login: it refuses anonymous clients.

Does WeInc need an API key?

Yes. Every time we knock, WeInc answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is WeInc?

It answers our handshake in 623 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.