Developer · Remote MCP server
VeriTeknik
Manage VeriTeknik servers, DNS, backups and support tickets from your AI assistant.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.veriteknik/mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- com.veriteknik
- Namespace
- Namespace verified by the MCP Registry via the domain veriteknik.com · how
- Website
- veriteknik.com/docs/en/mcp/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://veriteknik.com/api/mcp | None |
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 VeriTeknik
VeriTeknik is a remote MCP server: there is nothing to install. Its endpoint is https://veriteknik.com/api/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 developer servers
| Server | Runs |
|---|---|
| Verify SCITT receipts from Forestrie transparency logs, offlineVerify a SCITT receipt under a trust root you hold - offline, no backend, no key, no network. | Local · stdio |
| 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 |
| Verlon AI MCPInspect and manage Verlon AI gates, logs, recommendations, and experiments from any MCP client. | Local · stdio |
| 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 |