← Registry

AI & Machine Learning

mtok.market

Provides tools for buying and selling AI model tokens on a decentralized marketplace.

x402 supported1 endpoint13 known toolsFirst detected July 3, 2026Last detected September 24, 2026

ENDPOINT 1

https://mtok.market/mcp

No auth detected

MCP server metadata

Name
mtok.market
Version
1
Capabilities
tools
Server instructions

Spot market for AI inference tokens — NON-CUSTODIAL and SELLER-HOSTED: the platform never vaults a key, never proxies inference, and never holds money; it matches, verifies on-chain payments, prices, and tracks reputation. Delivery is always seller-hosted (tier:"direct"): the seller runs THEIR OWN relay pointed at an upstream they control, and buyers pay bounded draws in USDC on Base. Each draw goes through the MtokDripLedger contract (get_config.dripContractAddress) and the relay requires the DrawPaid event before upstream delivery; the canonical delivered tape is GET /api/chain/draws. Every live draw is paid in USDC, and every participant needs a funded EVM wallet on Base (there is no no-wallet path). register to get an agent key, then send it as the x-api-key header on EVERY subsequent request (this transport is stateless — the key is not remembered between calls). BUY flow: register -> fund a wallet on Base (USDC + a little ETH for gas; only a human can) -> place_bid -> read routes[] OR get_book -> get_config -> pay each draw on-chain through MtokDripLedger and draw through the seller relay (it verifies DrawPaid and serves report-free) -> affirmDraw on-chain when good (disputeDraw + STOP on a bad draw, max loss one draw). The mtok SDK's drawFromSeller implements the loop. SELL flow: register -> set up your inference upstream -> run mtok-relay over public HTTPS -> place_offer with tier:"direct" + relayEndpoint + settlementPubkey; your relay serves report-free. See buying_guide / selling_guide for detail. Full manual: https://mtok.market/llms.txt

Known tools 13

get_spot

Spot prices per model: the delivered OUTPUT-token rate (USD/MTok) from affirmed on-chain draws (last price, median, draw count).

Inferred read-only
selling_guide

Turnkey, executable steps to put a human's spare AI capacity on mtok.market via SELLER-HOSTED delivery — run YOUR OWN relay pointed at an upstream you control (a local Ollama/vLLM model, a subscription via a CLI bridge, or a provider key) and list a tier:direct offer; buyers pay you per chunk on-chain.

Potential side effects
buying_guide

Turnkey, executable steps to get a human cheap AI tokens and run their prompts on mtok.market: bid (read routes[]) or read the book for a tier:direct offer, then draw paid chunks from the seller's relay (pay each draw on-chain through MtokDripLedger, POST <relayEndpoint>/chunk, the relay verifies DrawPaid and serves).

Potential side effects
get_book

Open offers (asks) and bids for a model.

Inferred read-only
get_draws

The chain-derived draw tape: contract-paid draws indexed from MtokDripLedger events on Base.

Inferred read-only
get_stats

Exchange fee model plus chain-derived volume: delivered volume + affirmed/disputed counts, all recomputable from MtokDripLedger events on Base (source:"chain").

Inferred read-only
register

Create an agent identity.

Potential side effects
get_me

Your agent state: open orders (offers + bids).

Inferred read-only
place_offer

List capacity for sale via SELLER-HOSTED delivery (tier:"direct" — the only advertised path).

Inferred read-only
place_bid

Bid for a block.

Inferred read-only
cancel_order

Cancel one of your open orders.

Inferred read-only
get_reputation

A seller's reputation: score, tier, recommendedMaxChunkUsd (the per-draw size a buyer should risk in the direct tier), plus a chain object {affirmed, disputed, deliveredUsd} folded from MtokDripLedger events (source:"chain").

Inferred read-only
get_config

Chain config a SELLER-HOSTED buyer needs to build the on-chain draw payment: { feeAddress, feeBps, dustThresholdUsd, chainId, usdcAddress, dripContractAddress }.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mtok-market]
url = "https://mtok.market/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "mtok-market": {
      "type": "http",
      "url": "https://mtok.market/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: mtok-market
Remote MCP URL: https://mtok.market/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mtok-market": {
      "url": "https://mtok.market/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "mtok-market": {
      "type": "http",
      "url": "https://mtok.market/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "mtok-market",
  "transport": "streamable-http",
  "url": "https://mtok.market/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for mtok.market was fetched 2026-08-03T19:31:49.220Z and is being refreshed.

Trust status Neutral

mtok.market is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.