For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-30T11:15:19.289950+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://mcp.supplyslate.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T11:15:19.289950+00:00",
"registry_status": null,
"subject": {
"id": "com.supplyslate/sourcing",
"kind": "mcp"
},
"tools": {
"names": [
"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"
],
"names_truncated": false,
"sha256": "9e0f3aee6339db7f198f47de3e2da5bbf7b46c9deb90b5793e12c93e958fb3cc"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T11:15:19.289950+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology