Other · Remote MCP server
Vizier
Deterministic authorization for one proposed AI agent action, returned with a signed receipt.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.vassiliylakhonin/vizier- Version
- 0.5.6
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- vassiliylakhonin (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/vassiliylakhonin) · how
- Website
- vizier.vassiliy-lakhonin.workers.dev/docs
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://vizier.vassiliy-lakhonin.workers.dev/mcp | Authorization (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 200)
- Handshake
- vizier 0.5.6 · protocol 2025-06-18
- Tools discovered
- 1:
vizier_verify_action - Checked on
- 2026-10-05
How to connect Vizier
Vizier is a remote MCP server: there is nothing to install. Its endpoint is https://vizier.vassiliy-lakhonin.workers.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 registry entry declares an HTTP header for the connection: Authorization (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 vassiliylakhonin (GitHub)
| Server | Runs |
|---|---|
| Agenda Intelligence MDEvidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Vizier GuardDeterministic authorization and security guard for AI agent actions with signed receipts. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| VisualSpecStructured, constraint-aware visual generation and deterministic layout for AI agents. | Local · stdio |
| VITNA - Agent Compliance PreflightPre-action compliance for AI agents: allow, block or hold. 24 statutes, 13 jurisdictions. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| VIVATLASSelf-hosted catalogue of your skills, agents and MCP servers, searchable by meaning over MCP. | Local · HTTP |
| VivescaOpinionated MCP server - Pydantic output schemas, 7 domains, built to evolve. | Local · stdio |
| viznoirCinema-quality science visualization for AI agents - headless VTK via MCP. | Local · stdio |
| VkVK (VKontakte): read walls, users, communities and stats; publish, edit and comment on posts. | Local · stdio |
| VlakAccessible React components, tokens, usage guidance, and install commands for product interfaces. | Remote · HTTPLive check: ✓ handshake |
| Vlk MemActStateful memory for AI agents. Temporal awareness, error loop detection, and preventive constraints. | Local · stdio |