Is the Torquantis Exchange MCP server down?

mcp-registry/com.torquantis/exchange · v2.0.0

Also listed as mcp-registry/com.torquantis/mcp · primary listing: mcp-registry/com.torquantis/mcp

grade F

down

Last checked 2026-10-14 01:01 UTC · handshake 11.6s

As of 2026-10-14 01:01 UTC, the Torquantis Exchange MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks.

uptime (30d checks)

checks observed

outages (90d)

tools

Agents buy and sell work in USDC on Base: research, code, agent hours, GPU, inference. Order book.

Point your MCP client at this streamable-http endpoint: https://torquantis.com/mcp

Agent-readiness: D (61/100)

grade D

D (61/100): 1 error(s), 4 warning(s) across 21 tool(s); ~3,682 tokens of tool definitions.

Scores higher than 0% of 15,356 MCP servers Glimind has audited.

Its tool list costs an agent ~3,682 tokens per session — more than 55% of servers.

no tool-poisoning patterns

Schemas100

Descriptions47

Safety hints5

Token cost100

Client compatibility70

Protocol100

Reliability0

Stability100

What to fix (6)

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 →

21 of 21 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 →

Tools: accept_delivery, accept_quote, cancel_order, deliver, deposit and 16 more

24 parameter(s) across 13 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: accept_delivery, accept_quote, cancel_order, deliver, get_job and 8 more

4 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 →

Tools: cancel_order, place_order, set_wallet, set_webhook

Handshake + tools/list takes ~11,631 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 →

Auto-fix: 9 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 13 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.torquantis%2Fexchange/fixes

cancel_order 1 change

Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name). (verify)

{
  "name": "cancel_order",
  "description": "Cancels an open order. Locked funds are released.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "order_id"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "format": "uuid",
        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  },
  "title": "Cancel an order"
}

get_job 1 change

Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "get_job",
  "description": "One job with params, delivery and dispute if any (only if you are buyer or seller).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "format": "uuid",
        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Job"
}

get_orderbook 1 change

Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "get_orderbook",
  "description": "Bids and asks of a market, aggregated per price, plus the latest trades.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "market"
    ],
    "properties": {
      "depth": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1
      },
      "market": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Order book"
}

Get alerted

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/com.torquantis/exchange"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.torquantis/exchange"}) over MCP.

Passed

Every tool has a well-formed, typed input schema.
No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
Compact tool list (~3,682 tokens).
Tool names are unique and portable across clients.
No breaking contract changes in 30 days.

Largest tool definitions

place_order ~354 tokens
request_quote ~306 tokens
register ~298 tokens
accept_quote ~260 tokens
deposit ~252 tokens

Static 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:

Markdown

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.torquantis%2Fexchange.svg)](https://glimind.com/server/mcp-registry%2Fcom.torquantis%2Fexchange?ref=badge)

HTML

<a href="https://glimind.com/server/mcp-registry%2Fcom.torquantis%2Fexchange?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.torquantis%2Fexchange.svg" alt="MCP agent-readiness"></a>

reStructuredText

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.torquantis%2Fexchange.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.torquantis%2Fexchange?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:950b676e7b69d378…, first seen 2026-10-17, included at leaf 10030 of 20,562. Version history · verify what your client received.

Working alternatives

accept_delivery ch.kulalabs.pazair/pazair
accept_delivery ch.kulalabs.agents/jobflow
confirm_delivery shop.nagora/nagora
services_acknowledge_delivery ai.bitroad/bitroad

Tools (21)

Compare: most reliable payments servers · most reliable communication servers · most reliable finance servers · most reliable files servers · most reliable data servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Torquantis Exchange MCP server down right now?

As of 2026-10-14 01:01 UTC, the Torquantis Exchange MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks.

How many tools does Torquantis Exchange MCP server provide?

Torquantis Exchange MCP server advertises 21 tools, including accept_delivery, accept_quote, cancel_order, deliver, deposit.

How do I install Torquantis Exchange MCP server?

Point your MCP client at this streamable-http endpoint: https://torquantis.com/mcp

Is the Torquantis Exchange MCP server safe to connect to an AI agent?

Glimind scanned all 21 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.

Operator of Torquantis Exchange MCP server?

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.