Is the It Scorptech X402 MCP server down?

mcp-registry/com.it.scorptech/x402 · v1.0.0

healthy
Last checked 2026-10-24 13:44 UTC · handshake 268ms

As of 2026-10-24 13:44 UTC, the It Scorptech X402 MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
335
outages (90d)
0
tools
300+

112 x402 pay-per-call tools: web data, security/OSINT, SEC and public data, Solana/EVM lookups

Install It Scorptech X402 MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http it-scorptech-x402-mcp-server https://scorptech.it.com/api/x402/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "it-scorptech-x402-mcp-server": {
      "type": "http",
      "url": "https://scorptech.it.com/api/x402/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (66/100)

D (66/100): 1 error(s), 3 warning(s) across 1012 tool(s); ~174,571 tokens of tool definitions.
Scores higher than 1% of 15,635 MCP servers Glimind has audited.
Its tool list costs an agent ~174,571 tokens per session — more than 99% of servers.
80 → 66 since 2026-10-23
no tool-poisoning patterns
Schemas90
Descriptions31
Safety hints100
Token cost5
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (5)

Loading this server's tool list costs an agent ~174,571 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

1012 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

1296 parameter(s) across 859 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: abundance, abundancy, achilles, additive_persistence, airport_status and 854 more

8 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: json_canonicalize, json_diff, json_patch, json_schema_infer, json_to_types and 3 more

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: 8 corrected tool definitions

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

json_canonicalize 1 change
{
  "name": "json_canonicalize",
  "description": "RFC 8785 JSON Canonicalization Scheme (JCS): deterministic serialization with keys sorted by UTF-16 code units and ECMAScript number formatting, plus SHA-256 / SHA-512 digests of the canonical bytes for signing, caching and deduplication. Also returns sorted pretty JSON and document stats (depth, keys, values, bytes). POST JSON body {json}. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/json-canonicalize",
  "inputSchema": {
    "type": "object",
    "required": [
      "json"
    ],
    "properties": {
      "json": {
        "description": "Any JSON value",
        "type": "string"
      },
      "pretty": {
        "type": "boolean",
        "default": false,
        "description": "Also return an indented key-sorted rendering"
      }
    }
  },
  "annotations": {
    "title": "Json Canonicalize",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Json Canonicalize"
}
json_diff 1 change
{
  "name": "json_diff",
  "description": "Structural diff of two JSON documents: list of added / removed / changed values with JSON Pointer paths and old/new values, an RFC 6902 JSON Patch that turns a into b, and counts. Arrays are aligned by longest common subsequence (inserted items show as inserts, not a cascade of changes) or matched by an id field. POST JSON body {a, b}. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/json-diff",
  "inputSchema": {
    "type": "object",
    "required": [
      "a",
      "b"
    ],
    "properties": {
      "a": {
        "description": "Original JSON value (any type)",
        "type": "string"
      },
      "b": {
        "description": "New JSON value (any type)",
        "type": "string"
      },
      "arrayKey": {
        "type": "string",
        "maxLength": 100,
        "description": "Match array elements that are objects by this field (e.g. \"id\") instead of by position"
      },
      "maxChanges": {
        "type": "integer",
        "default": 1000,
        "maximum": 5000,
        "minimum": 1
      }
    }
  },
  "annotations": {
    "title": "Json Diff",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Json Diff"
}
json_patch 1 change
{
  "name": "json_patch",
  "description": "Apply a JSON Patch (RFC 6902: add, remove, replace, move, copy, test) or a JSON Merge Patch (RFC 7386) to a JSON document and return the result. Atomic: any failing operation or test returns 422 with the operation index and nothing is applied. POST JSON body {document, patch}. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/json-patch",
  "inputSchema": {
    "type": "object",
    "required": [
      "document",
      "patch"
    ],
    "properties": {
      "mode": {
        "enum": [
          "auto",
          "json-patch",
          "merge-patch"
        ],
        "type": "string",
        "default": "auto"
      },
      "patch": {
        "description": "RFC 6902 operations array, or an object = RFC 7386 merge patch",
        "type": "string"
      },
      "document": {
        "description": "Target JSON value",
        "type": "string"
      }
    }
  },
  "annotations": {
    "title": "Json Patch",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Json Patch"
}

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.it.scorptech/x402"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.it.scorptech/x402"}) over MCP.

Passed

Largest tool definitions

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.it.scorptech%2Fx402.svg)](https://glimind.com/server/mcp-registry%2Fcom.it.scorptech%2Fx402?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.it.scorptech%2Fx402?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.it.scorptech%2Fx402.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.it.scorptech%2Fx402.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.it.scorptech%2Fx402?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:019974a3969944de…, first seen 2026-10-23, included at leaf 54511 of 59,094. Version history · verify what your client received.

Tools (300+)

Compare: most reliable code servers · most reliable other servers · most reliable data servers · most reliable ml servers · most reliable search 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 It Scorptech X402 MCP server down right now?

As of 2026-10-24 13:44 UTC, the It Scorptech X402 MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does It Scorptech X402 MCP server provide?

It Scorptech X402 MCP server advertises 300+ tools, including abi_encode, abundance, abundancy, achilles, additive_persistence.

How do I install It Scorptech X402 MCP server?

Point your MCP client at this streamable-http endpoint: https://scorptech.it.com/api/x402/mcp

Is the It Scorptech X402 MCP server safe to connect to an AI agent?

Glimind scanned all 1012 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 It Scorptech X402 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.

Feedback
Help us improve