Polymarket Guard

io.github.evidai由 GitHub 帳號 evidai 發布v0.1.0更新於 Oct 24, 2026

Polymarket prediction markets — buy/sell positions in USDC. LemonCake pay-per-call billing.

已驗證STDIO僅桌面金融商業與電商

概覽

AI 產生的概覽

本機 MCP 伺服器,用於以 USDC 買賣 Polymarket 預測市場部位,可選用 LemonCake 按次計費。

可以做什麼
  • 買入與賣出 Polymarket 預測市場的 USDC 部位
  • 未提供錢包私鑰時以唯讀模式執行
  • 透過買家權杖走 LemonCake 按次計費呼叫
  • 未公布工具清單,實際操作未在文件中說明
適用情境
適合需要在桌面環境中檢視或交易 Polymarket 預測市場,或需要透過 LemonCake 為按次計費的 API 呼叫付費的助理。
執行需求
以本機 stdio 程序執行(npm 套件 polymarket-guard-mcp),僅限桌面端。交易需要 POLYMARKET_PRIVATE_KEY 中的 Polygon 錢包私鑰;未設定則以唯讀模式執行。按次計費需要 LEMON_CAKE_BUYER_JWT 中的 LemonCake 買家 JWT。需要連線至 Polymarket 與 LemonCake 服務的網路。
安裝前請注意
POLYMARKET_PRIVATE_KEY 是錢包私鑰,可動用真實資金,持有者即可控制該錢包,建議使用專用的低餘額錢包。交易會花費真實 USDC 且無法撤銷。LEMON_CAKE_BUYER_JWT 可授權產生信用卡扣款的付費呼叫,須留意消費上限。README 主要在介紹 LemonCake 計費平台,而非此伺服器本身的工具。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Polymarket Guard,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

🍋 LemonCake

The billing, budget & identity layer for software for agents. Private Beta · Open core

Monetize any MCP/API in minutes, and let AI agents pay for it safely — each agent gets a spend-capped identity (budget, usage, pause/revoke). Buyers pay by card; no crypto wallet. First 3,000 calls free (lifetime). Then 3% only when your API earns.

[License: MIT (SDK)] [Open core] [MCP Compatible] [x402 native] [npm: agent-payment-mcp] [FSA-confirmed] [Glama score]

🚀 Get started · 💲 Pricing · 📚 Docs · 🌐 Live


[An AI agent pays for paid API calls on its own — spend-capped, no crypto]

☝️ A real AI agent buys API calls by itself ($0.01 each), stops at its cap, and the API owner earns — no human, no crypto. · demo source


🚀 Get started

Monetizing an MCP/API? Start here — one command:

bash
npx create-lemon-mcp my-paid-mcp     # a paid MCP server, running in sandbox now# then add a Seller Key in /app and set LEMONCAKE_SELLER_KEY → it charges for real (no code change)

Pick your path:

I want to…Do this
Monetize my MCP/API (sellers)npx create-lemon-mcp → add a Seller Key in /app to go live
Add billing to a server I already have@lemon-cake/mcp-sdk — wrap a tool with lc.charge(), or route through the gateway (no code)
Let an agent pay for paid APIs (buyers)npx -y agent-payment-mcp — 8 free demo tools, no signup
Buyer-side MCP — try in 30 seconds
bash
npx -y agent-payment-mcp
json
{ "mcpServers": { "lemon": { "command": "npx", "args": ["-y", "agent-payment-mcp"] } } }

Ask your agent to run list_demos / call_demo. To call paid APIs, set LC_PAY_TOKEN (get one at lemoncake.xyz/app).


What is LemonCake?

LemonCake is an x402 payment rail for monetizing MCP servers and HTTP APIs. Sellers register an endpoint and set a price per call. Buyers prepay by card and receive a spend-capped Pay Token. Agents call the gateway with that token, and LemonCake verifies, meters, forwards, and records usage.

mermaid
sequenceDiagram    participant A as 🤖 AI Agent    participant G as 🍋 LemonCake Gateway    participant API as Your API    A->>G: POST /g/:id (no token)    G-->>A: 402 + accepts[] (price, mintUrl)    A->>G: mint Pay Token (off-session, capped)    A->>G: Bearer :jwt    G->>API: forward (upstream key hidden)    API-->>A: 200 + result    Note over A,G: budget exhausted → 402 → agent self-funds → continues

Sellers register any HTTP API and set a price per call. Buyers / agents prepay with a card → Pay Token issued automatically → agent calls the API within budget. Budget exhausted → 402 challenge → agent self-funds → continues. No humans.


🧱 Open core

LayerStatusWhere
Buyer-side MCP (agent-payment-mcp)✅ MITnpm, src
Seller SDK (@lemon-cake/mcp-sdk)✅ MITnpm, src
Starter templates✅ MITexamples/
Docs site✅ Publiclemoncake.xyz/docs
Gateway + billing engine🔒 Hostedlemoncake.xyz
Dashboard (analytics, usage ledger)🔒 Hostedlemoncake.xyz/app

💳 How payment works

For buyers (human or agent)

  1. Open a buy link (lemoncake.xyz/buy/<shortId>)
  2. Pay with a card → Pay Token (JWT) issued automatically
  3. Pass Authorization: Bearer <token> to the gateway
  4. Gateway verifies, meters, forwards to the real API
  5. Budget exhausted → 402 challenge returned with payment instructions

For agents (fully autonomous)

  1. Issue a Buyer Key (bk_...) at /app → Pay Tokens pane
  2. Save a card once at /agent/fund
  3. Agent calls POST /api/lc/agent/tokens (Bearer bk_) → off-session card charge → JWT
  4. Agent uses JWT to call gateway — hard-capped, no human in the loop
json
// MCP config for agent with pre-issued Pay Token{  "mcpServers": {    "lemon": {      "command": "npx",      "args": ["-y", "agent-payment-mcp"],      "env": {        "LC_PAY_TOKEN": "<jwt from Pay Token>"      }    }  }}

🏗 Publish your API on LemonCake (sellers)

Monetize any HTTP API or MCP server:

  1. Sign in at lemoncake.xyz/app
  2. Add API — paste your URL, set price per call (e.g. $0.01)
  3. Share the buy link, or issue a Seller Key (sk_live_…) to charge from your own server
  4. You keep 97%. LemonCake takes 3% (Stripe Connect Direct Charge). Never holds funds.

Scaffold a paid MCP in one command — sandbox by default, production with one env var:

bash
npx create-lemon-mcp my-paid-mcp     # demo runs with no key# then: set LEMONCAKE_SELLER_KEY=sk_live_… → it charges for real (no code change)

Add billing to any tool with the SDK (@lemon-cake/mcp-sdk v1, no crypto):

typescript
import { createLemonCakeSDK } from "@lemon-cake/mcp-sdk";
const lc = createLemonCakeSDK();   // reads LEMONCAKE_SELLER_KEY (demo without it)
server.tool("my_premium_tool", "desc", { q: z.string() },  lc.charge({ price: 0.01 })(async ({ q }) => {    return { content: [{ type: "text", text: "result" }] };  }),);

lc.charge wraps the handler: preflight (reserve) → run → settle (confirm on success, refund on failure). Or route existing traffic through https://lemoncake.xyz/g/<shortId> — no code changes required.


🪪 Agent Identity

Give each AI agent its own spend-capped identity — so a fleet can pay for APIs without a shared card or runaway cost. Built on top of Pay Tokens; no balance pool, custody-free (an agent's "budget" is just the Pay Tokens bound to it).

  • Bind a Pay Token to an agent when issuing it (agentId) → spend is attributed to that agent.
  • Per-agent rollup — budget, spend, calls, last-used in the dashboard.
  • Kill switch — pause / resume / revoke an agent; bound tokens are rejected at the gateway instantly (AGENT_PAUSED / AGENT_REVOKED), even with budget remaining.
  • Server-authoritative — price is set on the endpoint; agents never carry a card or a seller key.
bash
# manage agents (owner-authenticated)POST /api/agents            # create  → { agent_id, ... }POST /api/agents/:id/pause  # kill switch (also /resume, /revoke)GET  /api/agents            # list + per-agent spend rollup

✨ Features

For agents / buyers

  • ✅ x402 native — 402 challenge returns accepts[] with price + mintUrl
  • ✅ Hard-capped — per-mint / daily / monthly limits, server-enforced
  • ✅ Off-session top-up — agent self-funds via Buyer Key (bk_...), no prompts
  • ✅ Demo Mode — 8 free tools, try without any setup

For API providers / sellers

  • ✅ 5-min go-live — npx create-lemon-mcp, or lc.charge() on any tool, or route through the gateway
  • ✅ Custody-free — Stripe Connect Direct Charge, 97% goes directly to seller
  • ✅ Usage ledger — every call recorded, revenue visible in dashboard
  • ✅ Buy link — share one URL, buyers self-serve

For agent fleets / operators

  • ✅ Per-agent identity — bind Pay Tokens to an agent, attribute spend
  • ✅ Per-agent kill switch — pause / resume / revoke, enforced at the gateway
  • ✅ Spend rollup — budget / spent / calls per agent
  • ✅ No balance pool — custody-free; budget = the agent's bound Pay Tokens

Infrastructure

  • 🔧 Stripe Connect Direct Charge (no custody)
  • 🔧 x402 gateway with WWW-Authenticate: Lemoncake-Prepaid
  • 🔧 EN / 日本語 / Español dashboard
  • 🔧 JP FSA: registration not required (confirmed 2026-06)

🏗 Architecture

┌─────────────────────────────────────────────────┐│  Buyer / Agent                                  ││   ↳ prepays via card OR Buyer Key (bk_...)      ││   ↳ receives Pay Token (signed JWT)             │└──────────────────────┬──────────────────────────┘                       │  Authorization: Bearer <jwt>                       ▼┌─────────────────────────────────────────────────┐│  LemonCake Gateway  /g/<shortId>                ││   ↳ verify JWT signature                        ││   ↳ check budget + calls + rate limit           ││   ↳ decrement spend, write to ledger            │└──────────────────────┬──────────────────────────┘                       │  HTTPS + upstream_auth (hidden)                       ▼┌─────────────────────────────────────────────────┐│  Your API / MCP server (unchanged)              │└─────────────────────────────────────────────────┘

LemonCake is the middle box. It never holds funds — money flows Stripe → seller via Direct Charge.


🌍 Compliance

Japan FSA Fintech Support Desk (2026-06) confirmed: no registration required. Custody-free design (Stripe Connect Direct Charge, no pooled balance).

JurisdictionBasis
🇯🇵 JapanFSA — registration not required
🇺🇸 USAFinCEN 2019 §4.5 — non-custodial software ≠ MSB
🇪🇺 EUMiCA — non-CASP
🇬🇧 UKFCA — Tech Service Provider
🇸🇬 SingaporeMAS — DPT non-applicable
🇨🇦 CanadaFINTRAC — non-custodial exemption
🇨🇭 SwitzerlandFINMA — non-financial intermediary

See lemoncake.xyz/security


🔌 Package family

PackageWhat it does
agent-payment-mcpMain entry — x402 gateway + agent payment rail
@lemon-cake/mcp-sdkSeller SDK — lc.charge() / lc.protect(), fiat, no crypto
create-lemon-mcpScaffold a paid MCP server — sandbox→prod with one env var
xstocks-mcpBuy tokenized US stocks on Solana
alpaca-guard-mcpAlpaca paper / live trading with hard daily cap
tokenized-stock-mcpDinari dShares

🛡 Security

  • Server-side hard caps — per-mint / daily / monthly, cannot be exceeded
  • Pay Token = signed JWT — HS256, verified on every gateway call
  • upstream_auth never exposed — seller's real API key hidden from buyers
  • RLS on all DB tables — Supabase row-level security enabled
  • Stripe Connect Direct Charge — LemonCake never holds funds

來源:README.md,提交 f28f563

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分