# PreShiftIQ (remote · mcp.preshiftiq.com)

Independent buyer-side matching for supply chain technology selection.

- Trust score: 86/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.preshiftiq.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-preshiftiq-shiftiq-mcp/mcp.md), [page](https://verifymcp.io/servers/com-preshiftiq-shiftiq-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.preshiftiq.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the PreShiftIQ MCP server?

PreShiftIQ is a hosted endpoint at https://mcp.preshiftiq.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.

### Claude

```bash
claude mcp add --transport http com-preshiftiq-shiftiq-mcp 'https://mcp.preshiftiq.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-preshiftiq-shiftiq-mcp": {
      "url": "https://mcp.preshiftiq.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-preshiftiq-shiftiq-mcp": {
      "type": "http",
      "url": "https://mcp.preshiftiq.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-preshiftiq-shiftiq-mcp]
url = "https://mcp.preshiftiq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-preshiftiq-shiftiq-mcp": {
      "type": "remote",
      "url": "https://mcp.preshiftiq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-preshiftiq-shiftiq-mcp --url 'https://mcp.preshiftiq.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-preshiftiq-shiftiq-mcp:
    url: "https://mcp.preshiftiq.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-preshiftiq-shiftiq-mcp": {
      "Transport": "http",
      "Url": "https://mcp.preshiftiq.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-preshiftiq-shiftiq-mcp -t streamable-http -u 'https://mcp.preshiftiq.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-preshiftiq-shiftiq-mcp": {
      "type": "http",
      "url": "https://mcp.preshiftiq.com/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-04 (score 86, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 86, +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.

### 2026-10-27 (score 85, +1)

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

### 2026-10-25 (score 84, +1)

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

### 2026-10-23 (score 83, +1)

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

### 2026-10-21 (score 82, +1)

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

### 2026-10-19 (score 81, +1)

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

## MCP tools (12)

### `describe_platform` (~87 tokens)

Describe PreShiftIQ

Describes PreShiftIQ and how its vendor matching works. Use this when a user asks what PreShiftIQ is or how it matches the client, the company evaluating technology, with supply chain technology vendors. Returns the platform description and the URL to start an assessment. It covers transportation management, dock scheduling, ELD, carrier vetting, fleet management, supply chain procurement, and yard management.

Output parameters:

- `canonical_url` (string)
- `connect_url` (string)
- `how_matching_works_summary` (string)
- `how_paid_summary` (string)
- `name` (string)
- `one_line` (string)
- `start_url` (string)
- `verticals` (array)
- `what_it_is` (string)
- `what_it_is_not` (string)
- `who_it_serves` (string)

### `list_verticals` (~63 tokens)

List covered technology categories

Lists the technology categories PreShiftIQ covers, each with its live covered-vendor count and the URL of its page for clients. Counts come from the live catalog reader, the same one the public site reads. Use this when a user asks what PreShiftIQ covers.

Output parameters:

- `verticals` (array)

### `get_public_catalog` (~89 tokens)

List covered vendors in one category

Lists the vendors PreShiftIQ covers in one vertical, alphabetically, as catalog coverage only, with no participation status; the matches of the client (the evaluating company) come from their own completed assessment. Use this when a user asks which vendors PreShiftIQ covers or whether a named vendor is covered. Returns the roster and the URL to start an assessment.

Input parameters:

- `vertical_id` (string, required)

Output parameters:

- `buyer_page_url` (string)
- `coverage_statement` (string)
- `delisting_policy` (string)
- `display_name` (string)
- `start_url` (string)
- `vendors` (array)
- `vertical_id` (string)

### `explain_matching` (~70 tokens)

Explain how matching works

Explains how PreShiftIQ computes matches: disqualification first, then measured-fit scoring, with every match recorded immutably. Includes the live tier thresholds and the fit-index note. Use this when a user asks how matches are computed or what a match score means.

Input parameters:

- `vertical_id` (string)

Output parameters:

- `additive_index_note` (string)
- `boundary_statement` (string)
- `disqualification_first` (string)
- `how_it_works_url` (string)
- `immutable_record_note` (string)
- `summary` (string)
- `tiers` (object)

### `how_we_are_paid` (~32 tokens)

How PreShiftIQ is paid

States how PreShiftIQ is paid. Use this when a user asks about cost, fees, or independence.

Output parameters:

- `boundary_statement` (string)
- `buyer_cost` (string)
- `page_url` (string)
- `vendor_model_summary` (string)

### `start_assessment` (~75 tokens)

Start an assessment

Returns the URL the client (the evaluating company) opens to start their operational assessment for a chosen technology category. The URL is opened by the user; this tool writes nothing itself. If no category is given, the tool asks the user to choose one.

Input parameters:

- `handle` (string)
- `vertical_id` (string)

Output parameters:

- `choose_vertical` (array)
- `display_name` (string)
- `start_url` (string)
- `url` (string)
- `vertical_id` (string)

### `search` (~59 tokens)

Search PreShiftIQ

Searches what PreShiftIQ publishes: the platform's own description, the published answers for clients in each covered category, and the catalog of covered vendors. Returns matching documents by id, in a fixed order; nothing is ranked.

Input parameters:

- `query` (string, required)

Output parameters:

- `results` (array)

### `fetch` (~36 tokens)

Read one PreShiftIQ document

Returns one published PreShiftIQ document by the id search returned: its title, its text and its URL.

Input parameters:

- `id` (string, required)

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

### `my_assessment_status` (~115 tokens)

My assessment status

For the signed-in client (the evaluating company): whether the latest completed PreShiftIQ assessment has results, whether those results are under review, how many matched vendors were notified, how many have accepted, and how many matches are still queued for delivery. When no assessment has been submitted but one has been started, the status is in_progress, with its completion percentage and the URL to resume it. An assessment that was submitted and has no matches to show yet is submitted_pending. Status only; the match list is my_matches.

Output parameters:

- `accepted_matches` (integer)
- `completion_pct` (integer)
- `notified_matches` (integer)
- `pending_delivery` (integer)
- `resume_url` (string)
- `status` (string)
- `summary` (string)
- `vertical` (string|null)

### `my_matches` (~121 tokens)

My matches

For the signed-in client (the evaluating company): the notified matches of the latest completed assessment, or of the assessment named by assessment_id, best score first, each as a masked card with its score and tier. On a review account the cards are its matches, and no vendor is contacted. A vendor's contact details appear only on a match that vendor has accepted, with the requirement and preference credits that vendor earned for you and the status of each certification you required; every other card stays masked. No card carries pricing.

Input parameters:

- `assessment_id` (string)

Output parameters:

- `matches` (array)
- `pending_delivery` (integer)
- `status` (string)
- `summary` (string)
- `vertical` (string|null)

### `my_scorecard_status` (~101 tokens)

My vendor scorecard status

For the signed-in vendor: the scorecard's status and completion, and its lead counts (pending, accepted, declined, expiring soon). With match_id, the contact details of the client (the evaluating company) for that lead, and the client's unit and company profile, present only once the lead is accepted. On a client account the summary says so; a client's matches are under my_assessment_status.

Input parameters:

- `match_id` (string)

Output parameters:

- `buyer_company` (object|null)
- `client` (object|null)
- `leads` (object|null)
- `scorecard` (object|null)
- `status` (string)
- `summary` (string)

### `my_clients` (~111 tokens)

My clients

For a signed-in consultant or private equity firm member: the assessments of the clients the firm represents (the companies evaluating technology) who have accepted the advisor disclosure, in any status, each with its status, its Tier 1 and Tier 2 completion percentages, the number of its matches awaiting release to vendors and, once matches exist, its notified match cards masked exactly as the client sees them. A represented client who has not accepted the disclosure is only counted, as withheld. Available once the consultant disclosure is open.

Output parameters:

- `represented` (array)
- `status` (string)
- `summary` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-preshiftiq-shiftiq-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 85
- 2026-10-28: 85
- 2026-10-27: 85
- 2026-10-26: 84
- 2026-10-25: 84
- 2026-10-24: 83
- 2026-10-23: 83
- 2026-10-22: 82
- 2026-10-21: 82
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 79
- 2026-10-13: 79
- 2026-10-12: 79
- 2026-10-10: 78
- 2026-10-09: 77
- 2026-10-04: 74
- 2026-10-03: 74
- 2026-10-02: 74

## Common questions

### What is the PreShiftIQ MCP server?

PreShiftIQ is an MCP server listed in the public MCP registry as com.preshiftiq/shiftiq-mcp. Independent buyer-side matching for supply chain technology selection. This page covers its hosted endpoint (https://mcp.preshiftiq.com/mcp).

### Is the PreShiftIQ MCP server safe to use?

PreShiftIQ scores 86 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 PreShiftIQ MCP server expose?

PreShiftIQ exposes 12 tools: describe_platform, list_verticals, get_public_catalog, explain_matching, how_we_are_paid, and 7 more. Their descriptions and schemas cost roughly 959 tokens of context every time the server is loaded.

### Does the PreShiftIQ MCP server require authentication?

Its publisher declares no required credentials for PreShiftIQ. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the PreShiftIQ MCP server still maintained?

PreShiftIQ is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 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 PreShiftIQ MCP server?

VerifyMCP ran 3 checks on PreShiftIQ, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about PreShiftIQ: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.preshiftiq.com/mcp
- Repository: https://github.com/PreShiftIQ/preshiftiq-mcp
- Website: https://preshiftiq.com/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-preshiftiq-shiftiq-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-preshiftiq-shiftiq-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-preshiftiq-shiftiq-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-preshiftiq-shiftiq-mcp/mcp