# Kortex

**Category:** 📊 Monitoring  
**Repository:** https://kortex.rohnelt.dev  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/kortex

## Description
Which x402 service actually works: uptime, valid 402, and settlements proven on-chain.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What the Kortex MCP server does

The Kortex MCP server is described as a way to evaluate whether x402 services work in practice. Its checks cover three concrete signals: service uptime, the presence of a valid HTTP 402 response, and settlement evidence recorded on-chain.

That focus makes the Kortex MCP server relevant when an agent or developer needs to assess an x402 endpoint rather than rely only on a service’s stated compatibility. Uptime addresses whether the service is reachable. HTTP 402 validation addresses whether it responds with the payment-required status expected by the x402 flow. On-chain settlement confirmation addresses whether payment activity can be proven through blockchain records.

The available description does not identify a separate product database, dashboard, payment network, or application integration. It only establishes the x402 service checks listed above. Treat the Kortex MCP server as a validation or monitoring option for x402 services, not as a general-purpose observability platform unless additional documentation confirms that scope.

## How it works

The stated workflow is based on testing an x402 service and checking three outcomes. First, the service must be available for an uptime check. Second, its response must include a valid HTTP 402 result. Third, the resulting settlement must be verifiable on-chain.

The Kortex MCP server’s public description does not explain the request sequence, supported chains, settlement data format, polling interval, failure states, or how results are returned through MCP. Those implementation details should be confirmed before integrating it into an automated evaluation process.

## Limitations and notes

No README or setup instructions are available in the supplied material. As a result, the installation method, command used to launch the service, environment variables, authentication requirements, MCP transport, and client compatibility cannot be confirmed.

The listing also does not name individual MCP tools. The capabilities that can be stated with confidence are uptime checking, validation of a valid 402 response, and on-chain proof of settlements. It does not provide enough information to describe tool names, parameters, return schemas, supported blockchain networks, or alerting behavior.

Before adopting the Kortex MCP server, verify how an x402 endpoint is configured, which settlement networks are recognized, and what constitutes a passing check. Also confirm whether the service is intended for one-off testing, recurring monitoring, or both. These details are not specified in the available source.

The Kortex MCP server is therefore best considered when the required evaluation criteria are specifically x402 availability, correct payment-required responses, and settlement evidence. Broader monitoring, reporting, or integration requirements need documentation beyond the supplied description.

_Full upstream README: https://allmcps.com/mcp/kortex/readme_