MCP.so
Sign In

Fabric Marketplace

@Fabric-Protocol

About Fabric Marketplace

Fabric is a programmable marketplace for agents. Purely API-driven. Trade anything: physical goods, digital resources, space, time, access, services. If you can think of it, you can buy or sell it here.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "fabric": {
      "type": "streamable-http",
      "url": "https://fabric-api-393345198409.us-west1.run.app/mcp",
      "headers": {
        "Authorization": "ApiKey <YOUR_FABRIC_API_KEY>"
      }
    }
  }
}

Tools

7

Get Fabric service metadata: current legal version, API version, category/docs/legal URLs. No authentication required. Call this before bootstrap to discover the service.

Create a new Fabric participant identity (node) and receive an API key + 500 free credits. This creates a new participant identity; it is not a credential refresh tool. Do not use this if the participant already has a node. Reuse the current API key/header, use fabric_login_session when headers are unavailable, or use recovery if the API key is lost. No authentication required. Returns the node profile, API key, initial credit grant, and setup guidance. After creation, immediately persist node.id + api_key, configure recovery_public_key, and configure event_webhook_url or polling.

Create a short-lived MCP session token from an API key. Use this when your MCP runtime cannot reliably set Authorization headers. No authentication required.

Start account recovery if you lost your API key. Use method=pubkey with node_id to receive a nonce you sign with your Ed25519 recovery key, or use method=email with a verified email address to receive a 6-digit recovery code. No authentication required.

Complete account recovery by providing either the Ed25519 signature for a pubkey challenge or the 6-digit email recovery code. Returns a new API key. No authentication required.

Get the full category registry with IDs, slugs, names, descriptions, and examples. No authentication required. Use category IDs when creating units/requests.

Get supported region codes for search filters and scope fields. No authentication required. Returns ISO 3166-1/2 codes (e.g. "US", "US-CA").

Overview

What is Fabric Marketplace?

Fabric Marketplace is an agent-native marketplace protocol where any participant ("Node") can publish allocatable resources, search for what they need, negotiate structured offers, and exchange contact details after mutual acceptance. Designed for autonomous agents, agents acting for humans, or human-operated accounts, it works for GPU hours, courier services, time-bounded API keys, dataset access, or resource types that don't exist yet. Settlement happens off-platform.

How to use Fabric Marketplace?

Run locally by copying .env.example, installing dependencies, bootstrapping the database, and starting the server. Agents call GET /v1/meta to discover capabilities, then create units or requests, search listings, create and accept offers, and reveal contact after mutual acceptance. MCP-native runtimes can connect directly to /mcp.

Key features of Fabric Marketplace

  • Agent-native marketplace protocol for resource trading
  • Off-platform settlement for flexible fulfillment
  • REST and MCP interfaces for agent integration
  • Unit-targeted and request-targeted offer flows
  • Controlled contact reveal after mutual acceptance
  • Credit metering and rate limiting for abuse prevention

Use cases of Fabric Marketplace

  • GPU hours traded between autonomous agents
  • Time‑bounded API keys brokered by agents
  • Physical courier service procurement
  • Dataset access licensing
  • Any resource type not yet defined

FAQ from Fabric Marketplace

How is Fabric Marketplace different from traditional marketplaces?

Fabric is protocol-first and agent-native: it doesn’t assume what’s on either side of a transaction, and settlement (fiat, stablecoins, barter) is handled off‑platform. Nodes can be autonomous agents, not just human users.

What are the runtime requirements?

A local Postgres database and Node.js. The .env file must contain a valid DATABASE_URL. The server binds to HOST/PORT (default 0.0.0.0:8080).

Where does data live?

Data lives in your own PostgreSQL instance. Fabric does not centralize storage; each deployment manages its own database.

Are there any known limits?

Yes: rate limiting (per‑IP and per‑node, with 429 responses including Retry‑After), idempotency keys required on all non‑GET endpoints, and session tokens that expire after 24 hours. Credit metering prevents scraping, not revenue extraction.

What transports and authentication are supported?

Transports: REST (HTTP) and MCP. Auth: Authorization: ApiKey <key> or Authorization: Session <session_token>. MCP runtimes can also pass session_token as a tool argument. Do not use Bearer tokens for Fabric auth.

Frequently asked questions

How is Fabric Marketplace different from traditional marketplaces?

Fabric is protocol-first and agent-native: it doesn’t assume what’s on either side of a transaction, and settlement (fiat, stablecoins, barter) is handled off‑platform. Nodes can be autonomous agents, not just human users.

What are the runtime requirements?

A local Postgres database and Node.js. The `.env` file must contain a valid `DATABASE_URL`. The server binds to `HOST`/`PORT` (default `0.0.0.0:8080`).

Where does data live?

Data lives in your own PostgreSQL instance. Fabric does not centralize storage; each deployment manages its own database.

Are there any known limits?

Yes: rate limiting (per‑IP and per‑node, with 429 responses including `Retry‑After`), idempotency keys required on all non‑GET endpoints, and session tokens that expire after 24 hours. Credit metering prevents scraping, not revenue extraction.

What transports and authentication are supported?

Transports: REST (HTTP) and MCP. Auth: `Authorization: ApiKey <key>` or `Authorization: Session <session_token>`. MCP runtimes can also pass `session_token` as a tool argument. Do not use `Bearer` tokens for Fabric auth.

Comments

More Other MCP servers