Is com.supplyslate/sourcing up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://mcp.supplyslate.com/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Could not tell (HTTP 401)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Could not tell (HTTP 401).https://mcp.supplyslate.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Could not tell (HTTP 401)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (HTTP 401)./.well-known/http-message-signatures-directory |
Read at https://mcp.supplyslate.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 55 tools: ask_rfq_clarification, attach_artifact_reference, create_artifact_upload, create_catalog_import, create_project, create_provider_checkout_handoff, create_purchase_plan, decide_supplier_order_cancellation, decline_supplier_rfq, describe_supplyslate, get_bom, get_checkout_handoffs, get_compatibility, get_connection_guide, get_live_fabrication_capabilities, get_order, get_product, get_project, get_purchase_plan, get_requirement_schema, get_sourcing_request, get_supplier, get_supplier_offers, get_supplier_profile, get_supplier_rfq, list_fabrication_processes, list_orders, list_project_validations, list_sourcing_categories, list_sourcing_requests, list_supplier_orders, list_supplier_rfqs, list_supplier_taxonomy, open_warranty_claim, report_order_issue, request_order_cancellation, request_order_return, request_purchase_approval, revise_supplier_quote, search_live_components, search_products, search_suppliers, source_project, submit_sourcing_request, submit_supplier_quote, update_availability, update_project_requirements, update_supplier_capabilities, update_supplier_order, update_supplier_order_issue, update_supplier_order_return, update_supplier_warranty_claim, upsert_bom, upsert_supplier_catalog, validate_project.
No change to its tools between 2026-09 and 2026-10.
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.supplyslate/sourcing |
|---|---|
| Endpoint | https://mcp.supplyslate.com/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt