market.mtok/mcp

Est-ce que market.mtok/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « market.mtok/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 13 outils

• buying_guide≈ 112 tokens

  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). You need a funded wallet on Base.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "buying_guide", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cancel_order≈ 62 tokens

  Cancel one of your open orders. side: offer|bid.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
  • side · string · requis · offer | bid

  Exemple d'appel

  {"name": "cancel_order", "arguments": {"id": "texte", "side": "offer"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_book≈ 65 tokens

  Open offers (asks) and bids for a model. sort=input|output ranks by that dimension.

  Paramètres, retour & exemple (2)

  Paramètres

  • sort · string · optionnel · input | output
  • model · string · optionnel

  Exemple d'appel

  {"name": "get_book", "arguments": {"sort": "input", "model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_config≈ 110 tokens

  Chain config a SELLER-HOSTED buyer needs to build the on-chain draw payment: { feeAddress, feeBps, dustThresholdUsd, chainId, usdcAddress, dripContractAddress }. Pay each draw through the MtokDripLedger contract at dripContractAddress (payDraw), then affirmDraw/disputeDraw on-chain; the seller relay verifies the DrawPaid event before delivery.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_config", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_draws≈ 117 tokens

  The chain-derived draw tape: contract-paid draws indexed from MtokDripLedger events on Base. status=inProcess (DrawPaid with no terminal yet) | settled (closed by DrawAffirmed or DrawDisputed). This is the canonical delivered/receipt surface; the platform records nothing off-chain.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • status · string · optionnel · inProcess | settled

  Exemple d'appel

  {"name": "get_draws", "arguments": {"limit": 1, "status": "inProcess"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_me≈ 78 tokens

  Your agent state: open orders (offers + bids). Non-custodial — there is no platform wallet, grant, or credential vault in /me; money moves peer-to-peer on-chain, and your delivered draws are the on-chain tape (get_draws).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_me", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_reputation≈ 95 tokens

  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").

  Paramètres, retour & exemple (1)

  Paramètres

  • agentId · string · requis

  Exemple d'appel

  {"name": "get_reputation", "arguments": {"agentId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_spot≈ 55 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_spot", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_stats≈ 64 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_stats", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• place_bid≈ 364 tokens

  Bid for a block. The bid response returns routes[] — the crossing SELLER-HOSTED offers (lowest price first), each {offerId, sellerId, relayEndpoint, settlementPubkey, requestHashScheme?, inputPricePerMTok, outputPricePerMTok, availableInputTokens, availableOutputTokens}. Pick a route and DRAW paid chunks from its relayEndpoint (pay each draw on-chain through MtokDripLedger using /api/config, POST <relayEndpoint>/chunk, then affirmDraw/disputeDraw on-chain — see buying_guide / drawFromSeller). priceOn=input|output ranks matches by one dimension. You ALWAYS need a funded wallet on Base (there is no no-wallet path). SIGNING: a non-custodial market requires a client-signed Ed25519 intent — the MCP server CANNOT sign (it does not hold your key). Use the mtok SDK's bid() (it signs for you), or sign the intent yourself and pass {intent, sig}.

  Paramètres, retour & exemple (9)

  Paramètres

  • sig · string · optionnel
  • model · string · optionnel
  • intent · object · optionnel
  • priceOn · string · optionnel · input | output
  • inputTokens · integer · optionnel
  • outputTokens · integer · optionnel
  • maxInputPricePerMTok · number · optionnel
  • maxStartDelaySeconds · integer · optionnel
  • maxOutputPricePerMTok · number · optionnel

  Exemple d'appel

  {"name": "place_bid", "arguments": {"sig": "texte", "model": "texte", "intent": {}, "priceOn": "input", "inputTokens": 1, "outputTokens": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• place_offer≈ 614 tokens

  List capacity for sale via SELLER-HOSTED delivery (tier:"direct" — the only advertised path). Set tier:"direct" + relayEndpoint (your relay's PUBLIC HTTPS url — a cloudflared tunnel gives one free) + settlementPubkey (your seller payout EVM address on Base) and NO credentialId: you run your own relay (mtok-relay or any conforming passthrough) pointed at an upstream you control, and buyers pay each draw on-chain through MtokDripLedger (canonical relay protocol: GET /api/guides/selling, notes.directTierProtocol). After every instance behind relayEndpoint is dual-stack, add requestHashScheme:"nonce-v1"; omit it during a mixed-fleet rollout. Set a positive price; each on-chain draw pays seller plus configured platform fee, and the platform holds nothing. Your relay is REPORT-FREE: it verifies the DrawPaid event before delivery and reports nothing (the platform indexes the draw from MtokDripLedger events; the canonical tape is GET /api/chain/draws). GET /api/models/licenses is best-effort guidance, not a gate: you are responsible for the right to sell what you list. usableForSeconds is required. SIGNING: a non-custodial market requires a client-signed Ed25519 intent — the MCP server CANNOT sign (it does not hold your key); sign tier/relayEndpoint/settlementPubkey/requestHashScheme INTO the intent params. Use the mtok SDK's offer() (it signs for you), or sign the intent yourself and pass {intent, sig}.

  Paramètres, retour & exemple (15)

  Paramètres

  • sig · string · optionnel
  • tier · string · optionnel · direct
  • model · string · optionnel
  • intent · object · optionnel
  • recurring · boolean · optionnel
  • inputTokens · integer · optionnel
  • outputTokens · integer · optionnel
  • payoutAddress · string · optionnel
  • relayEndpoint · string · optionnel
  • startsInSeconds · integer · optionnel
  • settlementPubkey · string · optionnel
  • usableForSeconds · integer · optionnel
  • inputPricePerMTok · number · optionnel
  • requestHashScheme · string · optionnel · nonce-v1
    Optional signed rollout marker; set only when every relay instance behind relayEndpoint is dual-stack.
  • outputPricePerMTok · number · optionnel

  Exemple d'appel

  {"name": "place_offer", "arguments": {"sig": "texte", "tier": "direct", "model": "texte", "intent": {}, "recurring": true, "inputTokens": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• register≈ 122 tokens

  Create an agent identity. Returns {agentId, apiKey}; send the apiKey as the x-api-key (or Authorization: Bearer) header on EVERY subsequent request to act as that agent — this transport is stateless, so it is not remembered between calls. Pass pubkey (Ed25519 SPKI PEM) if you will place signed non-custodial orders.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
  • pubkey · string · optionnel

  Exemple d'appel

  {"name": "register", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• selling_guide≈ 135 tokens

  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. Gotchas baked in. supply_type filters to one path.

  Paramètres, retour & exemple (1)

  Paramètres

  • supply_type · string · optionnel · open-weight | subscription | provider-key

  Exemple d'appel

  {"name": "selling_guide", "arguments": {"supply_type": "open-weight"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mtok.market/mcp