for developers & autonomous agents

Agent console

Everything an agent needs to find skills, read their MCP tool schemas, and call them through one gateway. Discovery is free; billable calls settle on-chain in USDC via x402 — the platform signs each payment from your custodial wallet, within the caps you set.

One MCP endpointPay per call · USDC on BaseNo SDK required

Overview

How it works

Three ideas carry the whole system. Connect once, let the platform handle payment, and stay in control with limits you define.

One endpoint

Connect a single MCP server. MCPORT routes to every seller behind it, tools namespaced per skill. The catalog grows without reconfiguring your client.

Custodial wallet

You top up USDC; the platform holds it and signs each x402 payment on the agent's behalf. Agents never handle keys or sign transactions themselves.

Spending caps

Set per-day and per-call limits. The gateway refuses any call that would exceed them — the agent can never overspend without your sign-off.

Example spending caps

Per day$25.00

Per call$0.50

Illustrative values — set your own from the dashboard or with the set_spending_cap tool.

Connect

Point a client at the gateway

MCP is JSON-RPC over HTTP, so there's no SDK to install. Configure any MCP client with the aggregated endpoint, or call it directly from your own code.

https://mcport-api.uptopia.xyz

# Recommended: no key to copy. Your MCP client opens a browser to sign in.
claude mcp add --transport http mcport https://mcport-api.uptopia.xyz/mcp

# Or in mcp.json — the client discovers OAuth via the gateway:
{
"mcpServers": {
  "mcport": { "url": "https://mcport-api.uptopia.xyz/mcp" }
}
}

Two kinds of endpoint

Aggregate — every skill in one connection

https://mcport-api.uptopia.xyz/mcp

One connection exposes tools/listfor every skill you've enabled, plus the built-in account tools (search_skills, enable_skill, check_balance, and more). This is what the connect flow and the client picker below set up by default — best when your agent should be able to reach your whole account from one server entry.

Per-listing — one specific skill

https://mcport-api.uptopia.xyz/v1/mcp/{listingId}

tools/liston this endpoint returns only that one listing's own tools — nothing else you've enabled shows up, and tools/callonly works once you've enabled that specific skill. Use this when an agent should be restricted to a single skill. {listingId}is the skill's slug, shown in its detail-page URL and in your buyer dashboard — the "Connect agent" tab on a skill's own detail page already fills this in for you.

Connect

Connect an AI agent

Point any of these MCP clients at the gateway. Every value below comes from the same config MCPORT uses in the connect flow and buyer dashboard — nothing here should ever drift from what you see in the app.

Pick your client

Claude Code

Claude Code discovers the authorization server automatically and opens a browser to sign in — no key to copy or store.

https://mcport-api.uptopia.xyz

claude mcp add --transport http mcport https://mcport-api.uptopia.xyz/mcp

Sign inAfter adding the server, start Claude Code and run /mcp — it opens your browser to sign in on the first connect, then the tools are ready to call.

Claude Code MCP docs ↗

Authentication

Two ways to connect, one account

An API key and an interactive OAuth login resolve to the same account, wallet, and spending controls — so a developer and an autonomous agent share one access and billing model.

API key

Set a bearer key in the client environment. Best for headless agents and CI.

OAuth at the MCP

Authorize interactively at the endpoint. Best for user-driven MCP clients.

https://mcport-api.uptopia.xyz

Authorization: Bearer <AGENT_KEY>
Content-Type: application/json

Key scopes

mcp:read discovers and reads schemas; mcp:call invokes tools and pays. Least-privilege by default.

Rotation

Revoke a leaked key instantly — in-flight calls fail closed. Keys never expire unless revoked.

Discover

A catalog agents can read

Everything a human sees in the marketplace has an API equivalent. Search it with built-in tools over MCP, or over plain REST.

One shared endpoint — the MCPORT MCP

Connect a single endpoint and MCPORT routes to every listed seller behind it. Tools are namespaced per seller, and your agent opts into skills at runtime. One wallet, one bill, a catalog that grows without reconfiguring.

MCPhttps://mcport-api.uptopia.xyz/mcp

Built-in tools an agent can call on its own

search_skills

Find MCPs, skills or workflows for a stated need (semantic search + filters).

get_skill

Return a listing’s tools and JSON schemas.

get_pricing

Return per-call or per-execution price for a listing.

enable_skill

Add a skill to the caller’s active toolset.

disable_skill

Remove a skill from the caller’s active toolset.

check_balance

Report the current USDC balance.

get_usage

Return calls and spend over a period.

set_spending_cap

Set a per-day or per-skill spending limit.

estimate_cost

Project spend for a given skill and call volume.

add_fundssoon

Return a Base Pay / on-ramp link to top up USDC.

GET/v1/catalog?search=web&category=search&type=mcp&sort=popular&page=1&page_size=12

The REST equivalent of search_skills — filter by search, category, type and sort, paginated with page / page_size. Returns listings with prices, tool schemas and ratings, ready to rank and call.

Call & pay

x402 payment, step by step

Billable tools use /v1/mcp/{listingId} with a Bearer key and an Idempotency-Key. Free methods like initialize and tools/list bypass billing entirely.

1Request

Client posts a tools/call JSON-RPC request to /v1/mcp/{listingId}.

2Platform signs

The gateway checks funds and your daily cap, then signs payment from the custodial wallet.

3Capture

PAYMENT-RESPONSE is returned only after the payment is captured on-chain.

https://mcport-api.uptopia.xyz

HTTP/1.1 200 OK
PAYMENT-RESPONSE: <captured-payment>
Content-Type: application/json

{
"jsonrpc": "2.0",
"id": 1,
"result": { "content": [] }
}

Seller guide

List a skill in the marketplace

Everything above is the buying side. This is the other one: a four-step wizard at Seller dashboard → Create listing, followed by an automated security check and an admin review. Connect a wallet first — payouts settle to the Base wallet on your account.

MCP server

A live endpoint you host. Give the URL and transport (HTTP or SSE) and MCPORT connects to it, discovering every tool and its JSON schema from the running server. Each tool is then priced on its own.

Skill or Workflow

A downloadable ZIP bundle — no endpoint, no tool schemas. Buyer and agent instructions belong in SKILL.md (or README.md / workflow.json) at the root of the ZIP. The bundle is malware-scanned before it can go live.

Step 1

Endpoint or bundle

Pick the type first — it drives every step after it and can't be changed once the listing exists. MCP takes an endpoint URL and transport, which MCPORT checks live; Skill and Workflow take a ZIP upload.

Step 2

Pricing

MCP listings price each tool per call; a bundle takes one price, or free. What you enter is what the buyer pays — you receive that minus MCPORT's 5% fee. Paid prices start at $0.01 with up to 6 decimals, and 0 means free. Always USDC on Base.

Step 3

Details

Only the name and short description are required — category, icon, tags, readme, docs URL and support contact are all optional. MCP listings get one request/response sample per discovered tool, prefilled from its schema; workflows need at least one step title.

Step 4

Review & submit

Check the catalog card, then submit. A hosted endpoint runs the security precheck first — MCPORT discovers and actually calls every tool live, so a flagged response blocks the submission and counts as a warning on your account. Bundles must pass the malware scan instead.

After you submit

Draft

Saved but not submitted — visible only to you.

In review

Precheck or bundle scan passed; waiting on an admin.

Live

In the catalog. Agents can connect and pay per call.

An admin approves the listing to Live, or sends it back to Draft with a reason. Editing a live listing also returns it to Draft — resubmit and it is re-reviewed before agents can call it again.

Minimum to submit

A name, a short description, and — depending on the type — either an endpoint with at least one discovered tool priced at $0.01 or more (or 0 for free), or a ZIP bundle that passes the scan. Workflows also need one step title. Icon, category, tags, readme, docs URL, support contact and samples are all optional and can improve after the listing is live.

Trust & safety

Security & Abuse policy

MCPORT runs independent monitoring on every call that passes through the gateway, looking for prompt-injection attempts and other adversarial behavior directed at agents or the payment flow. This runs on every listing, regardless of what the listing itself claims about its own safety.

Continuous detection

Every call is screened for deliberate, malicious behavior — not just at listing submission. Detection is independent of the listing and cannot be disabled by a seller.

No payout on a confirmed attack

When a call is confirmed as a deliberate attack, settlement is stopped: the listing behind it is not paid, and the buyer is not charged for that call.

Three strikes, permanent ban

Confirmed violations are tracked per seller account, across all of that seller's listings. A third confirmed violation results in the account being permanently banned from the marketplace, with no reinstatement.

Specific detection methods and thresholds are not published, by design — this keeps the policy effective rather than something to route around.

Troubleshooting

Errors & how to fix them

The gateway returns a JSON body of the shape { "error": { "code", "message" } }with a matching HTTP status. The ones you're most likely to hit:

401missing_api_key

No Authorization header on the request. Send Authorization: Bearer <your mcpk_… key>.

401invalid_api_key

The key is wrong, malformed, or revoked. Check the value; rotate and use a fresh key if it was revoked.

403insufficient_api_key_scope

The key lacks the scope this call needs. Discovery needs mcp:read; tools/call needs mcp:call. Add the scope to the key.

403not_enabled

The skill isn’t enabled for your account. Call enable_skill (or enable it in the dashboard) before calling the tool.

429spending_cap_exceeded

The call would exceed your per-day or per-call cap. Raise the cap with set_spending_cap, or wait for the daily reset.

402payment_required

The platform couldn’t reserve or capture payment. Check the USDC balance and that the cap allows the amount, then retry.

5xxsettlement_failed

Payment reached settlement but didn’t complete on-chain. Retry after confirming capture status — the call isn’t billed until captured.

Still stuck? Check the wallet balance and recent spend with check_balance and get_usage, or review caps and funding from your dashboard.

Agent console

One MCP endpointPay per call · USDC on BaseNo SDK required

# Recommended: no key to copy. Your MCP client opens a browser to sign in. claude mcp add --transport http mcport https://mcport-api.uptopia.xyz/mcp # Or in mcp.json — the client discovers OAuth via the gateway: { "mcpServers": { "mcport": { "url": "https://mcport-api.uptopia.xyz/mcp" } } }