mcp-registry/dev.rohnelt.vortex/vortex · v0.1.0
As of 2026-10-17 21:40 UTC, the Rohnelt Vortex Vortex MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Which stores can actually ship to your destination, at what real landed cost.
Point your MCP client at this streamable-http endpoint: https://vortex.rohnelt.dev/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,162 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
2 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.rohnelt.vortex%2Fvortex/fixes
{
"name": "capabilities",
"description": "Return the full machine-readable manifest of Vortex: every operation, its price in USD, its input schema and how to pay. Free.\n\nWhen to use: Call this first if you have never used Vortex and want to know what it can do and what it costs.\n\nPrice: Free.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Describe Vortex"
}{
"name": "identity_create",
"description": "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.\n\nWhen to use: Call this once, before anything else. You need the returned token for every other call.\n\nPrice: Free.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"wallet",
"signature",
"message"
],
"properties": {
"label": {
"type": "string",
"maxLength": 64,
"description": "A name for your own reference."
},
"wallet": {
"type": "string",
"pattern": "^0x[a-fA-F0-9]{40}$",
"description": "Your EVM wallet address. This is your permanent identity."
},
"message": {
"type": "string",
"maxLength": 200,
"minLength": 8,
"description": "Must contain your wallet address and a timestamp within the last 10 minutes."
},
"signature": {
"type": "string",
"pattern": "^0x[a-fA-F0-9]+$",
"description": "EIP-191 personal_sign of the message field, proving you control the wallet."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Claim an identity"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.rohnelt.vortex/vortex"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.rohnelt.vortex/vortex"}) over MCP.
find ~373 tokensreport ~360 tokenslanded ~354 tokenswatch ~331 tokensidentity_create ~270 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.rohnelt.vortex%2Fvortex?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.rohnelt.vortex%2Fvortex?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.rohnelt.vortex%2Fvortex.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.rohnelt.vortex%2Fvortex.svg :target: https://glimind.com/server/mcp-registry%2Fdev.rohnelt.vortex%2Fvortex?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f8035a099910d57f…, first seen 2026-10-17, included at leaf 12543 of 22,407. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable finance servers · most reliable search servers · most reliable data servers · most reliable identity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 21:40 UTC, the Rohnelt Vortex Vortex MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Rohnelt Vortex Vortex MCP server advertises 10 tools, including capabilities, credit_deposit, feasibility, find, history.
Point your MCP client at this streamable-http endpoint: https://vortex.rohnelt.dev/mcp
Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.