MCP.so
Sign In
H

HIVE402 MCP Server

@Script Master Labs

Basic information

Transport

streamable-http

Authentication

None

Last updated

Category

Finance & Commerce

Author

Script Master Labs

About HIVE402 MCP Server

HIVE402 is an x402 marketplace from Script Master Labs that lets AI agents discover paid API endpoints and plan purchases. Its remote MCP server has no-auth discovery tools for searching the catalog and listings, plus tools to plan multi-step missions and prepare and submit x402 payments.

Connection details

https://hive402.scriptmasterlabs.com/mcp

Setup

claude mcp add hive402 --transport http https://hive402.scriptmasterlabs.com/mcp

HIVE402 MCP Server tools

17

Search live paid x402 endpoints settled by OMNIGATE or 402Proof, filtered by text, network and max price.

Get full details for one marketplace listing by id, including example input and output.

Request a listing unpaid and return its live x402 payment challenge plus the exact steps to pay through OMNIGATE or 402Proof. Nothing is charged.

List your own x402 endpoint in the market for free. It is called unpaid and listed only if it returns a valid x402 v2 challenge on an OMNIGATE or 402Proof network. Settlement defaults to direct to your payTo at 0% HIVE402 take; pass settlement_route 'omnigate' to opt in to OMNIGATE routing (Base USDC only: receipt token per settlement, 0.005 USDC fee inside settlement, waived inside the daily budget).

Suggest up to three live catalog services for a task on one payment rail, within a spending ceiling. No payment or task execution occurs; review endpoint inputs and fee legs. Rail and asset must be a settleable pair (canonical map, src/rails.mjs): Base/Arc/Solana settle in USDC, XRPL in XRP or RLUSD, Xahau in XAH, MultiversX in EGLD, MEX or USDC — any other pair is rejected with an error, never silently re-railed.

Get reusable catalog-matched task templates with current listing IDs on a single rail. Templates are not verified completed workflows; budget is expressed in atomic units.

Probe up to three catalog endpoints unpaid and rank valid live payment challenges by observed response time. Does not measure historical uptime, paid success or outcome quality.

Recheck an approved listing's current x402 challenge against expected payout, rail, price and remaining atomic budget. For XRP (402Proof, website-verified sellers) and Base USDC (OMNIGATE, verified-payable sellers) steps the result carries execution.available with an executionToken when tracked execution is offered. Caller must inspect fees and sign; this tool never pays.

Compare caller-held snapshots with the live public catalog for price, payment-term and catalog-presence changes. Callers retain snapshots and schedule polling; no push delivery.

Submit a caller-signed Mission payment for a prepared step and record confirmed settlement once. XRP steps: signedTxBlob (the caller's signed XRP transaction) settles through the verified seller's 402Proof key; fees accrued = HIVE402 platform fee 10% plus 402Proof facilitator fee $0.0100, kept separate. Base USDC steps: paymentPayload (decoded x402 payload object carrying the EIP-3009 signature + authorization) or paymentSignature (the same payload base64-encoded, as in the PAYMENT-SIGNATURE header) settles through OMNIGATE; fees accrued = HIVE402 platform fee 10% plus the OMNIGATE facilitator fee from the settlement receipt (0.005 USDC when charged, 0 when waived), kept separate. Base settlement is recorded only after OMNIGATE success AND on-chain confirmation. Exactly one payment form must be supplied, matching the prepared step's rail. Never signs or holds funds; does not execute seller task inputs.

Read the HIVE402 Board — the market's public message board: ScriptMasterLabs announcements, system posts generated at read time from live catalog and subscription data (aggregate counts only), and posts from claimed operator profiles (new products, upgrades, announcements, requests). Free and read-only. The same content is at GET /api/public/board.

Describe what you need; get the best payable x402 endpoint plus fallbacks, each re-challenged live seconds ago, with payment requirements and exact call instructions. Optionally validates your input against each candidate's schema.

Forwards one call to a catalog listing. Without payment_signature returns the decoded 402 challenge. With payment_signature (base64 PAYMENT-SIGNATURE you signed) forwards it untouched and returns the seller's response and receipt. HIVE402 never signs or re-sends a paid call.

Search the catalog ranked by relevance × trust × on-chain demand × latency × price, with score breakdowns and intel fields.

Explained 0–100 trust score for one listing: probe uptime, on-chain demand, call spec, latency, operator claim, and junk/sanctions flags.

Side-by-side price, trust, uptime, latency and real demand for 2–10 listings.

Check an input against a listing's call spec and get the exact request to send.

Overview

What it is

HIVE402 is a marketplace of paid API endpoints that settle with the x402 payment protocol. The MCP server lets an agent browse the catalog and work through purchases.

What it can do

  • search_catalog, get_listing, list_endpoint: browse listings and endpoints
  • start_purchase, prepare_mission_step, submit_mission_payment: run x402 purchases
  • plan_mission, get_recipes, check_services, check_watchlist: plan multi-step tasks and monitor services

Connect

Remote endpoint (Streamable HTTP): https://hive402.scriptmasterlabs.com/mcp.

Authentication and limits

Discovery needs no authentication; purchases are paid through x402.

Sources

Frequently asked questions

1

What is the HIVE402 remote MCP server?

The HIVE402 remote MCP server is a hosted Model Context Protocol endpoint at https://hive402.scriptmasterlabs.com/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the HIVE402 MCP server?

Add the endpoint https://hive402.scriptmasterlabs.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the HIVE402 MCP server require authentication?

No. HIVE402's MCP server does not require authentication — you can connect directly with the endpoint URL.

4

Which transport does the HIVE402 MCP server use?

HIVE402 exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments