Other · Remote MCP server
Intent-Verified Development (IVD)
33 tools that make AI write, implement, and verify intent against explicit, testable constraints.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.leocelis/ivd- Version
- 3.1.2
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-22
- Updated
- 2026-07-22
- Publisher
- leocelis (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/leocelis) · how
- Website
- ivdframework.dev
- Repository
- github.com/leocelis/ivd
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.ivdframework.dev/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Intent-Verified Development (IVD)
Intent-Verified Development (IVD) is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.ivdframework.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {api_key}.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from leocelis (GitHub)
| Server | Runs |
|---|---|
| Horizon Fidelity MonitorTracks conversation health in real time - drift, desync, and causal collapse - for any AI agent. | Remote · SSELive check: sign-in required |
More other servers
| Server | Runs |
|---|---|
| IntenCheckPsychological text analysis: tone, emotions, communication style, multilingual replies. | Remote · HTTPLive check: sign-in required |
| IntendedIntended's authority layer as MCP tools: ALLOW/ESCALATE/DENY decisions with signed tokens. | Local · stdio |
| Intent EngineeringAudit, scaffold, and triage agent intent specs against a 9-section template. | Local · stdio |
| Intent HubBook a local business by saying what you need; matching businesses bid and you confirm one. | Remote · HTTPLive check: ✓ handshake |
| IntentFence Agent Action FirewallFail-closed action authorization, MCP risk scanning, x402 checks, and signed receipts. | Remote · HTTPLive check: ✓ handshake |
| Intentions MCP ServerPersonalized timing intelligence for AI agents - ask 'should I do X on this date?'. | Remote · HTTPLive check: ✓ handshake |
| InterAI Risk OraclePre-execution policy gate for consequential agent actions with durable trust receipts. | Remote · HTTPLive check: ✓ handshake |
| InterbankingSaldos y movimientos bancarios de Interbanking (Argentina). Solo lectura. | Local · stdio |