Intent-Verified Development (IVD) MCP Server

by leocelis Your server? Claim it

answering

Intent-Verified Development (IVD) is answering right now. Last checked 2 min ago. Last commit 8 Sep 2026.

33 tools that make AI write, implement, and verify intent against explicit, testable constraints.

Uptime history 48 days of history · worst day 98%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

610 ms

Response time

average over 24h

Stars

last commit 8 Sep 2026

What the code does

We read the source, 1 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command canon/validation/validate_mcp.py:63, mcp_server/tools/run_constraint_tests.py:88

        self._proc = subprocess.Popen(

Page executes code built at runtime index.html:1399

        slot.innerHTML = t;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ivd --transport http https://mcp.ivdframework.dev/mcp

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

{
  "mcpServers": {
    "ivd": {
      "url": "https://mcp.ivdframework.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.ivd]
url = "https://mcp.ivdframework.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "ivd": {
      "url": "https://mcp.ivdframework.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "ivd": {
      "url": "https://mcp.ivdframework.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.ivdframework.dev/mcp	streamable-http	needs auth	702 ms	2 min ago

Alternatives to Intent-Verified Development (IVD)

same job, measured the same way

MCP Appium - Mobile Development and Automation Server

by appium

MCP server for Appium mobile automation on iOS and Android devices with test creation tools.

6 543 installs/wk local only

R Packagedev MCP

by b0ydt

MCP server for R package development using usethis, devtools, renv, and testthat

42 installs/wk local only

Wechat Devtools MCP

by watertian

MCP Server for WeChat DevTools CLI - Automate development & testing with 7 aggregated APIs.

1 192 installs/wk local only

replicant-mcp

by thecombatwombat

Android MCP server for AI-assisted development. Build, test, emulate, and automate.

121 installs/wk local only

Otterkit

by useotterkit

Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.

117 installs/wk local only

Simple MCP Server

by ormastes

Simple Language MCP server — code intelligence, debugging, build, test, and VCS tools

58 installs/wk local only

Wechat Devtools

by watertian

MCP Server for WeChat DevTools CLI - Automate Mini Program development & testing.

local only

.NET MCP Server

by jongalloway

AI assistant access to .NET SDK for projects, packages, building, testing, and development tools.

local only

Intent-Verified Development (IVD) — questions

Answers built from our own checks of this server.

Why is there no tool list for Intent-Verified Development (IVD)?

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 Intent-Verified Development (IVD) 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 610 ms. The bar chart above shows every period we have measured.

How do I connect Intent-Verified Development (IVD)?

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 credentials: it refuses anonymous clients.

Does Intent-Verified Development (IVD) need an API key?

Yes. Every time we knock, Intent-Verified Development (IVD) 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 Intent-Verified Development (IVD)?

It answers our handshake in 610 ms on average, which is faster than 21% 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.

Is Intent-Verified Development (IVD) open source?

Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.