Developer · Local MCP server
Verlon AI MCP
Inspect and manage Verlon AI gates, logs, recommendations, and experiments from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.verlon/mcp- Version
- 0.4.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- ai.verlon
- Namespace
- Namespace verified by the MCP Registry via the domain verlon.ai · how
- Website
- docs.verlon.ai/integrations/mcp
- Repository
- github.com/verlon-ai/mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @verlon-ai/mcp | 0.4.1 | stdio |
How to connect Verlon AI MCP
Verlon AI MCP runs locally from a Node.js package published to the npm registry: @verlon-ai/mcp version 0.4.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @verlon-ai/mcp@0.4.1. It reads these environment variables: VERLON_API_KEY (required, secret) and VERLON_BASE_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@verlon-ai/mcp@0.4.1"
],
"env": {
"VERLON_API_KEY": "<secret>",
"VERLON_BASE_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. 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 developer servers
| Server | Runs |
|---|---|
| verimcpTransparent MCP proxy that independently re-verifies tool-call claims before the Host trusts them. | Local · stdio |
| VerirunExecution-grounded verification for AI coding agents on Windows: evidence, not agent claims. | Local · stdio |
| VerisBehavioral verification intelligence for AI coding agents. 17 MCP tools. Local-first. MIT. | Local · stdio |
| VeriTeknikManage VeriTeknik servers, DNS, backups and support tickets from your AI assistant. | Remote · HTTPLive check: sign-in required |
| VersionlyMonitor third-party API changes in GitHub repos, map breaks to files, open reviewable auto-fix PRs. | Remote · HTTPLive check: sign-in required |
| VetDiscover and vet MCP servers: search 200K+ AI tools with security verification and schemas. | Local · stdio |
| Veto93 agentic MCP tools + 49 specialist agents for every major AI CLI. Self-learning, no API keys. | Local · stdio |
| Veto - SQL Safety & Cost OracleDeterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it. | Remote · HTTPLive check: ✓ handshake |