com.preshiftiq/shiftiq-mcp

Est-ce que com.preshiftiq/shiftiq-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.preshiftiq/shiftiq-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 12 outils

• describe_platform≈ 355 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "describe_platform", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "one_line": "texte", "start_url": "texte", "verticals": [], "what_it_is": "texte", "connect_url": "texte", "canonical_url": "texte", "who_it_serves": "texte", "what_it_is_not": "texte", "how_paid_summary": "texte", "how_matching_works_summary": "texte"}}

• explain_matching≈ 358 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • vertical_id · string · optionnel · tms | dock-scheduling | eld | carrier-vetting | fleet-management | supply-chain-procurement | yard-management

  Exemple d'appel

  {"name": "explain_matching", "arguments": {"vertical_id": "tms"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tiers": {}, "summary": "texte", "how_it_works_url": "texte", "boundary_statement": "texte", "additive_index_note": "texte", "immutable_record_note": "texte", "disqualification_first": "texte"}}

• fetch≈ 229 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis

  Exemple d'appel

  {"name": "fetch", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "text": "texte", "title": "texte", "metadata": {}}}

• get_public_catalog≈ 434 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • vertical_id · string · requis · tms | dock-scheduling | eld | carrier-vetting | fleet-management | supply-chain-procurement | yard-management

  Exemple d'appel

  {"name": "get_public_catalog", "arguments": {"vertical_id": "tms"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"vendors": [], "start_url": "texte", "vertical_id": "tms", "display_name": "texte", "buyer_page_url": "texte", "delisting_policy": "texte", "coverage_statement": "texte"}}

• how_we_are_paid≈ 181 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "how_we_are_paid", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page_url": "texte", "buyer_cost": "texte", "boundary_statement": "texte", "vendor_model_summary": "texte"}}

• list_verticals≈ 297 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_verticals", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"verticals": []}}

• my_assessment_status≈ 396 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "my_assessment_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "no_results", "summary": "texte", "vertical": "tms", "resume_url": "texte", "completion_pct": 1, "accepted_matches": 1, "notified_matches": 1, "pending_delivery": 1}}

• my_clients≈ 814 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "my_clients", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "represented", "summary": "texte", "represented": []}}

• my_matches≈ 643 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • assessment_id · string · optionnel

  Exemple d'appel

  {"name": "my_matches", "arguments": {"assessment_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "no_results", "matches": [], "summary": "texte", "vertical": "tms", "pending_delivery": 1}}

• my_scorecard_status≈ 659 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • match_id · string · optionnel

  Exemple d'appel

  {"name": "my_scorecard_status", "arguments": {"match_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"leads": {}, "client": {}, "status": "scorecard", "summary": "texte", "scorecard": {}, "buyer_company": {}}}

• search≈ 247 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis

  Exemple d'appel

  {"name": "search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": []}}

• start_assessment≈ 428 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • handle · string · optionnel
  • vertical_id · string · optionnel · tms | dock-scheduling | eld | carrier-vetting | fleet-management | supply-chain-procurement | yard-management

  Exemple d'appel

  {"name": "start_assessment", "arguments": {"handle": "texte", "vertical_id": "tms"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "start_url": "texte", "vertical_id": "tms", "display_name": "texte", "choose_vertical": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.preshiftiq.com/mcp