Kortex
REMOTE · KORTEX.ROHNELT.DEV · SCANNED OCT 15
Which x402 service actually works: uptime, valid 402, and settlements proven on-chain.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Kortex MCP server?
Kortex is a hosted endpoint at https://kortex.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 · kortex.rohnelt.dev
claude mcp add --transport http dev-rohnelt-kortex-kortex 'https://kortex.rohnelt.dev/mcp'
{
"mcpServers": {
"dev-rohnelt-kortex-kortex": {
"url": "https://kortex.rohnelt.dev/mcp"
}
}
} {
"servers": {
"dev-rohnelt-kortex-kortex": {
"type": "http",
"url": "https://kortex.rohnelt.dev/mcp"
}
}
} [mcp_servers.dev-rohnelt-kortex-kortex] url = "https://kortex.rohnelt.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-rohnelt-kortex-kortex": {
"type": "remote",
"url": "https://kortex.rohnelt.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-rohnelt-kortex-kortex --url 'https://kortex.rohnelt.dev/mcp' --transport streamable-http
mcp_servers:
dev-rohnelt-kortex-kortex:
url: "https://kortex.rohnelt.dev/mcp" {
"McpServers": {
"dev-rohnelt-kortex-kortex": {
"Transport": "http",
"Url": "https://kortex.rohnelt.dev/mcp"
}
}
} assistant mcp add dev-rohnelt-kortex-kortex -t streamable-http -u 'https://kortex.rohnelt.dev/mcp'
{
"mcpServers": {
"dev-rohnelt-kortex-kortex": {
"type": "http",
"url": "https://kortex.rohnelt.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Oct 26 −56
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
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 15 Oct 2026 · Probed https://kortex.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=kortex.rohnelt.dev | CN=YE1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 614e8049d1df86156815a461f70ce85476d |
| SANs: kortex.rohnelt.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 kortex.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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 502 |
| 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://kortex.rohnelt.dev/mcp | HTTP error | 502 | |
| http (plaintext) | http://kortex.rohnelt.dev/mcp | HTTPS enforced | 301 | https://kortex.rohnelt.dev/mcp |
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 →
capabilities Describe Kortex ~66
Return the full machine-readable manifest of Kortex: 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 Kortex 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.
check Is this one safe to pay ~152
Everything Kortex knows about a single resource URL: whether it is up, whether its 402 is well formed, what it quotes, and whether its payout address has ever been paid on-chain. Returns a verdict, not just data. When to use: Call this when you already have a URL and want to know whether sending money to it is a good idea. Worth it above roughly US$0.05 a call; below that the check costs more than the risk. Price: US$0.002000 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| probe_now | boolean | – | Hit the endpoint live instead of using the most recent scheduled probe. |
| resource | string | yes | The exact URL you are about to pay, including the path. |
No output schema declared.
No examples provided.
compare Rank several candidates ~76
Score two or more resource URLs side by side on the same evidence, and say which one to pay. When to use: Call this when you already have a shortlist and need to pick. Cheaper than calling check once per URL. Price: US$0.003000 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| resources | array | yes | The URLs to rank. |
No output schema declared.
No examples provided.
credit_deposit Top up balance ~91
Buy Kortex 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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | string | – | One of 1, 5 or 20. Defaults to 1. |
No output schema declared.
No examples provided.
history Show me the record ~115
The full time series behind a score: every probe outcome, every price and payout-address change, and the on-chain settlement history of the address it pays to. When to use: Call this when a verdict surprises you, or before committing to a service you plan to depend on. This is the evidence itself rather than the summary. Price: US$0.002000 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How far back to look. |
| resource | string | yes | The exact URL you are about to pay, including the path. |
No output schema declared.
No examples provided.
identity_create Claim an identity ~142
Turn a wallet address into a permanent Kortex identity and an API token. Free, and grants a small trial credit. When to use: Call this once, before anything else. You need the returned token for every other call. No account, no email, no human. Price: Free.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | A name for your own reference. |
| message | string | yes | Must contain your wallet address and a timestamp within the last 10 minutes. |
| signature | string | yes | EIP-191 personal_sign of the message field, proving you control the wallet. |
| wallet | string | yes | Your EVM wallet address. This is your permanent identity. |
No output schema declared.
No examples provided.
report Report what happened ~163
Tell Kortex that you paid a service and what you got. Free, and only counted once the payment is found on-chain — so a report costs at least the price of the call it describes. When to use: Call this after any paid call that went wrong, and after ones that went right. It is free, it makes every later verdict better, and the evidence it adds is the kind no probe can produce. Price: Free.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | What happened, in your own words. |
| outcome | string | yes | What actually happened after you paid. |
| resource | string | yes | The exact URL you are about to pay, including the path. |
| tx_hash | string | – | The settlement transaction, if you have it. Speeds up verification. |
No output schema declared.
No examples provided.
resolve Find a service that actually works ~222
Describe what you need in plain language and get back x402 services ranked by evidence: how much of the time they have been up, whether they answer with a valid 402, and how many distinct wallets have actually paid them on-chain. One entry per operator, not per URL. When to use: Call this before paying a service you have not used, and instead of taking the first result from a directory. Of the services listed as x402 today, measured across 1,015 of them, only 25% actually answer with a payment requirement — the rest are up but sell nothing. Price: US$0.005000 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many candidates to return. |
| max_price_usd | string | – | Skip anything that quotes more than this per call. |
| need | string | yes | What you want done, in plain language. Example: scrape a web page and return clean text. |
| require_paid | boolean | – | Only return services with at least one on-chain settlement. Turn off to see untested ones too. |
No output schema declared.
No examples provided.
watch Tell me if it changes ~124
Register interest in a service. Kortex records a watch and reports what has changed — price, payout address, or availability — the next time you ask. When to use: Call this for a service you depend on. A payout address that moves is the strongest warning signal there is, and you will not notice it by yourself. Price: US$0.005000 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | Optional. If set, Kortex POSTs here when something changes. |
| resource | string | yes | The exact URL you are about to pay, including the path. |
No output schema declared.
No examples provided.
whoami Who am I ~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.
What is the Kortex MCP server?
Kortex is an MCP server listed in the public MCP registry as dev.rohnelt.kortex/kortex. Which x402 service actually works: uptime, valid 402, and settlements proven on-chain. This page covers its hosted endpoint (https://kortex.rohnelt.dev/mcp).
Is the Kortex MCP server safe to use?
Kortex scores 25 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 Kortex MCP server expose?
Kortex exposes 10 tools: capabilities, identity_create, whoami, credit_deposit, resolve, and 5 more. Their descriptions and schemas cost roughly 1,196 tokens of context every time the server is loaded.
Does the Kortex MCP server require authentication?
Its publisher declares no required credentials for Kortex. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Kortex MCP server still maintained?
Kortex is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.