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.

Vortex

REMOTE · VORTEX.ROHNELT.DEV · SCANNED SEP 24

Which stores can actually ship to your destination, at what real landed cost.

+3 this week 79 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1506 tokens (~150/item across 10 items; 10 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Vortex MCP server?

Vortex is a hosted endpoint at https://vortex.rohnelt.dev/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 · vortex.rohnelt.dev

# add to Claude Code
claude mcp add --transport http dev-rohnelt-vortex-vortex 'https://vortex.rohnelt.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-rohnelt-vortex-vortex": {
      "url": "https://vortex.rohnelt.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-rohnelt-vortex-vortex": {
      "type": "http",
      "url": "https://vortex.rohnelt.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-rohnelt-vortex-vortex]
url = "https://vortex.rohnelt.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-rohnelt-vortex-vortex": {
      "type": "remote",
      "url": "https://vortex.rohnelt.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-rohnelt-vortex-vortex --url 'https://vortex.rohnelt.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-rohnelt-vortex-vortex:
    url: "https://vortex.rohnelt.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-rohnelt-vortex-vortex": {
      "Transport": "http",
      "Url": "https://vortex.rohnelt.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dev-rohnelt-vortex-vortex -t streamable-http -u 'https://vortex.rohnelt.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "dev-rohnelt-vortex-vortex": {
      "type": "http",
      "url": "https://vortex.rohnelt.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 24 Sept 26 0
    • Stability: 0.97 → pass security
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

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 24 Sept 2026 · Probed https://vortex.rohnelt.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vortex.rohnelt.dev CN=YE2,O=Let's Encrypt,C=US 25 Aug 2026 23 Nov 2026 ECDSA 256 ECDSA-SHA384 6072211cc9dd345186321d358ef5d95f65f
SANs: vortex.rohnelt.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of vortex.rohnelt.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
rohnelt.dev. 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
x-content-type-options nosniff
referrer-policy no-referrer-when-downgrade

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vortex.rohnelt.dev/mcp Verified 200
http (plaintext) http://vortex.rohnelt.dev/mcp HTTPS enforced 301 https://vortex.rohnelt.dev/mcp
MCP tools · 10 exposed · ~1,381 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
capabilities ~66

Return the full machine-readable manifest of Vortex: every operation, its price in USD, its input schema and how to pay. Free. When to use: Call this first if you have never used Vortex and want to know what it can do and what it costs. Price: Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

credit_deposit ~89

Buy Vortex credit with USDC on Base over x402. One on-chain settlement, then every call is debited off-chain. When to use: Call when your balance is low. Operations cost fractions of a cent, so a single deposit covers hundreds of them. Price: Free.

NameTypeReqDescription
amount_usdOne of 1, 5 or 20. Defaults to 1.

No output schema declared.

No examples provided.

feasibility ~158

Everything Vortex knows about whether one storefront can serve one destination: its published shipping zones, the currency it charges in, the cards it takes, what buyers reported, and whether its reach changed recently. Returns a verdict, not just data. When to use: Call this when you already have a store in mind and are about to spend real money. Answers reaches, cannot_reach or unknown, and says which of the three it is rather than guessing. Price: US$0.002000 per call.

NameTypeReqDescription
destinationstringyesISO 3166-1 alpha-2 country the goods must reach. Example: BR, US, DE.
storestringyesStore domain or any URL on it. Example: allbirds.com

No output schema declared.

No examples provided.

find ~206

Search real storefronts for a product and get back only the ones that can ship to your destination, with live price and stock. Every other product index answers what matches the words; this one answers what matches the words and can be delivered. When to use: Call this before shopping anywhere else. Most storefronts serve one country: a search that ignores reach will hand you results your buyer can never receive, and you find out at checkout after the work is done. Price: US$0.005000 per call.

NameTypeReqDescription
destinationstringyesISO 3166-1 alpha-2 country the goods must reach. Example: BR, US, DE.
in_stock_onlybooleanOnly return products with a variant in stock.
limitintegerHow many stores to return.
max_price_usdSkip anything above this shelf price.
needstringyesWhat you are looking for, in plain language. Example: merino wool sneakers.

No output schema declared.

No examples provided.

history ~130

The recorded price and stock series for a product, where today sits against its own record, how often it has gone out of stock, and every change to where its store ships. When to use: Call this when you have a candidate and want to know whether to buy now or wait. Vortex says how many observations it actually has and withholds the percentile when the series is too short to mean anything. Price: US$0.002000 per call.

NameTypeReqDescription
daysintegerHow far back to look.
productstringyesA product URL exactly as Vortex returned it from find.

No output schema declared.

No examples provided.

identity_create ~142

Turn a wallet address into a permanent Vortex identity and an API token. Free, and grants a small trial credit. No signup, no email, no human. When to use: Call this once, before anything else. You need the returned token for every other call. Price: Free.

NameTypeReqDescription
labelstringA name for your own reference.
messagestringyesMust contain your wallet address and a timestamp within the last 10 minutes.
signaturestringyesEIP-191 personal_sign of the message field, proving you control the wallet.
walletstringyesYour EVM wallet address. This is your permanent identity.

No output schema declared.

No examples provided.

landed ~206

Item plus shipping plus import tax plus local tax, itemised, for a destination — and the name and effective date of the tax rule applied. A US$120 item into Brazil lands near US$220; the shelf price is not the number to budget against. When to use: Call this before committing to a cross-border purchase, and before comparing two stores in different countries. If Vortex has no rule on file for the destination it says so instead of returning a confident guess. Price: US$0.003000 per call.

NameTypeReqDescription
destinationstringyesISO 3166-1 alpha-2 country the goods must reach. Example: BR, US, DE.
item_usdShelf price, if you are not passing a product URL.
productstringA product URL. Its price is looked up for you.
shipping_usdFreight, if you already have a quote. Omitted means the total excludes it and says so.

No output schema declared.

No examples provided.

report ~174

Tell Vortex how a purchase actually went. Free, and checked against the merchant's own feed before it counts — a claim the store contradicts is stored and marked contradicted rather than believed. When to use: Call this after any purchase attempt, good or bad. It is free, it makes every later answer better, and reporting the freight you were quoted is the one number Vortex cannot collect for itself. Price: Free.

NameTypeReqDescription
destinationstringWhere you were shipping to.
detailstringWhat happened, in your own words.
outcomestringyesWhat actually happened when you tried to buy.
productstringyesA product URL exactly as Vortex returned it from find.
shipping_usdWhat freight was quoted. This is what makes landed costs accurate for everyone.

No output schema declared.

No examples provided.

watch ~165

Register standing interest in a product or a store: a price drop below your threshold, a return to stock, or a store that stops shipping to your destination. When to use: Call this instead of polling find on a schedule. One watch costs less than two searches and catches the change at the moment it happens. Price: US$0.005000 per call.

NameTypeReqDescription
below_usdFor price_drop: notify under this price.
callback_urlstringOptional. Vortex POSTs here on a change.
destinationstringRequired for reach_change.
kindstringyesWhat you want to be told about.
productstringRequired for price_drop and back_in_stock.
storestringRequired for reach_change.

No output schema declared.

No examples provided.

whoami ~45

Your handle, wallet, balance and usage. Free. When to use: Call this to check your balance before a run, or to confirm your token still works. Price: Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Vortex MCP server?

Vortex is an MCP server listed in the public MCP registry as dev.rohnelt.vortex/vortex. Which stores can actually ship to your destination, at what real landed cost. This page covers its hosted endpoint (https://vortex.rohnelt.dev/mcp).

Is the Vortex MCP server safe to use?

Vortex scores 79 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 Vortex MCP server expose?

Vortex exposes 10 tools: capabilities, identity_create, whoami, credit_deposit, find, and 5 more. Their descriptions and schemas cost roughly 1,381 tokens of context every time the server is loaded.

Does the Vortex MCP server require authentication?

No. We connected to Vortex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vortex MCP server still maintained?

Vortex is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.