# com.hektai/market (remote · mcp.hektai.com)

One Hekte market answer per call, paid first over Lightning by a hold invoice in the tool result.

- Trust score: 64/100 (medium)
- Registry status: deleted
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

> **Deleted**: this server was marked deleted in the MCP registry on 2026-09-20. Its details are retained for reference. The registry records this reason: "withdrawn."

## Components

- remote · `mcp.hektai.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-hektai-market/mcp.md), [page](https://verifymcp.io/servers/com-hektai-market/mcp)

## Channel facts

- Endpoint: `https://mcp.hektai.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1116 tokens (~372/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-15 (score 62)

First indexed and scored.

## MCP tools (3)

### `hekte_ask` (~556 tokens)

Buy one answer on the Hekte market — PAY FIRST, per call, Lightning. Call it with `prompt` alone: the result is an error with `status: "payment_required"`, a Lightning `invoice` (bolt11) for `amount_sat` (whole sats), a `pay_url` a human can open, an `expires_at`, and `retry_with` (`payment_hash`, `retry_token`). Show the human the `pay_url` (or the invoice) and ask them to pay it; then call this tool AGAIN with the SAME `prompt` and `class` plus the `payment_hash` and `retry_token`. Before the payment arrives the retry answers `payment_not_received`; after it, the question is posted as a paid job, a worker answers, the payment settles ON DELIVERY and the answer comes back with who served it and a `receipt`. If nothing is delivered the hold is cancelled (`hold_cancelled: true`) and nothing is charged. No balance is kept, no account exists: one invoice is one call. Refused by name: `prompt_too_large` (over 16384 bytes), `class_unknown`, `invalid_max_sat`, `proof_unknown`, `proof_expired`, `proof_replayed`, `proof_cancelled`, `retry_token_invalid` (the token is not this invoice's), `request_mismatch` (a retry must repeat the paid prompt), `contract_mismatch` (the `contract` named is not 2, this door's).

Input parameters:

- `class` (string): The task class. Only `chat` exists today.
- `contract` (integer): The hosted contract number this client speaks — every result of this door names it as `contract` and `retry_with` repeats it (today 2). Omit it if unknown; an older number is refused `contract_mismat…
- `max_sat` (integer): Optional cap on this call's price, whole sats. May only LOWER the door's per-call price; a higher value is lowered to it.
- `payment_hash` (string): The `retry_with.payment_hash` value from this tool's `payment_required` result, once a human has paid the invoice. Omit it on the first call; always send it together with `retry_token`.
- `prompt` (string, required): The question, verbatim — it is posted to the market as the job's input. A retry must repeat it exactly.
- `retry_token` (string): The `retry_with.retry_token` value from this tool's `payment_required` result. Omit it on the first call; always send it together with `payment_hash`.

### `hekte_balance` (~152 tokens)

The PRICE of the next `hekte_ask` on this pay-first door: `price_sat` (whole sats, Lightning, per call), `invoice_expiry_s` (how long a minted invoice can be paid), `pay_first: true`, and `open` (whether the door can buy on the market right now). No balance exists here — every call is its own invoice.

Input parameters:

- `contract` (integer): The hosted contract number this client speaks — every result of this door names it as `contract` and `retry_with` repeats it (today 2). Omit it if unknown; an older number is refused `contract_mismat…

### `hekte_job` (~222 tokens)

One job's lines from this door's BUYER LEDGER (posted, offers, funding, delivery, settlement — ids, sats, times, codes; never the brief or the output), for a job YOUR payment ran: `job_id` must be the one `hekte_ask` returned for this `payment_hash` + `retry_token`. `found: false` = no line names it.

Input parameters:

- `contract` (integer): The hosted contract number this client speaks — every result of this door names it as `contract` and `retry_with` repeats it (today 2). Omit it if unknown; an older number is refused `contract_mismat…
- `job_id` (string, required): The job id `hekte_ask` returned.
- `payment_hash` (string, required): The `payment_hash` of the `hekte_ask` that ran this job.
- `retry_token` (string, required): The `retry_token` of the `hekte_ask` that ran this job.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hektai-market/mcp#diagnostics

## Score history

- 2026-09-20: 64
- 2026-09-19: 64
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 62
- 2026-09-15: 62

## Common questions

### What is the com.hektai/market MCP server?

com.hektai/market is an MCP server listed in the public MCP registry as com.hektai/market. One Hekte market answer per call, paid first over Lightning by a hold invoice in the tool result. This page covers its hosted endpoint (https://mcp.hektai.com/mcp).

### Is the com.hektai/market MCP server safe to use?

com.hektai/market scores 64 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 com.hektai/market MCP server expose?

com.hektai/market exposes 3 tools: hekte_ask, hekte_balance, hekte_job. Their descriptions and schemas cost roughly 930 tokens of context every time the server is loaded.

### Does the com.hektai/market MCP server require authentication?

No. We connected to com.hektai/market without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.hektai/market MCP server still maintained?

com.hektai/market has been deleted from the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.hektai.com/mcp
- Website: https://hekte.org/
- Changelog RSS feed: https://verifymcp.io/servers/com-hektai-market/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hektai-market/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hektai-market/mcp