mcpbeat Sign in

Lediv MCP Server

answering

Lediv is answering right now. Last checked moments ago.

Visual website builder synced with real code. Build, publish and maintain websites from any agent.

Uptime history 32 hours of history · worst hour 50%
32 hours agonow
98.9%
Uptime 24h
90 of 91 checks
Tools
hidden behind auth
369 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Lediv does not always answer

Over the last week it answered 97.4% 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 0 min ago.

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

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://lediv.app/mcp streamable-http sign-in 327 ms 0 min ago

Alternatives to Lediv

same job, measured the same way
Zarla Website Builder
by zarla

Build, edit and publish websites from Claude, ChatGPT, Cursor and Gemini. No code — Zarla hosts it.

answering
tdmcp — TouchDesigner MCP server
by pantani

Build real visual systems in TouchDesigner from plain language with Claude, Cursor or Codex.

112 installs/wk local only
Carryo Website Publisher
by carryo

Publish and update HTML websites, landing pages, reports and proposals from AI chat. OAuth sign-in.

12 tools answering
Cdbx
by cdbx

Build Apps and run code in 30 languages — sandboxed, with persistent sessions for agent loops.

answering
C
Convika
by convika

Create, preview, publish, and measure landing pages from Claude, Codex, or any MCP client.

answering
Draw2agent
by zero-abd

Draw on your website, let your AI agent see it. Visual context for code generation via MCP.

31 installs/wk local only
Claude Handoff
by vasilispapg

Session handoff for Claude Code: list sessions and build handoff docs another agent continues from.

887 installs/wk local only
Yocoolab
by jonahbkerr

Pin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent.

40 installs/wk local only

Lediv — questions

Answers built from our own checks of this server.

Why is there no tool list for Lediv?
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 Lediv working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 369 ms. The bar chart above shows every period we have measured.
How do I connect Lediv?
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 Lediv?
No API key is involved. Lediv 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 Lediv?
It answers our handshake in 369 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.