# SupplySlate

> Agent-native supply network for components, fabrication, industrial RFQs, offers, and fulfillment.

- name: com.supplyslate/sourcing
- version: 2.0.0
- connection class: R0 (autonomous)
- trust: 76/100 flags: no-repository
- quality: 89/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.supplyslate%2Fsourcing
- tools: https://api.protogrid.dev/v1/servers/com.supplyslate%2Fsourcing/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "sourcing": {
      "type": "http",
      "url": "https://mcp.supplyslate.com/mcp",
      "headers": {
        "Authorization": "Bearer ${SOURCING_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${SOURCING_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 98
- freshness: 85
- provenance: 45
- drivers: +dns-namespace +reachable +uptime-95% ~updated-61d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 55 of 55 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- warn `tools.token_cost`: about 13,400 tokens to load every tool
- warn `tools.api_dump`: 55 tools, 64% named like REST operations: looks like an API mapped one endpoint per tool

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 55, about 13,400 tokens to load them all
- tool set hash: cf3aca6839f3cc9cd6efd09dc6208d42
- badge: [![protogrid quality](https://protogrid.dev/badge/com.supplyslate/sourcing.svg)](https://protogrid.dev/servers/com.supplyslate/sourcing)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.supplyslate.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.94690263)

## Packages

_none_

## Tools (55)

- `ask_rfq_clarification`: Ask the buyer a clarification question on an approved supplier RFQ without changing the immutable request package.
- `attach_artifact_reference`: Attach an HTTPS repository, document, drawing, datasheet, BOM, or design reference to the current project revision without copying its bytes. Private or expiring URLs remain the buyer's responsibility until uploaded directly.
- `create_artifact_upload`: Create a short-lived, one-time private artifact upload URL. The caller must stream the exact declared bytes with a SHA-256 checksum.
- `create_catalog_import`: Create a durable CSV, XLSX, JSON, feed, API, document, or manual catalog import. Supply parsed rows for immediate validation, or an artifact/source reference to enter the mapping workflow.
- `create_project`: Create a durable supply project from an idea, file, BOM, exact part, or RFQ origin. Requires a scoped buyer credential.
- `create_provider_checkout_handoff`: After a human has approved the exact purchase plan, create one supplier-hosted payment link for a checkout-connected provider offer. This creates an unpaid provider order but never submits payment or exposes payment credentials to SupplySlate.
- `create_purchase_plan`: Create an immutable, single-currency, multi-supplier purchase plan from selected current quote lines, choosing at most one commercial option per requested line. This records a plan only; it neither approves nor purchases anything.
- `decide_supplier_order_cancellation`: Accept or reject a buyer cancellation request for the authenticated supplier's unshipped merchant order. Acceptance is the state-changing merchant decision.
- `decline_supplier_rfq`: Decline an approved RFQ with a structured reason so the buyer and network can route more accurately.
- `describe_supplyslate`: Explain what SupplySlate does, what it does not do, and when a buyer-owned agent should use it.
- `get_bom`: Read the current revision of one project BOM, including hierarchy, quantities, sourcing state, and interface dependencies.
- `get_checkout_handoffs`: List merchant-hosted checkout, supplier invoice, or merchant-order handoffs for an approved plan. Suppliers remain merchant of record and SupplySlate does not process funds.
- `get_compatibility`: Read one published compatibility or substitution assertion with exact subject, object, conditions, confidence, evidence source, and observation time.
- `get_connection_guide`: Return the exact MCP and REST connection details a buyer, developer, or agent operator needs to connect to SupplySlate.
- `get_live_fabrication_capabilities`: Read attributed live fabrication capabilities from the connected AFN provider. This is discovery only and neither uploads a design nor requests a quote.
- `get_order`: Read one merchant-confirmed order with items, fulfillment, shipments, issues, evidence, and event history.
- `get_product`: Read one published canonical product with variants, category links, evidence scope, observation dates, and freshness.
- `get_project`: Read a project, its current immutable-capable revision, requirements, artifacts, BOM summaries, and validation history.
- `get_purchase_plan`: Read one exact purchase-plan version with selected lines, merchants, totals, risks, evidence, approvals, and checkout handoffs.
- `get_requirement_schema`: Read the evidence-safe input schema for a configurable supply category or fabrication process, including required fields, recommended fields, accepted artifacts, and safety notes.
- `get_sourcing_request`: Read the current status and normalized line items for one authenticated buyer sourcing request.
- `get_supplier`: Read one public supplier profile with source URLs and evidence for every category, capability, and brand claim.
- `get_supplier_offers`: Retrieve current normalized supplier quote revisions for one buyer sourcing request, including unquoted lines, compatibility, price, availability, lead time, terms, and evidence. SupplySlate returns explicit tradeoffs and applies no hidden winner score.
- `get_supplier_profile`: Read the authenticated supplier's SupplySlate profile and current catalog-item count. Requires a supplier API key.
- `get_supplier_rfq`: Read an approved RFQ and its normalized buyer line items. Requires a supplier API key.
- `list_fabrication_processes`: List configurable fabrication, kitting, assembly, and test processes with their required artifacts and requirement schemas.
- `list_orders`: List merchant-confirmed orders for the buyer organization. A plan or queued handoff is never represented as an order.
- `list_project_validations`: List versioned validation reports for a project without implying licensed engineering approval.
- `list_sourcing_categories`: List the editable supply categories currently accepting requests. Agents may still submit a precise request outside this list.
- `list_sourcing_requests`: List recent sourcing requests owned by the authenticated buyer organization across API keys and OAuth agents.
- `list_supplier_orders`: List merchant-confirmed orders attributable to the authenticated supplier. RFQs, quotes, plans, and checkout handoffs are not represented as orders.
- `list_supplier_rfqs`: List approved RFQs matched to the authenticated supplier. Requires a supplier API key.
- `list_supplier_taxonomy`: List the product categories used by the public industrial compressor service-parts supplier directory, including verified supplier counts.
- `open_warranty_claim`: Open a durable warranty claim on an accepted order or specific order line. This records the claim and notifies the supplier without asserting eligibility or approval.
- `report_order_issue`: Open a durable post-purchase issue for a merchant-confirmed order. This notifies the supplier-side organization and records owner, status, and event history; it does not claim a resolution.
- `request_order_cancellation`: Ask the merchant to cancel an unshipped order. This creates a request and notification; it never reports the order as cancelled until the supplier or an operator accepts it.
- `request_order_return`: Open a return request after shipment. The supplier remains merchant of record and controls authorization and refund state.
- `request_purchase_approval`: Create a human review link bound to the exact purchase-plan version, suppliers, maximum amount, currency, risks, and expiry. This does not approve or purchase the plan.
- `revise_supplier_quote`: Create a new immutable revision of a supplier quote. The previous revision remains in history and the new revision becomes current.
- `search_live_components`: Search attributed current electronic-component product, availability, lead-time, and price data from Mouser. Results retain provider, observation time, and merchant URLs; no checkout or order is created.
- `search_products`: Search published canonical product facts. Commercial price, stock, compatibility, and lead time are returned only when separately supported by current evidence.
- `search_suppliers`: Search source-backed public supplier profiles by product category, brand, company type, service, compressor type, industry, or text. No authentication required.
- `source_project`: Lock the validated project revision into an immutable sourcing package, create normalized request lines, and return transparent supplier candidates. This does not contact suppliers; a human operator must approve every outbound recipient, message, and artifact scope.
- `submit_sourcing_request`: Submit a real non-sensitive B2B sourcing request on behalf of the buyer. SupplySlate routes it to relevant suppliers and returns structured offers later. Requires a buyer API key.
- `submit_supplier_quote`: Submit the first structured commercial quote for a human-approved RFQ. Money is integer minor units with an explicit currency; partial line coverage and labeled alternatives are allowed.
- `update_availability`: Append timestamped supplier availability evidence and update current catalog state by supplier SKU without rewriting historical snapshots.
- `update_project_requirements`: Replace the structured requirement set on an unlocked project revision. Confirmed flags distinguish buyer-confirmed facts from agent interpretation.
- `update_supplier_capabilities`: Replace the supplier-submitted capability set while preserving separately sourced public, operator-verified, and transaction-proven evidence.
- `update_supplier_order`: Acknowledge or update fulfillment on a merchant-confirmed supplier order, optionally recording a shipment. State transitions and order-item quantities are validated and audited.
- `update_supplier_order_issue`: Update ownership, status, or resolution for a buyer-reported issue on the authenticated supplier's merchant order.
- `update_supplier_order_return`: Advance an authenticated supplier return through authorization, shipment, receipt, and refund states without changing historical order evidence.
- `update_supplier_warranty_claim`: Advance a warranty claim through supplier review, approval, replacement, resolution, or rejection with a merchant reference and durable history.
- `upsert_bom`: Create a BOM or a new BOM revision with assemblies, catalog items, custom parts, services, consumables, artifacts, and interface dependencies.
- `upsert_supplier_catalog`: Create or update normalized supplier catalog items through a durable manual import with row-level validation, history, evidence scope, availability, and commercial terms.
- `validate_project`: Run the current versioned validators and return separate blocking errors, compatibility conflicts, warnings, missing information, passed checks, and unavailable checks.