io.github.yofor/ovanek-mcp

{
  "mcpServers": {
    "ovanek-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ovanek/mcp@1.0.0"
      ]
    }
  }
}

{
  "mcpServers": {
    "ovanek-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ovanek/mcp@1.0.0"
      ]
    }
  }
}

{
  "servers": {
    "ovanek-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ovanek/mcp@1.0.0"
      ]
    }
  }
}

code --add-mcp '{"name":"ovanek-mcp","type":"stdio","command":"npx","args":["-y","@ovanek/mcp@1.0.0"]}'

claude mcp add --transport stdio ovanek-mcp -- npx -y @ovanek/mcp@1.0.0

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @ovanek/mcp@1.0.0

Settings → Connectors → Add custom connector, then paste:
https://ovanek.vercel.app/api/mcp

The entry also requires the header Authorization.

{
  "mcpServers": {
    "ovanek-mcp": {
      "url": "https://ovanek.vercel.app/api/mcp",
      "headers": {
        "Authorization": "<Authorization>"
      }
    }
  }
}

{
  "servers": {
    "ovanek-mcp": {
      "type": "http",
      "url": "https://ovanek.vercel.app/api/mcp",
      "headers": {
        "Authorization": "${input:authorization}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "authorization",
      "description": "Authorization",
      "password": true
    }
  ]
}

claude mcp add --transport http ovanek-mcp https://ovanek.vercel.app/api/mcp --header "Authorization: <Authorization>"

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://ovanek.vercel.app/api/mcp --transport http

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Facts about the publisher. We do not turn them into a trust score.

Source: the registry entry and api.github.com · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

No session

No session could be opened when we tried, so no check could run. No security score is given; a check we did not run is never counted as passed.

Why not security-tested: The server did not answer within our time limit; a longer limit or a retry is on us. — our limit

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). None of the 18 checks that apply to it could be exercised. We do not publish security-check outcomes for named servers.

Source: our own test in an isolated sandbox, date not recorded, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

The steps in order, as the test record holds them.

1. 0 msStarted the published package in an isolated sandbox
2. No answer within our time limit.
3. 240,000 msFinished: 0 checks exercised.

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.