Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VAREXIS-INDEX - Source-linked evidence

REMOTE · VAREXIS.TECH

7 packs: free read-only previews; paid snapshots/unsigned receipts. No advice or authority.

Available components

72 Trust /100

Last scanned (15 hours ago)

Scores higher than 63% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 695 tokens (~173/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 +1
    • Tool “find_evidence_questions” rewrote its description, which is the text the model reads security
    • Tool “get_index_access_options” rewrote its description, which is the text the model reads security
    • Tool “preview_evidence_answer” rewrote its description, which is the text the model reads security
    • Schema quality: 151 → 173 ▼ functional
    • Tool coverage: 0% → 25% ▲ functional
    • “find_evidence_questions” reworded the description of “offset” cosmetic
    • “find_evidence_questions” reworded the description of “query” cosmetic
  • 17 Oct 26 0
    • Tool “preview_evidence_answer” rewrote its description, which is the text the model reads security
  • 16 Oct 26 0
    • Tool “find_evidence_questions” rewrote its description, which is the text the model reads security
    • Tool “preview_evidence_answer” rewrote its description, which is the text the model reads security
  • 15 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_index_access_options” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
  • 13 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://varexis.tech/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=varexis.tech CN=YR1,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 RSA 2048 SHA256-RSA 5f83e38ded3e9b4ccdaf24dc2457e1b57a6
SANs: varexis.tech
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of varexis.tech. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
tech. present 2185 13 Verified
varexis.tech. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self' https://checkout.stripe.com; img-src 'self' data: blob: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://checkout.stripe.com; connect-src 'self' https://api.stripe.com https://checkout.stripe.com; frame-src 'self' https://js.stripe.com https://checkout.stripe.com https://hooks.stripe.com; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://varexis.tech/mcp Verified 200
http (plaintext) http://varexis.tech/mcp HTTPS enforced 308 https://varexis.tech/mcp
MCP tools · 4 exposed · ~622 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_evidence_questions ~228

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 ecosystem/package lookup, use find_package_advisories instead. Supply query as keywords (maximum 160 characters), or leave it blank to browse. offset is the zero-based pagination offset (default 0, maximum 10000; increase by 20). Returns up to 20 matches with route_id, matched wording and the scoped question; pass a route_id to preview_evidence_answer for the complete free answer and sources. Matching ignores case, punctuation and common question words; it does not validate arbitrary new claims. No match is not a negative verdict. Free and read-only.

NameTypeReqDescription
offsetinteger–Zero-based result offset, 0 to 10000; start at 0 and increase by 20 for the next page.
querystring–Keywords for an existing reviewed question or evidence-pack topic; leave blank to browse the first 20 routes.

No output schema declared.

No examples provided.

find_package_advisories ~149

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 route IDs for preview_evidence_answer. Source capture dates and withdrawals are explicit. Full previews include separately dated EPSS/KEV matches and explicit fix boundaries; scores are not asset-risk assessments. No results never mean safe. No range solving, current scanning, independent verification or payment. Free and read-only.

NameTypeReqDescription
advisory_idstring––
cursorstring––
ecosystemstring––
packagestring––

No output schema declared.

No examples provided.

get_index_access_options ~117

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 standalone Tool Admission (GBP49) and Audit Coverage (GBP79). Existing subscriptions exclude these two licences. Use purchase_url for hosted checkout; compatible agents need owner spending authority for the exact quote and must follow agent_payments_contract for payment and recovery. Free evidence needs no payment. Never send keys here; this tool cannot charge or retrieve purchases.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preview_evidence_answer ~128

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. Executable-product previews show scope, schemas and examples, not the licensed ZIP; the original integration kit also has a distinct preview_payload_sha256. Optional version checks exact advisory-listed versions only, not ranges or safety. For prices and licences, call get_index_access_options. No paid saving or live testing.

NameTypeReqDescription
route_idstringyes–
versionstring––

No output schema declared.

No examples provided.

Install

How do I install the VAREXIS-INDEX - Source-linked evidence MCP server?

VAREXIS-INDEX - Source-linked evidence is a hosted endpoint at https://varexis.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · varexis.tech

# add to Claude Code
claude mcp add --transport http tech-varexis-varexis-index 'https://varexis.tech/mcp'
Common questions

What is the VAREXIS-INDEX - Source-linked evidence MCP server?

VAREXIS-INDEX - Source-linked evidence is an MCP server listed in the public MCP registry as tech.varexis/varexis-index. 7 packs: free read-only previews; paid snapshots/unsigned receipts. No advice or authority. This page covers its hosted endpoint (https://varexis.tech/mcp).

Is the VAREXIS-INDEX - Source-linked evidence MCP server safe to use?

VAREXIS-INDEX - Source-linked evidence scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VAREXIS-INDEX - Source-linked evidence MCP server expose?

VAREXIS-INDEX - Source-linked evidence exposes 4 tools: find_evidence_questions, preview_evidence_answer, find_package_advisories, get_index_access_options. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.

Does the VAREXIS-INDEX - Source-linked evidence MCP server require authentication?

No. We connected to VAREXIS-INDEX - Source-linked evidence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VAREXIS-INDEX - Source-linked evidence MCP server still maintained?

VAREXIS-INDEX - Source-linked evidence is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.