# PreShiftIQ

> Independent buyer-side matching for supply chain technology selection.

- name: com.preshiftiq/shiftiq-mcp
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 84/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.preshiftiq%2Fshiftiq-mcp
- tools: https://api.protogrid.dev/v1/servers/com.preshiftiq%2Fshiftiq-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-19d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 84/100 (good)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 60000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 12 of 12 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,833 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 54 tool changes in 30 days
- fail `stability.rug_pull`: 3 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 12, about 1,833 tokens to load them all
- tool set hash: 2ada9ab943e797c6be13082bdf58c732
- tools last changed: 2026-10-18T02:58:39.965Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.preshiftiq/shiftiq-mcp.svg)](https://protogrid.dev/servers/com.preshiftiq/shiftiq-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-18 `my_clients` changed (outputSchema)
- 2026-10-18 `my_scorecard_status` changed (outputSchema)
- 2026-10-18 `my_matches` changed (outputSchema)
- 2026-10-18 `my_assessment_status` changed (outputSchema)
- 2026-10-18 `start_assessment` changed (inputSchema, outputSchema)
- 2026-10-18 `explain_matching` changed (inputSchema)
- 2026-10-18 `get_public_catalog` changed (inputSchema, outputSchema)
- 2026-10-18 `list_verticals` changed (outputSchema)
- 2026-10-18 `describe_platform` changed (description)
  - before: 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, and fleet management.
  - after: 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.
- 2026-10-17 `my_clients` changed (description, outputSchema)
  - before: For a signed-in consultant or private equity firm member: the assessments of the buyers the firm represents 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 buyer sees them. A represented buyer who has not accepted the disclosure is only counted, as withheld. Available once the consultant disclosure is open.
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/com.preshiftiq%2Fshiftiq-mcp/changes

## Remotes

- https://mcp.preshiftiq.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (12)

- `describe_platform`: 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.
- `explain_matching`: 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.
- `fetch`: Returns one published PreShiftIQ document by the id search returned: its title, its text and its URL.
- `get_public_catalog`: 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.
- `how_we_are_paid`: States how PreShiftIQ is paid. Use this when a user asks about cost, fees, or independence.
- `list_verticals`: 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.
- `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.
- `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.
- `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.
- `my_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.
- `search`: 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.
- `start_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.