Developer · Remote MCP server
Veridu
Multi-reviewer AI code review: surfaces findings the reviewers agree on, disputes flagged.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.michaelw-pr/veridu- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-14
- Updated
- 2026-09-14
- Publisher
- michaelw-pr (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/michaelw-pr) · how
- Website
- veridu.io
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.veridu.io/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; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Veridu
Veridu is a remote MCP server: there is nothing to install. Its endpoint is https://api.veridu.io/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 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 michaelw-pr (GitHub)
| Server | Runs |
|---|---|
| Presentr AnalyzePodcast and media analysis: transcripts, captions, chapters, ad markers and show notes. | Remote · HTTPLive check: sign-in required |
More developer servers
| Server | Runs |
|---|---|
| Verdict - Compliance for AI-Generated CodeCompliance verdicts for AI-generated code. SOC 2, HIPAA, HITRUST for healthcare IT. | Local · stdio |
| Verdict MCPSandboxed test runs for coding agents: compact typed verdicts with failure fingerprints and history. | Local · stdio |
| VerdocDeterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402. | Local · stdio |
| Veredicto HumanoAsk a real human (not an LLM) for a judgment, $0.10 USDC via x402. The result returns to the agent. | Remote · HTTPLive check: ✓ handshake |
| Verifactu MCPMCP server para VeriFactu (AEAT). Facturación electrónica española desde Claude Code. | Local · stdio |
| verifiable-claim-seedZero-dependency verifiable-claims MCP: validate safely, verify with allow_execution, self-test. | Local · stdio |
| Verificate MCPAgentic code review, no signup to try: reality gates + frontier-model review, with veto. | Remote · HTTPLive check: ✓ handshake |
| Verified Ai Free TiersVerified AI free tiers plus source-backed agent and MCP discovery monitoring. | Remote · HTTPLive check: ✓ handshake |