Skip to main content
Glama

Fabric Marketplace

by io.github.Fabric-Protocol

Server Details

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

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
Fabric-Protocol/fabric
GitHub Stars
1
Server Listing
Fabric Marketplace

Available Tools

7 tools
fabric_create_identityAInspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
emailNoOptional email for account recovery.
display_nameYesDisplay name for the new node.
referral_codeNoOptional referral code from another node.
recovery_public_keyNoEd25519 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.
confirm_new_identityYesRequired 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.

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are all false and provide minimal behavioral hints. The description compensates by disclosing that the tool creates a new identity, requires no authentication, returns specific items, and mandates post-creation steps (persist node.id/api_key, configure recovery_public_key, configure webhook/polling). It also warns against using it when an existing node exists, implying non-idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is about five sentences long, with each sentence carrying distinct, non-redundant information: purpose, non-credential-refresh clarification, usage alternatives, auth requirement, return values, and post-creation actions. It is front-loaded with the core action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there is no output schema, the description appropriately enumerates return values (node profile, API key, credit grant, setup guidance) and includes both prerequisites and follow-up steps. This makes it complete for a creation tool without requiring external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides 100% description coverage for all five parameters, including detailed semantics for recovery_public_key. The description adds only minor extra context (e.g., 'configure recovery_public_key') but does not need to compensate since schema coverage is high. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Create a new Fabric participant identity (node) and receive an API key + 500 free credits,' which clearly identifies the verb, resource, and outcome. It also differentiates from siblings by explicitly stating it is not a credential refresh tool and referencing login_session/recovery as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use and when-not-to-use guidance: 'Do not use this if the participant already has a node' and directs to alternatives (fabric_login_session when headers are unavailable, recovery if the API key is lost). It also notes that no authentication is required, which is a key prerequisite.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fabric_get_categoriesA
Read-onlyIdempotent
Inspect

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

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this as readOnly, idempotent, and not destructive. The description adds value beyond those by disclosing 'No authentication required,' which is a behavioral trait not present in the annotations. It also describes the data fields returned. There is no contradiction or missing critical behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler. The first sentence front-loads the core function and expected output, the second gives actionable usage guidance and an access note. Every sentence earns its place, and the text is appropriately sized for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema, the description compensates by explicitly listing the data fields (IDs, slugs, names, descriptions, examples). It covers access requirements (no auth) and how to apply the result (use IDs when creating units/requests). For a parameterless read-only getter, this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the schema is an empty object, so schema coverage is effectively 100%. Per the guidelines, 0 parameters gives a baseline of 4. The description adds no parameter-level detail because there are none, but it does explain the purpose of the returned data, which is sufficient for this tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'Get the full category registry', a specific verb+resource combination that clearly states what the tool does. It also enumerates the contents (IDs, slugs, names, descriptions, examples), which further clarifies the purpose and distinguishes it from siblings like fabric_get_meta or fabric_get_regions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context: 'Use category IDs when creating units/requests.' This tells the agent when to use the tool's output. It also notes 'No authentication required,' which sets expectations. However, it does not explicitly name alternative tools or state when not to use this tool, so it stops short of full exclusionary guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fabric_get_metaA
Read-onlyIdempotent
Inspect

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

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds behavioral value by stating 'No authentication required,' which is not captured in annotations. It also implies the returned metadata is needed before bootstrap, giving context beyond safety hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the action ('Get Fabric service metadata') and followed by essential context (no auth, before bootstrap). Every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple metadata fetch with no parameters and no output schema. The description covers purpose, the type of data returned, authentication requirements, and when to call it, making it complete for an agent to select and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description doesn't need to explain parameters since there are none. No additional parameter info is necessary.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets Fabric service metadata, listing specific content (legal version, API version, URLs). It distinguishes itself from sibling tools like fabric_get_categories and fabric_get_regions by covering general service metadata rather than a specific subset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage guidance: 'Call this before bootstrap to discover the service.' This communicates when to use it. It doesn't explicitly mention alternatives or when not to use it, but the context is clear enough for a simple metadata retrieval tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fabric_get_regionsA
Read-onlyIdempotent
Inspect

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

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable extra context: 'No authentication required' discloses an important access requirement, and 'Returns ISO 3166-1/2 codes' clarifies the output format, which is crucial since no output schema exists. This goes beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—two short sentences that front-load the purpose and immediately provide key behavioral details (no auth, output format). Every word earns its place, with no redundant or irrelevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with zero parameters, no output schema, and simple functionality, the description is complete. It states the purpose, specifies the output type (ISO codes with examples), and notes authentication requirements. Nothing essential is missing for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

This tool has zero parameters, so the baseline is 4. The description does not need to explain parameter meanings. The empty input schema covers parameter details, and the description adds no parameter-specific information because none exists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Get supported region codes for search filters and scope fields.' It uses a specific verb and resource, and the mention of 'region codes' distinguishes it from siblings like fabric_get_categories (categories) and fabric_get_meta (meta).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context by stating the codes are for 'search filters and scope fields,' implying when the tool is relevant. It does not explicitly mention alternatives or when not to use it, but the sibling tools cover different domains, so the context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fabric_login_sessionAInspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
api_keyYesFabric API key from bootstrap or key management.

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are all false, providing no behavioral hints. The description adds that the token is short-lived and that no authentication is required, which goes beyond the schema. However, it does not disclose details like token lifespan, side effects, or error conditions, leaving a transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with the action. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool, the description covers purpose, usage context, and a constraint. It lacks mention of token usage or specific expiry, but the 'short-lived' qualifier and the provided context suffice. Given low complexity, it is relatively complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already describes the api_key parameter. The tool description does not add additional meaning beyond the schema, so with high schema coverage, a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a short-lived MCP session token from an API key, with a specific verb and resource. It distinguishes itself from sibling tools like fabric_create_identity and fabric_get_categories by focusing on session token creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Use this when your MCP runtime cannot reliably set Authorization headers', providing a clear condition for use. However, it does not mention when not to use it or alternative tools, so it lacks explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fabric_recovery_completeAInspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
codeNoFor email recovery: the 6-digit code emailed to the verified account address.
signatureNoFor pubkey recovery: Ed25519 signature of the challenge (hex or base64). Sign the challenge bytes with the private key corresponding to your recovery_public_key.
challenge_idYesThe challenge_id returned by fabric_recovery_start.

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only set all hints to false, providing little safety profile. The description supplements this by disclosing the return value (new API key), the two input options (signature/code), and the lack of authentication. It does not go into side effects or failure modes, but annotations are not contradicted, and the added context covers the essential behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences convey the core action, both input modes, output, and an important condition (no authentication). No filler or repetition; every sentence is essential and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly states the return value. It explains both recovery paths and the challenge_id prerequisite. The tool is simple enough (3 parameters, no enums) that all essential usage context is covered in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions cover all parameters (100%), and the description adds the key semantic that 'signature' and 'code' are mutually exclusive alternatives. This clarifies the relationship between the three parameters beyond the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Complete account recovery') and clearly states the outcome ('Returns a new API key'). It distinguishes from the sibling fabric_recovery_start by implying this is the follow-up step, but it does not explicitly name the former.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after fabric_recovery_start by referencing 'challenge_id' and the two alternative recovery modes. It also adds a key condition: 'No authentication required.' It does not explicitly contrast with alternatives, keeping it a point short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fabric_recovery_startAInspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
emailNoRequired for method=email. Must match a verified email already on the node.
methodYesRecovery method. Use pubkey for Ed25519 challenge/response or email for a verified-email recovery code.
node_idNoRequired for method=pubkey. Your node ID (UUID from the original bootstrap response).

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With all annotations being false, the description compensates by stating 'No authentication required' and describing the expected outputs (a nonce for pubkey, a 6-digit recovery code for email). This adds behavioral context beyond the annotations, though it does not fully articulate server-side side effects or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the primary purpose, then immediately providing actionable method-specific guidance. Every sentence contributes value with no redundancy, achieving excellent conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite lacking an output schema, the description explicitly tells the caller what they will receive for each method (nonce or recovery code) and the prerequisites (verified email, node ID). This is sufficient for an agent to invoke the tool correctly, especially given the sibling fabric_recovery_complete for the next step.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description reinforces the relationships between method and the other parameters but does not add substantially new semantic information beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description precisely states 'Start account recovery if you lost your API key', using a specific verb and resource. It also outlines two distinct methods (pubkey and email) with their respective parameters, making it clearly distinguishable from the sibling tool fabric_recovery_complete which handles the next step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear use cases (when you lost your API key) and detailed instructions for each method, including requirements like node_id for pubkey and a verified email for email. It does not explicitly mention when not to use this tool or alternatives, but the context is clear enough to guide correct selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 3 tool updates
    • Changedfabric_create_identity1 field changed
      • changedInput schema / properties / recovery_public_key / description
        Previous value: -"Ed25519 public key for account recovery. SPKI PEM is recommended; raw 32-byte hex is also accepted for compatibility. Strongly recommended — without this, a lost API key cannot be recovered."New value: +"Ed25519 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."
    • Changedfabric_recovery_complete3 fields changed
      • addedInput schema / properties / code
        Added value: +{
+  "description": "For email recovery: the 6-digit code emailed to the verified account address.",
+  "type": "string"
+}
      • changedInput schema / properties / signature / description
        Previous value: -"Ed25519 signature of the challenge (hex or base64). Sign the challenge bytes with the private key corresponding to your recovery_public_key."New value: +"For pubkey recovery: Ed25519 signature of the challenge (hex or base64). Sign the challenge bytes with the private key corresponding to your recovery_public_key."
      • changedInput schema / required
        Previous value: -[
-  "challenge_id",
-  "signature"
-]New value: +[
+  "challenge_id"
+]
    • Changedfabric_recovery_start4 fields changed
      • addedInput schema / properties / email
        Added value: +{
+  "description": "Required for method=email. Must match a verified email already on the node.",
+  "type": "string"
+}
      • addedInput schema / properties / method
        Added value: +{
+  "description": "Recovery method. Use pubkey for Ed25519 challenge/response or email for a verified-email recovery code.",
+  "enum": [
+    "pubkey",
+    "email"
+  ],
+  "type": "string"
+}
      • changedInput schema / properties / node_id / description
        Previous value: -"Your node ID (UUID from the original bootstrap response)."New value: +"Required for method=pubkey. Your node ID (UUID from the original bootstrap response)."
      • changedInput schema / required
        Previous value: -[
-  "node_id"
-]New value: +[
+  "method"
+]
  2. 23 tool updates
    • Removedfabric_auth_keys
    • Removedfabric_bootstrap
    • Addedfabric_create_identity
    • Removedfabric_create_inventory
    • Removedfabric_decide_offer
    • Removedfabric_delete_inventory
    • Removedfabric_get_billing_info
    • Removedfabric_get_events
    • Removedfabric_get_inventory
    • Removedfabric_get_node_inventory
    • Removedfabric_get_nodes_categories_summary
    • Removedfabric_get_offers
    • Removedfabric_list_inventory
    • Removedfabric_logout_session
    • Removedfabric_profile
    • Removedfabric_referrals
    • Removedfabric_report_offer
    • Removedfabric_reveal_contact
    • Removedfabric_search
    • Removedfabric_set_inventory_visibility
    • Removedfabric_start_purchase
    • Removedfabric_update_inventory
    • Removedfabric_write_offer
  3. 59 tool updates
    • Removedfabric_accept_offer
    • Addedfabric_auth_keys
    • Removedfabric_buy_credit_pack_crypto
    • Removedfabric_buy_credit_pack_stripe
    • Removedfabric_cancel_offer
    • Removedfabric_claim_referral
    • Removedfabric_counter_offer
    • Removedfabric_create_auth_key
    • Addedfabric_create_inventory
    • Removedfabric_create_offer
    • Removedfabric_create_request
    • Removedfabric_create_unit
    • Addedfabric_decide_offer
    • Addedfabric_delete_inventory
    • Removedfabric_delete_request
    • Removedfabric_delete_unit
    • Addedfabric_get_billing_info
    • Removedfabric_get_credit_quote
    • Removedfabric_get_credits
    • Removedfabric_get_crypto_currencies
    • Addedfabric_get_inventory
    • Removedfabric_get_ledger
    • Addedfabric_get_node_inventory
    • Removedfabric_get_node_listings
    • Removedfabric_get_node_listings_by_category
    • Removedfabric_get_node_requests
    • Removedfabric_get_node_requests_by_category
    • Removedfabric_get_offer
    • Addedfabric_get_offers
    • Removedfabric_get_profile
    • Removedfabric_get_referral_code
    • Removedfabric_get_referral_stats
    • Removedfabric_get_request
    • Removedfabric_get_unit
    • Removedfabric_list_auth_keys
    • Addedfabric_list_inventory
    • Removedfabric_list_offers
    • Removedfabric_list_requests
    • Removedfabric_list_units
    • Addedfabric_profile
    • Removedfabric_publish_request
    • Removedfabric_publish_unit
    • Addedfabric_referrals
    • Removedfabric_reject_offer
    • Addedfabric_report_offer
    • Removedfabric_revoke_auth_key
    • Addedfabric_search
    • Removedfabric_search_listings
    • Removedfabric_search_requests
    • Addedfabric_set_inventory_visibility
    • Addedfabric_start_purchase
    • Removedfabric_subscribe_stripe
    • Removedfabric_unpublish_request
    • Removedfabric_unpublish_unit
    • Addedfabric_update_inventory
    • Removedfabric_update_profile
    • Removedfabric_update_request
    • Removedfabric_update_unit
    • Addedfabric_write_offer
  4. 4 tool updates
    • Changedfabric_create_request1 field changed
      • addedInput schema / properties / publish_status
        Added value: +{
+  "description": "Optional create-time visibility override. Omit to auto-publish when the payload is publish-ready; use draft to force a private draft.",
+  "enum": [
+    "draft",
+    "published",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_create_unit1 field changed
      • addedInput schema / properties / publish_status
        Added value: +{
+  "description": "Optional create-time visibility override. Omit to auto-publish when the payload is publish-ready; use draft to force a private draft.",
+  "enum": [
+    "draft",
+    "published",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_update_request1 field changed
      • addedInput schema / properties / publish_status
        Added value: +{
+  "description": "Optional create-time visibility override. Omit to auto-publish when the payload is publish-ready; use draft to force a private draft.",
+  "enum": [
+    "draft",
+    "published",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_update_unit1 field changed
      • addedInput schema / properties / publish_status
        Added value: +{
+  "description": "Optional create-time visibility override. Omit to auto-publish when the payload is publish-ready; use draft to force a private draft.",
+  "enum": [
+    "draft",
+    "published",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
  5. 2 tool updates
    • Changedfabric_bootstrap1 field changed
      • changedInput schema / properties / recovery_public_key / description
        Previous value: -"Ed25519 public key (hex) for account recovery. Strongly recommended — without this, a lost API key cannot be recovered."New value: +"Ed25519 public key for account recovery. SPKI PEM is recommended; raw 32-byte hex is also accepted for compatibility. Strongly recommended — without this, a lost API key cannot be recovered."
    • Changedfabric_recovery_complete1 field changed
      • changedInput schema / properties / signature / description
        Previous value: -"Ed25519 signature of the challenge (hex-encoded). Sign the challenge bytes with the private key corresponding to your recovery_public_key."New value: +"Ed25519 signature of the challenge (hex or base64). Sign the challenge bytes with the private key corresponding to your recovery_public_key."
  6. 47 tool updates
    • Changedfabric_accept_offer1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_buy_credit_pack_crypto1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_buy_credit_pack_stripe1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_cancel_offer1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_claim_referral1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_counter_offer1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_create_auth_key1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_create_offer1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_create_request1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_create_unit1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_delete_request1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_delete_unit1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_credit_quote1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_credits1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_crypto_currencies1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_events1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_ledger1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_node_listings1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_node_listings_by_category1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_node_requests1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_node_requests_by_category1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_nodes_categories_summary1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_offer1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_profile1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_referral_code1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_referral_stats1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_request1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_get_unit1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_list_auth_keys1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_list_offers1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_list_requests1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_list_units1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Addedfabric_login_session
    • Addedfabric_logout_session
    • Changedfabric_publish_request1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_publish_unit1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_reject_offer1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_reveal_contact1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_revoke_auth_key1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_search_listings1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_search_requests1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_subscribe_stripe1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_unpublish_request1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_unpublish_unit1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_update_profile1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_update_request1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_update_unit1 field changed
      • addedInput schema / properties / session_token
        Added value: +{
+  "description": "Optional session token from fabric_login_session. Use when your MCP client cannot set Authorization headers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  7. 7 tool updates
    • Changedfabric_bootstrap1 field changed
      • addedInput schema / properties / recovery_public_key
        Added value: +{
+  "description": "Ed25519 public key (hex) for account recovery. Strongly recommended — without this, a lost API key cannot be recovered.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • Changedfabric_buy_credit_pack_stripe5 fields changed
      • changedInput schema / properties / cancel_url / description
        Previous value: -"URL to redirect to if payment is cancelled."New value: +"URL to redirect to if payment is cancelled. Optional — auto-generated if omitted."
      • changedInput schema / properties / cancel_url / type
        Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
      • changedInput schema / properties / success_url / description
        Previous value: -"URL to redirect to after successful payment."New value: +"URL to redirect to after successful payment. Optional — auto-generated if omitted."
      • changedInput schema / properties / success_url / type
        Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
      • changedInput schema / required
        Previous value: -[
-  "pack_code",
-  "success_url",
-  "cancel_url"
-]New value: +[
+  "pack_code"
+]
    • Addedfabric_recovery_complete
    • Addedfabric_recovery_start
    • Changedfabric_search_listings3 fields changed
      • changedInput schema / properties / filters / description
        Previous value: -"Structured filters (category_ids_any, region, etc.)."New value: +"Scope-specific filters. REQUIRED per scope: local_in_person → regions OR (center + radius_miles); remote_online_service → regions; ship_to → ship_to_regions; digital_delivery → no required filters; OTHER → scope_notes."
      • addedInput schema / properties / filters / properties
        Added value: +{
+  "category_ids_any": {
+    "description": "Match listings in any of these category IDs.",
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  },
+  "center": {
+    "description": "Geo-center for local_in_person search. Required with radius_miles (unless regions provided).",
+    "properties": {
+      "lat": {
+        "type": "number"
+      },
+      "lon": {
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "max_ship_days": {
+    "description": "Max shipping days (1-30). Optional for ship_to scope.",
+    "type": "number"
+  },
+  "radius_miles": {
+    "description": "Radius in miles (1-200) for local_in_person center-based search.",
+    "type": "number"
+  },
+  "regions": {
+    "description": "ISO region codes (e.g. [\"US\"]). Required for remote_online_service and local_in_person (unless center provided).",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "scope_notes": {
+    "description": "Free-text scope description. Required for OTHER scope.",
+    "type": "string"
+  },
+  "ship_to_regions": {
+    "description": "ISO region codes for destination. Required for ship_to scope.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "ships_from_regions": {
+    "description": "ISO region codes for origin. Optional for ship_to scope.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
      • changedInput schema / properties / scope / description
        Previous value: -"Primary modality for the search (determines required filters)."New value: +"Primary modality for the search. Each scope requires specific filters — see \"filters\" description."
    • Changedfabric_search_requests3 fields changed
      • changedInput schema / properties / filters / description
        Previous value: -"Structured filters (category_ids_any, region, etc.)."New value: +"Scope-specific filters. REQUIRED per scope: local_in_person → regions OR (center + radius_miles); remote_online_service → regions; ship_to → ship_to_regions; digital_delivery → no required filters; OTHER → scope_notes."
      • addedInput schema / properties / filters / properties
        Added value: +{
+  "category_ids_any": {
+    "description": "Match listings in any of these category IDs.",
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  },
+  "center": {
+    "description": "Geo-center for local_in_person search. Required with radius_miles (unless regions provided).",
+    "properties": {
+      "lat": {
+        "type": "number"
+      },
+      "lon": {
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "max_ship_days": {
+    "description": "Max shipping days (1-30). Optional for ship_to scope.",
+    "type": "number"
+  },
+  "radius_miles": {
+    "description": "Radius in miles (1-200) for local_in_person center-based search.",
+    "type": "number"
+  },
+  "regions": {
+    "description": "ISO region codes (e.g. [\"US\"]). Required for remote_online_service and local_in_person (unless center provided).",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "scope_notes": {
+    "description": "Free-text scope description. Required for OTHER scope.",
+    "type": "string"
+  },
+  "ship_to_regions": {
+    "description": "ISO region codes for destination. Required for ship_to scope.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "ships_from_regions": {
+    "description": "ISO region codes for origin. Optional for ship_to scope.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
      • changedInput schema / properties / scope / description
        Previous value: -"Primary modality for the search (determines required filters)."New value: +"Primary modality for the search. Each scope requires specific filters — see \"filters\" description."
    • Changedfabric_subscribe_stripe5 fields changed
      • changedInput schema / properties / cancel_url / description
        Previous value: -"URL to redirect to if signup is cancelled."New value: +"URL to redirect to if signup is cancelled. Optional — auto-generated if omitted."
      • changedInput schema / properties / cancel_url / type
        Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
      • changedInput schema / properties / success_url / description
        Previous value: -"URL to redirect to after successful signup."New value: +"URL to redirect to after successful signup. Optional — auto-generated if omitted."
      • changedInput schema / properties / success_url / type
        Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
      • changedInput schema / required
        Previous value: -[
-  "plan_code",
-  "success_url",
-  "cancel_url"
-]New value: +[
+  "plan_code"
+]
  8. 1 tool update
    • Changedfabric_buy_credit_pack_crypto2 fields changed
      • changedInput schema / properties / pay_currency / description
        Previous value: -"Crypto currency to pay with (e.g. \"usdcsol\", \"btc\", \"eth\"). Use fabric_get_crypto_currencies for the full list."New value: +"Must be \"usdcsol\" (USDC on Solana). Only accepted currency."
      • addedInput schema / properties / pay_currency / enum
        Added value: +[
+  "usdcsol"
+]
  9. 1 tool update
    • Changedfabric_list_offers1 field changed
      • addedInput schema / properties / request_id
        Added value: +{
+  "description": "Optional UUID — filter offers targeting this request.",
+  "type": "string"
+}
  10. 2 tool updates
    • Changedfabric_counter_offer2 fields changed
      • changedInput schema / properties / unit_ids / description
        Previous value: -"Array of unit UUIDs for the counter-offer."New value: +"Optional array of unit UUIDs for the counter-offer. Required for unit-target threads."
      • changedInput schema / required
        Previous value: -[
-  "offer_id",
-  "unit_ids"
-]New value: +[
+  "offer_id"
+]
    • Changedfabric_create_offer3 fields changed
      • addedInput schema / properties / request_id
        Added value: +{
+  "description": "Optional request UUID target. If set, note must be a non-empty string.",
+  "type": "string"
+}
      • changedInput schema / properties / unit_ids / description
        Previous value: -"Array of unit UUIDs to include in the offer (must all belong to same owner)."New value: +"Unit UUIDs. Required in unit-target mode. Optional in request-target mode (must belong to offer creator if provided)."
      • changedInput schema / required
        Previous value: -[
-  "unit_ids"
-]New value: +[]
  11. 42 tool updates
    • Addedfabric_accept_offer
    • Addedfabric_bootstrap
    • Addedfabric_buy_credit_pack_crypto
    • Addedfabric_buy_credit_pack_stripe
    • Addedfabric_cancel_offer
    • Addedfabric_claim_referral
    • Addedfabric_counter_offer
    • Addedfabric_create_auth_key
    • Addedfabric_create_offer
    • Addedfabric_create_request
    • Addedfabric_create_unit
    • Addedfabric_delete_request
    • Addedfabric_delete_unit
    • Addedfabric_get_categories
    • Addedfabric_get_credit_quote
    • Addedfabric_get_crypto_currencies
    • Addedfabric_get_ledger
    • Addedfabric_get_meta
    • Addedfabric_get_node_listings
    • Addedfabric_get_node_listings_by_category
    • Addedfabric_get_node_requests
    • Addedfabric_get_node_requests_by_category
    • Addedfabric_get_nodes_categories_summary
    • Addedfabric_get_profile
    • Addedfabric_get_referral_code
    • Addedfabric_get_referral_stats
    • Addedfabric_get_regions
    • Addedfabric_list_auth_keys
    • Addedfabric_list_offers
    • Addedfabric_list_requests
    • Addedfabric_list_units
    • Addedfabric_publish_request
    • Addedfabric_publish_unit
    • Addedfabric_reject_offer
    • Addedfabric_reveal_contact
    • Addedfabric_revoke_auth_key
    • Addedfabric_subscribe_stripe
    • Addedfabric_unpublish_request
    • Addedfabric_unpublish_unit
    • Addedfabric_update_profile
    • Addedfabric_update_request
    • Addedfabric_update_unit
  12. 6 tool updates
    • Changedfabric_get_events1 field changed
      • changedInput schema / properties / since / description
        Previous value: -"Opaque cursor for strictly-after pagination."New value: +"Opaque cursor from previous response for strictly-after pagination."
    • Changedfabric_get_offer1 field changed
      • changedInput schema / properties / offer_id / description
        Previous value: -"UUID of the offer."New value: +"UUID of the offer to retrieve."
    • Changedfabric_get_request1 field changed
      • changedInput schema / properties / request_id / description
        Previous value: -"UUID of the request."New value: +"UUID of the request to retrieve."
    • Changedfabric_get_unit1 field changed
      • changedInput schema / properties / unit_id / description
        Previous value: -"UUID of the unit."New value: +"UUID of the unit to retrieve."
    • Changedfabric_search_listings10 fields changed
      • addedInput schema / properties / broadening / description
        Added value: +"Optional broadening settings (deprecated, defaults to level 0)."
      • addedInput schema / properties / broadening / properties / allow / description
        Added value: +"Allow automatic broadening."
      • addedInput schema / properties / broadening / properties / level / description
        Added value: +"Broadening level (0 = none)."
      • addedInput schema / properties / budget / description
        Added value: +"Spend ceiling for this search."
      • changedInput schema / properties / budget / properties / credits_requested / description
        Previous value: -"Maximum credits to spend."New value: +"Maximum credits to spend on this search call."
      • changedInput schema / properties / cursor / description
        Previous value: -"Pagination cursor."New value: +"Pagination cursor from a previous search response."
      • addedInput schema / properties / scope / description
        Added value: +"Primary modality for the search (determines required filters)."
      • addedInput schema / properties / target / description
        Added value: +"Optional target constraint to search a specific node."
      • addedInput schema / properties / target / properties / node_id / description
        Added value: +"Restrict search to a specific node by ID."
      • addedInput schema / properties / target / properties / username / description
        Added value: +"Restrict search to a specific node by display name."
    • Changedfabric_search_requests10 fields changed
      • addedInput schema / properties / broadening / description
        Added value: +"Optional broadening settings (deprecated, defaults to level 0)."
      • addedInput schema / properties / broadening / properties / allow / description
        Added value: +"Allow automatic broadening."
      • addedInput schema / properties / broadening / properties / level / description
        Added value: +"Broadening level (0 = none)."
      • addedInput schema / properties / budget / description
        Added value: +"Spend ceiling for this search."
      • changedInput schema / properties / budget / properties / credits_requested / description
        Previous value: -"Maximum credits to spend."New value: +"Maximum credits to spend on this search call."
      • changedInput schema / properties / cursor / description
        Previous value: -"Pagination cursor."New value: +"Pagination cursor from a previous search response."
      • addedInput schema / properties / scope / description
        Added value: +"Primary modality for the search (determines required filters)."
      • addedInput schema / properties / target / description
        Added value: +"Optional target constraint to search a specific node."
      • addedInput schema / properties / target / properties / node_id / description
        Added value: +"Restrict search to a specific node by ID."
      • addedInput schema / properties / target / properties / username / description
        Added value: +"Restrict search to a specific node by display name."
  13. 7 tool updates
    • First observedfabric_get_credits
    • First observedfabric_get_events
    • First observedfabric_get_offer
    • First observedfabric_get_request
    • First observedfabric_get_unit
    • First observedfabric_search_listings
    • First observedfabric_search_requests

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

Related MCP Servers

  • io.github.Kosta1985/relaymarke

    Kosta1985
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to discover other agents, publish and match tasks, exchange messages and artifacts, and build transaction-backed reputation over MCP and A2A.
    -
  • mcpSovereign SDK by mcpsovereign

    mcpSovereign SDKofficial

    mcpsovereign
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    A two-sided marketplace that enables AI agents to buy and sell datasets, prompt packs, and MCP tools using Bitcoin Lightning for instant settlement. It provides agents with tools to manage local stores, publish products globally, and earn credits through a specialized economy.
    388
    1
    -

  • Schelling Protocol

    codyz123
    A
    license
    Not graded
    quality
    C
    maintenance
    Universal coordination hub for AI agents. Find collaborators, negotiate terms, form contracts, and build reputation through an MCP interface. Supports natural language search across agent networks.
    4
    MIT

  • moltbridge

    SageMindAI
    A
    license
    Not graded
    quality
    D
    maintenance
    Agent network intelligence for trust verification, broker discovery, and capability matching. Ed25519 identity, graph-based trust scoring, USDC payments, and MCP tools for agent registration, search, and trust attestation.
    1,498
    5
    MIT
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

All 7 tools have clearly distinct purposes: identity creation, metadata retrieval, category/region discovery, session management, and two-step recovery. No overlap.

Naming Consistency5/5

Every tool follows the 'fabric_<verb>_<noun>' pattern with consistent snake_case. Verbs are descriptive (create, get, login, recovery_start, recovery_complete) making the convention predictable.

Tool Count5/5

7 tools cover essential identity lifecycle steps (creation, session, recovery) and discovery (categories, regions, meta). This is well-scoped for the domain without bloat.

Completeness3/5

Core creation and discovery tools exist, but missing configuration updates (e.g., webhook URL, recovery key setup) and identity deletion. The recovery flow is complete, but post-creation setup must be done manually or via other means.

Resources