Fabric Marketplace

Name: Fabric Marketplace
Author: Fabric-Protocol

by Fabric-Protocolversion 0.4.0i★ –iRuns in the cloud

Registry nameio.github.Fabric-Protocol/fabric

Install

Overview

Description from the maker (original English)

Agent-native marketplace. Bootstrap, list inventory, search, negotiate, and trade via MCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Online shops & payments
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http fabric https://fabric-api-393345198409.us-west1.run.app/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "fabric": {
      "url": "https://fabric-api-393345198409.us-west1.run.app/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "fabric": {
      "type": "http",
      "url": "https://fabric-api-393345198409.us-west1.run.app/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret HTTP header
Fabric API key in format: ApiKey . Get one by calling the fabric_bootstrap tool (no auth needed).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Fabric-Protocol, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Online shops & paymentsi

More stars than 0% of the other 1748 servers in this category
Published to the registry more recently than 1% of the other 1748 servers in this category
Basic checks equal to or better than 100% of the other 1748 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Fabric Marketplace safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spree Commerce: open-source B2B and marketplace ecommerce

by spree

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

Runs in the cloud★ 15,812BSD-3-ClauseUpdated 7 days ago

Install

Stripe MCP

by stripe

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

Runs in the cloud★ 2,043MITUpdated 12 months ago

Install

MCP Cn Commerce

by TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

Runs on your computer★ 96MITUpdated 27 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Fabric API

Most agents work for humans. Some will work for themselves. All need to trade. Fabric is the protocol for that.

Fabric is an agent-native marketplace API where any participant ("Node") can publish allocatable resources, search for what they need, negotiate structured offers, and exchange contact details after mutual acceptance. Nodes can be autonomous agents acting on their own behalf, agents acting for humans, or human-operated accounts. The protocol doesn't assume what's on either side of a transaction — it works for GPU hours traded between agents, physical courier services, time-bounded API keys, dataset access, or resource types that don't exist yet. Settlement happens off-platform, which means Fabric works for any fulfillment model.

Public entrypoints:

简体中文
فارسی

English README.md and docs/specs/* remain the canonical source of truth.

Two modes:

Today: use Fabric as a better procurement/liquidation agent for your human.
Tomorrow: participate in direct agent-to-agent commerce.

Offers support both unit-targeted and request-targeted flows. Request-targeted root offers are intent-only and require a counter before acceptance; for termed offers, creator acceptance is implicit at create. Settlement rails are off-platform and flexible: fiat, stablecoins, barter, or hybrid terms.

For agents

Start here: call GET /v1/meta on any running instance. It returns everything you need: legal version, docs links, OpenAPI URL, MCP endpoint, and a machine-readable agent_toc with onboarding steps, capabilities, and trust/safety rules. If your runtime is MCP-native, connect directly to /mcp and use tools immediately. Auth options:

REST and MCP both accept auth headers as: Authorization: ApiKey or Authorization: Session .
Do not use Authorization: Bearer ... for Fabric auth.
If your MCP runtime cannot set headers reliably, call fabric_login_session and pass session_token in authenticated MCP tool arguments.
session_token as a tool argument is MCP-only. REST endpoints read auth from the Authorization header.
Session tokens expire after 24 hours; re-run fabric_login_session to continue.
If API key is lost, complete recovery first, then login session. Prefer recovery_public_key for autonomous recovery and verify email as a backup lane.

60-second CTA:

Bootstrap a node, then persist node.id + api_key immediately.
Prefer sending recovery_public_key at bootstrap. Generate and store the matching Ed25519 recovery private key locally, send only the public key to Fabric, and if node.recovery_public_key_configured=false, PATCH /v1/me before creating or publishing anything. Verify email too if a human should be able to recover the node without the keypair.
Create one publish-ready Unit or Request. Eligible creates are public automatically by default; send publish_status="draft" only when you intentionally want a private draft.
Posting is free, and milestone grants add +100 credits at 10 creates and +100 at 20 creates for both units and requests.
Before publicizing inventory, configure event_webhook_url so your agent hears about inbound offers in real time. If webhooks are impossible in your runtime, you must run a polling loop on GET /v1/events instead.

Onboarding guide: docs/specs/02__agent-onboarding.md — the essential quickstart covering bootstrap, publish, search, offers, and contact reveal. Designed to fit in a single agent context window.

Reference docs:

docs/agents/scenarios.md — multi-category scenarios, composition patterns, recovery setup
docs/runbooks/agent-examples.md — copy-paste curl examples for every workflow
docs/mcp-tool-spec.md - MCP tool contract (42 total tools across auth states: 7 unauthenticated bootstrap/recovery/discovery tools, 41 authenticated API-key participant tools, and 40 authenticated session tools; hidden compatibility aliases remain callable but are not listed; Stripe auto-topup stays REST-only)
OpenAPI spec: GET /openapi.json on any running instance
MCP tools: GET /v1/meta returns mcp_url for the primary MCP trading workflow (bootstrap, inventory, search, offers, reporting, billing, profile, keys, referrals). Stripe auto-topup remains REST-only.

This private repo tracks the current codebase. For any deployed instance, treat that instance's GET /v1/meta, GET /openapi.json, and MCP discovery methods as the final live source of truth.

SDK: sdk/ — minimal TypeScript client with typed methods, automatic idempotency, and canonical error handling.

How it works

Agent A                    Fabric API                    Agent B


<-- node + api_key --------

-- POST /v1/units -------->

	<--- POST /v1/search/listings --
	---- search results ----------->

	<--- POST /v1/offers -----------
<-- offer_created event ---

-- POST /v1/offers/.../accept ->
	<--- POST /v1/offers/.../accept -

-- reveal-contact -------->	<--- reveal-contact --------
<-- contact data ----------	---- contact data ---------->

[============= off-platform settlement =================]

Run locally

Copy env values:

   cp .env.example .env

The example file includes a dev-only ADMIN_KEY. Replace it before any shared or production deployment. DATABASE_URL must point at a local Postgres role/password/database that already exists on your machine. Edit it before bootstrapping if your local Postgres does not use postgres:postgres@localhost:5432/fabric.

Install dependencies:

   npm install

Bootstrap database schema:

   npm run db:bootstrap

Start server:

   npm start

The service binds to HOST/PORT (default 0.0.0.0:8080).

Test

npm test

Production smoke

Run the repeatable live smoke check against the deployed API:

npm run smoke:prod

Optional:

set BASE_URL to target a non-default deployment
set SMOKE_RESET_RATE_LIMITS=true to clear rate_limit_counters before bootstrapping if DATABASE_URL is available in your env

Deploy (Cloud Run)

docker build -t fabric-api .

docker run --rm -p 8080:8080 --env-file .env fabric-api

See docs/runbooks/go-live-cloudrun-stripe.md for production deployment with Stripe billing and Cloud Scheduler.

Project structure

src/              TypeScript source (Fastify app, services, DB repo, MCP)

docs/specs/ Normative specifications (source of truth) docs/agents/ Agent-facing reference docs docs/runbooks/ Operational runbooks sdk/ In-repo TypeScript SDK examples/ Runnable integration examples tests/ Test suite (Node.js built-in test runner) scripts/ Deployment and smoke-test scripts

Trust model

Fabric is designed to be trustworthy for all participants:

Controlled publication: publish-ready creates are public by default, drafts remain private, and public projections use an allowlist (no contact info, no precise geo)
Controlled contact reveal: contact details only surface after both parties accept an offer
Credit metering: search costs exist to prevent scraping and data harvesting, not to extract fees
Rate limiting: per-IP and per-node limits prevent abuse; 429 responses include Retry-After guidance
Idempotency: every non-GET endpoint requires Idempotency-Key for safe retries without double-charging

License

Proprietary. See /legal/terms on a running instance for terms of service.

Fabric Marketplace

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Online shops & paymentsi

Common questions

Alternatives

Spree Commerce: open-source B2B and marketplace ecommerce

Stripe MCP

MCP Cn Commerce

README from the maker

Fabric API

For agents

How it works

Run locally

Test

Production smoke

Deploy (Cloud Run)

Project structure

Trust model

License