Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PreShiftIQ

REMOTE · MCP.PRESHIFTIQ.COM

Independent buyer-side matching for supply chain technology selection.

+1 this week 86 Trust /100

Last scanned (8 hours ago)

Scores higher than 93% of remote servers

Unreachable for 2 days in a row. Last reached 3 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

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.

Changelog

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.

  • 4 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Oct 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.

  • 27 Oct 26 +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.

  • 25 Oct 26 +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.

  • 23 Oct 26 +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.

  • 21 Oct 26 +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.

  • 19 Oct 26 +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.

Diagnostics

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 5 Nov 2026 · Probed https://mcp.preshiftiq.com/mcp

TLS unreached
DNSSEC insecure

Validation of mcp.preshiftiq.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
preshiftiq.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.preshiftiq.com/mcp Unreachable
http (plaintext) http://mcp.preshiftiq.com/mcp HTTPS enforced
MCP tools · 12 exposed · ~959 tokens

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 →

Tool Tokens
describe_platform ~87

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
canonical_urlstringyes–
connect_urlstringyes–
how_matching_works_summarystringyes–
how_paid_summarystringyes–
namestringyes–
one_linestringyes–
start_urlstringyes–
verticalsarrayyes–
what_it_isstringyes–
what_it_is_notstringyes–
who_it_servesstringyes–

No examples provided.

explain_matching ~70

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.

NameTypeReqDescription
vertical_idstring––
NameTypeReqDescription
additive_index_notestringyes–
boundary_statementstringyes–
disqualification_firststringyes–
how_it_works_urlstringyes–
immutable_record_notestringyes–
summarystringyes–
tiersobjectyes–

No examples provided.

fetch ~36

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

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
idstringyes–
metadataobjectyes–
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_public_catalog ~89

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.

NameTypeReqDescription
vertical_idstringyes–
NameTypeReqDescription
buyer_page_urlstringyes–
coverage_statementstringyes–
delisting_policystringyes–
display_namestringyes–
start_urlstringyes–
vendorsarrayyes–
vertical_idstringyes–

No examples provided.

how_we_are_paid ~32

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
boundary_statementstringyes–
buyer_coststringyes–
page_urlstringyes–
vendor_model_summarystringyes–

No examples provided.

list_verticals ~63

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
verticalsarrayyes–

No examples provided.

my_assessment_status ~115

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
accepted_matchesintegeryes–
completion_pctinteger––
notified_matchesintegeryes–
pending_deliveryintegeryes–
resume_urlstring––
statusstringyes–
summarystringyes–
verticalstring|nullyes–

No examples provided.

my_clients ~111

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
representedarrayyes–
statusstringyes–
summarystringyes–

No examples provided.

my_matches ~121

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.

NameTypeReqDescription
assessment_idstring––
NameTypeReqDescription
matchesarrayyes–
pending_deliveryintegeryes–
statusstringyes–
summarystringyes–
verticalstring|nullyes–

No examples provided.

my_scorecard_status ~101

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.

NameTypeReqDescription
match_idstring––
NameTypeReqDescription
buyer_companyobject|nullyes–
clientobject|nullyes–
leadsobject|nullyes–
scorecardobject|nullyes–
statusstringyes–
summarystringyes–

No examples provided.

search ~59

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.

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

start_assessment ~75

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.

NameTypeReqDescription
handlestring––
vertical_idstring––
NameTypeReqDescription
choose_verticalarray––
display_namestring––
start_urlstring––
urlstring––
vertical_idstring––

No examples provided.

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.

remote · mcp.preshiftiq.com

# add to Claude Code
claude mcp add --transport http com-preshiftiq-shiftiq-mcp 'https://mcp.preshiftiq.com/mcp'
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.