# SCiMon.co RFQ Desk (remote · mcp.scimon.co)

Request quotes for custom parts, design services and box build from pre-vetted suppliers.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.scimon.co`: 74/100 (this document), [markdown](https://verifymcp.io/servers/co-scimon-rfq-desk/mcp.md), [page](https://verifymcp.io/servers/co-scimon-rfq-desk/mcp)

## Channel facts

- Endpoint: `https://mcp.scimon.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 393 tokens (~98/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 20% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SCiMon.co RFQ Desk MCP server?

SCiMon.co RFQ Desk is a hosted endpoint at https://mcp.scimon.co/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.

### Claude

```bash
claude mcp add --transport http co-scimon-rfq-desk 'https://mcp.scimon.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-scimon-rfq-desk": {
      "url": "https://mcp.scimon.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-scimon-rfq-desk": {
      "type": "http",
      "url": "https://mcp.scimon.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-scimon-rfq-desk]
url = "https://mcp.scimon.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-scimon-rfq-desk": {
      "type": "remote",
      "url": "https://mcp.scimon.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-scimon-rfq-desk --url 'https://mcp.scimon.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-scimon-rfq-desk:
    url: "https://mcp.scimon.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-scimon-rfq-desk": {
      "Transport": "http",
      "Url": "https://mcp.scimon.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-scimon-rfq-desk -t streamable-http -u 'https://mcp.scimon.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-scimon-rfq-desk": {
      "type": "http",
      "url": "https://mcp.scimon.co/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `get_capabilities` (~46 tokens)

Get SCiMon.co capabilities

What SCiMon.co can source (design services, manufacturing processes, box build, sectors, supplier countries), how vetting works, and the terms an RFQ is quoted on.

### `check_rfq` (~35 tokens)

Check an RFQ before submitting

Checks a draft RFQ and lists missing required information and recommended additions. Nothing is submitted.

Input parameters:

- `rfq` (object, required)

### `submit_rfq` (~107 tokens)

Submit an RFQ

Submits an RFQ to the SCiMon.co RFQ Desk and returns an RFQ number plus one upload link per listed file. A SCiMon sourcing expert follows up by email at contact_email. Export-controlled (ITAR, EAR, CUI) work is not accepted here.

Input parameters:

- `export_controlled` (boolean, required): True if any part or data is ITAR, EAR or CUI controlled. Must be false to submit here.
- `rfq` (object, required)

### `get_rfq_status` (~59 tokens)

Get RFQ status

Returns the status of an RFQ: Received, In progress, Quotes ready or Closed. Requires the RFQ number and the contact email it was submitted with.

Input parameters:

- `contact_email` (string, required)
- `rfq_number` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-scimon-rfq-desk/mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 68
- 2026-11-07: 68
- 2026-11-06: 67
- 2026-11-05: 67

## Common questions

### What is the SCiMon.co RFQ Desk MCP server?

SCiMon.co RFQ Desk is an MCP server listed in the public MCP registry as co.scimon/rfq-desk. Request quotes for custom parts, design services and box build from pre-vetted suppliers. This page covers its hosted endpoint (https://mcp.scimon.co/mcp).

### Is the SCiMon.co RFQ Desk MCP server safe to use?

SCiMon.co RFQ Desk scores 74 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 SCiMon.co RFQ Desk MCP server expose?

SCiMon.co RFQ Desk exposes 4 tools: get_capabilities, check_rfq, submit_rfq, get_rfq_status. Their descriptions and schemas cost roughly 247 tokens of context every time the server is loaded.

### Does the SCiMon.co RFQ Desk MCP server require authentication?

No. We connected to SCiMon.co RFQ Desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SCiMon.co RFQ Desk MCP server still maintained?

SCiMon.co RFQ Desk is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SCiMon.co RFQ Desk MCP server?

VerifyMCP ran 13 checks on SCiMon.co RFQ Desk, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.scimon.co/mcp
- Website: https://scimon.co/agents.html
- Changelog RSS feed: https://verifymcp.io/servers/co-scimon-rfq-desk/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-scimon-rfq-desk/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-scimon-rfq-desk/mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-scimon-rfq-desk/mcp
