Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fabric Marketplace

REMOTE · FABRIC-API-393345198409.US-WEST1.RUN.APP · SCANNED SEP 20

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

0 this week 86 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1256 tokens (~34/item across 36 items; 7 tools + 29 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Fabric Marketplace MCP server?

Fabric Marketplace is a hosted endpoint at https://fabric-api-393345198409.us-west1.run.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · fabric-api-393345198409.us-west1.run.app

# add to Claude Code
claude mcp add --transport http fabric-protocol-fabric 'https://fabric-api-393345198409.us-west1.run.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "fabric-protocol-fabric": {
      "url": "https://fabric-api-393345198409.us-west1.run.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fabric-protocol-fabric": {
      "type": "http",
      "url": "https://fabric-api-393345198409.us-west1.run.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.fabric-protocol-fabric]
url = "https://fabric-api-393345198409.us-west1.run.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fabric-protocol-fabric": {
      "type": "remote",
      "url": "https://fabric-api-393345198409.us-west1.run.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fabric-protocol-fabric --url 'https://fabric-api-393345198409.us-west1.run.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fabric-protocol-fabric:
    url: "https://fabric-api-393345198409.us-west1.run.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fabric-protocol-fabric": {
      "Transport": "http",
      "Url": "https://fabric-api-393345198409.us-west1.run.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add fabric-protocol-fabric -t streamable-http -u 'https://fabric-api-393345198409.us-west1.run.app/mcp'
// mcp.json
{
  "mcpServers": {
    "fabric-protocol-fabric": {
      "type": "http",
      "url": "https://fabric-api-393345198409.us-west1.run.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Sept 26 0
    • Schema quality: good → excellent functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://fabric-api-393345198409.us-west1.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WR2,O=Google Trust Services,C=US 4 Sept 2026 27 Nov 2026 ECDSA 256 SHA256-RSA a6993fec773504b312550b7de9609011
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WR2,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a07c4cded100ad9d66a5107b98
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fabric-api-393345198409.us-west1.run.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
run.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; style-src 'unsafe-inline'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fabric-api-393345198409.us-west1.run.app/mcp Verified 200
http (plaintext) http://fabric-api-393345198409.us-west1.run.app/mcp HTTPS enforced 302 https://fabric-api-393345198409.us-west1.run.app/mcp
MCP tools · 7 exposed · ~696 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fabric_create_identity ~257

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.

NameTypeReqDescription
confirm_new_identitybooleanyesRequired safety confirmation. Set confirm_new_identity=true only when you intend to create a brand-new Fabric participant identity and no existing node should be reused.
display_namestringyesDisplay name for the new node.
emailstring|nullOptional email for account recovery.
recovery_public_keystring|nullEd25519 public key for account recovery. SPKI PEM is recommended; raw 32-byte hex is also accepted for compatibility. Strongly recommended for autonomous recovery. Also verify email as a backup lane.
referral_codestring|nullOptional referral code from another node.

No output schema declared.

No examples provided.

fabric_get_categories ~40

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fabric_get_meta ~39

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fabric_get_regions ~46

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fabric_login_session ~53

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.

NameTypeReqDescription
api_keystringyesFabric API key from bootstrap or key management.

No output schema declared.

No examples provided.

fabric_recovery_complete ~123

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.

NameTypeReqDescription
challenge_idstringyesThe challenge_id returned by fabric_recovery_start.
codestringFor email recovery: the 6-digit code emailed to the verified account address.
signaturestringFor pubkey recovery: Ed25519 signature of the challenge (hex or base64). Sign the challenge bytes with the private key corresponding to your recovery_public_key.

No output schema declared.

No examples provided.

fabric_recovery_start ~138

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.

NameTypeReqDescription
emailstringRequired for method=email. Must match a verified email already on the node.
methodstringyesRecovery method. Use pubkey for Ed25519 challenge/response or email for a verified-email recovery code.
node_idstringRequired for method=pubkey. Your node ID (UUID from the original bootstrap response).

No output schema declared.

No examples provided.

Common questions

What is the Fabric Marketplace MCP server?

Fabric Marketplace is an MCP server listed in the public MCP registry as io.github.Fabric-Protocol/fabric. Agent-native marketplace. Bootstrap, list inventory, search, negotiate, and trade via MCP. This page covers its hosted endpoint (https://fabric-api-393345198409.us-west1.run.app/mcp).

Is the Fabric Marketplace MCP server safe to use?

Fabric Marketplace scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Fabric Marketplace MCP server expose?

Fabric Marketplace exposes 7 tools: fabric_get_meta, fabric_create_identity, fabric_login_session, fabric_recovery_start, fabric_recovery_complete, and 2 more. Their descriptions and schemas cost roughly 696 tokens of context every time the server is loaded.

Does the Fabric Marketplace MCP server require authentication?

No. We connected to Fabric Marketplace without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Fabric Marketplace MCP server still maintained?

Fabric Marketplace is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.