SupplySlate
REMOTE · MCP.SUPPLYSLATE.COM · SCANNED OCT 2
Agent-native supply network for components, fabrication, industrial RFQs, offers, and fulfillment.
Available components
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3694 tokens (~67/item across 55 items; 55 tools + 0 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 Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 55 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SupplySlate MCP server?
SupplySlate is a hosted endpoint at https://mcp.supplyslate.com/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 · mcp.supplyslate.com
claude mcp add --transport http com-supplyslate-sourcing 'https://mcp.supplyslate.com/mcp'
{
"mcpServers": {
"com-supplyslate-sourcing": {
"url": "https://mcp.supplyslate.com/mcp"
}
}
} {
"servers": {
"com-supplyslate-sourcing": {
"type": "http",
"url": "https://mcp.supplyslate.com/mcp"
}
}
} [mcp_servers.com-supplyslate-sourcing] url = "https://mcp.supplyslate.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-supplyslate-sourcing": {
"type": "remote",
"url": "https://mcp.supplyslate.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-supplyslate-sourcing --url 'https://mcp.supplyslate.com/mcp' --transport streamable-http
mcp_servers:
com-supplyslate-sourcing:
url: "https://mcp.supplyslate.com/mcp" {
"McpServers": {
"com-supplyslate-sourcing": {
"Transport": "http",
"Url": "https://mcp.supplyslate.com/mcp"
}
}
} assistant mcp add com-supplyslate-sourcing -t streamable-http -u 'https://mcp.supplyslate.com/mcp'
{
"mcpServers": {
"com-supplyslate-sourcing": {
"type": "http",
"url": "https://mcp.supplyslate.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 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
- 25 Sept 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
- 8 Sept 26 +1
- Stability: fail → pass ▲ security
- 7 Sept 26 −1
- Stability: pass → fail ▼ security
- 5 Sept 26 0
- Stability: 0.97 → pass security
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 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
- 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
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 2 Oct 2026 · Probed https://mcp.supplyslate.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supplyslate.com | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 6cf50b171c37eaba13152fc521393ff3 |
| SANs: supplyslate.com, mcp.supplyslate.com, *.mcp.supplyslate.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.supplyslate.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| supplyslate.com. | 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 |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.supplyslate.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.supplyslate.com/mcp | Inconclusive | 405 |
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 →
update_supplier_order_return ~86
Advance an authenticated supplier return through authorization, shipment, receipt, and refund states without changing historical order evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| merchant_return_reference | string | – | – |
| note | string | – | – |
| order_id | string | yes | – |
| refund_amount_minor | integer | – | – |
| return_id | string | yes | – |
| status | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| order | object | yes | – |
No examples provided.
update_supplier_warranty_claim ~74
Advance a warranty claim through supplier review, approval, replacement, resolution, or rejection with a merchant reference and durable history.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| order_id | string | yes | – |
| status | string | yes | – |
| supplier_reference | string | – | – |
| warranty_claim_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| order | object | yes | – |
No examples provided.
upsert_bom ~93
Create a BOM or a new BOM revision with assemblies, catalog items, custom parts, services, consumables, artifacts, and interface dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| bom_id | string | – | – |
| build_quantity | number | – | – |
| dependencies | array | – | – |
| items | array | yes | – |
| name | string | yes | – |
| project_id | string | yes | – |
| source_artifact_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bom | object | yes | – |
No examples provided.
upsert_supplier_catalog ~55
Create or update normalized supplier catalog items through a durable manual import with row-level validation, history, evidence scope, availability, and commercial terms.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| items | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_import | object | yes | – |
No examples provided.
validate_project ~43
Run the current versioned validators and return separate blocking errors, compatibility conflicts, warnings, missing information, passed checks, and unavailable checks.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| validation | object | yes | – |
No examples provided.
What is the SupplySlate MCP server?
SupplySlate is an MCP server listed in the public MCP registry as com.supplyslate/sourcing. Agent-native supply network for components, fabrication, industrial RFQs, offers, and fulfillment. This page covers its hosted endpoint (https://mcp.supplyslate.com/mcp).
Is the SupplySlate MCP server safe to use?
SupplySlate scores 81 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 SupplySlate MCP server expose?
SupplySlate exposes 55 tools: describe_supplyslate, list_sourcing_categories, get_connection_guide, list_fabrication_processes, get_live_fabrication_capabilities, and 50 more. Their descriptions and schemas cost roughly 3,694 tokens of context every time the server is loaded.
Does the SupplySlate MCP server require authentication?
No. We connected to SupplySlate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SupplySlate MCP server still maintained?
SupplySlate is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.