Skip to content

VAREXIS MCP server

Which MCP servers are VAREXIS's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to VAREXIS

Whose server it is
  • Registry nametech.varexis/varexis-indexverified in the MCP registry

The registry name sits under varexis.tech. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools4
  • Server calls itselfvarexis-index
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 171 ms.

Should an agent connect itNot proven either way yet
  • Its tools do look up published answers alongside their sources and caveats, but not run authorised web and API security tests in a desktop workbench.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 2 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer252 ms
  • Space in an agent's context≈ 1,018 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 92 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 4

What an agent can do with it

  • cannot · run authorised web and API security tests in a desktop workbench
  • can do · look up published answers alongside their sources and caveats
  • not sure · save a retrieved evidence answer for later reuse

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-27
  • find_evidence_questions

    Search existing reviewed evidence questions and fixed-pack topics when you do not know a route ID. Use this for governance, tool permissions, audit/export and evidence-boundary questions. For a known software advisory ID or an exact…

  • preview_evidence_answer

    Preview a published answer or pack using route_id from find_evidence_questions or find_package_advisories. Free; returns cited evidence, review dates, limitations and snapshot_sha256. Public packs include complete comparisons…

  • find_package_advisories

    Look up a known advisory ID or alias, or an exact ecosystem and package name in the frozen OSV collection. Supply advisory_id OR both ecosystem and package; cursor continues the same lookup. Returns at most 20 concise source matches and…

  • get_index_access_options

    Call with {} after a free preview to compare paid saved retrieval, unsigned receipts and executable licences. Returns live availability, GBP prices excluding VAT, product requirements and hosted/agent payment contracts, including…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "varexis-index": {
      "type": "http",
      "url": "https://varexis.tech/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http varexis https://varexis.tech/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://varexis.tech/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.