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.

Machship MCP

NPM · @DEVKIND/MACHSHIP-MCP

Model Context Protocol server for the Machship freight management platform

71 Trust /100

Last scanned (2 hours ago)

Scores higher than 40% of npm servers

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 33 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (ISC).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 11898 tokens (~95/item across 125 items; 125 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 126 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 +2
    • Security disclosure: unverified → pass ▲ functional
  • 3 Nov 26 +20
    • Malware scan: unverified → pass ▲ security
    • Source repository: fail → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 1.3.0 → 1.4.0 functional
  • 2 Nov 26 49

    First indexed and scored.

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 · Analysed npm/@devkind/machship-mcp@1.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 105 packages
Packages resolved 105
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 125 exposed · ~11,729 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
machship_group_and_perform_consolidation ~65

Groups and consolidates consignments in a single operation (combines grouping + performing). Args: - options (object): Consolidation options (companyId, carrierId, grouping rules, etc.)

NameTypeReqDescription
optionsobjectyesConsolidation options
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_group_consignments_for_consolidation ~77

Automatically groups consignments into consolidation groups based on options (carrier, route, etc.). Returns groups without actually consolidating — preview step before consolidation. Args: - options (object): Consolidation grouping options (companyId, carrierId, etc.)

NameTypeReqDescription
optionsobjectyesConsolidation grouping options
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_group_consignments_for_manifest ~60

Groups a specific set of consignments into manifest groups (preview before manifesting). Args: - consignmentIds (number[]): Consignment IDs to group

NameTypeReqDescription
consignmentIdsarrayyesConsignment IDs to group
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_group_consignments_for_printing ~57

Groups consignments for batch label printing and returns print groups. Args: - consignmentIds (number[]): Consignment IDs to group for printing

NameTypeReqDescription
consignmentIdsarrayyesConsignment IDs
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_link_identities_to_companies ~70

Assign companies and roles to identities to give them access to the system. Requires administrator access. Args: - links (array): Array of identity-company link objects, each with identityId, companyId, and roles

NameTypeReqDescription
linksarrayyesIdentity-company links to create
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_manifest_consignments ~90

Books/manifests consignments with the carrier — creates the pickup booking and generates tracking numbers. This is the final step in the consignment workflow before physical pickup. Args: - manifests (array): Array of booked manifest objects with consignment IDs and carrier booking details

NameTypeReqDescription
manifestsarrayyesManifest booking objects (consignmentIds, carrierId, despatchDate, etc.)
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_perform_consolidation ~67

Consolidates a set of consignments into consolidated shipments. This merges multiple consignments into fewer shipment units for carrier efficiency. Args: - request (object): Consolidation request with consignment IDs and consolidation parameters

NameTypeReqDescription
requestobjectyesConsolidation request payload
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_ping ~53

Determines the current user's login status and retrieves session properties from Machship. Use this to verify authentication is working and to get the current user/company context. Returns: session info including user details, company ID, and permissions.

Input schema present but exposes no named parameters.

NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_rebook_manifest_pickup ~71

Rebooks the carrier pickup for an existing manifest (e.g. missed pickup or changed schedule). Args: - rebooking (object): Rebooking details including manifestId and new pickup datetime

NameTypeReqDescription
rebookingobjectyesRebooking details (manifestId, pickupDate, etc.)
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_reenable_identities ~50

Re-enable previously disabled identities, restoring login access. Args: - ids (number[]): Array of identity IDs to re-enable

NameTypeReqDescription
idsarrayyesIdentity IDs to re-enable
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_remove_organisation_link ~57

Removes an existing link between two organisations. This action is irreversible. Args: - request (object): Unlink request with organisationLinkId to remove

NameTypeReqDescription
requestobjectyesUnlink request (organisationLinkId)
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_reset_organisation_public_key ~62

Resets the public key for an organisation (generates new key). Does NOT affect existing links. Args: - id (number, optional): Organisation ID (defaults to current org)

NameTypeReqDescription
idinteger–Organisation ID (optional)
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_return_identity_public_keys ~73

Get the public keys of the supplied identities. These keys can be used by a linked organisation to grant those identities access to companies in their organisation. Requires administrator access. Args: - ids (number[]): Array of identity IDs to retrieve public keys for

NameTypeReqDescription
idsarrayyesIdentity IDs
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_return_item_pdfs_for_consignments ~130

Returns item labels as a zip for up to 40 consignments (POST variant — use this when passing a body payload is preferred over query string). Returns { fileBase64, contentType, sizeBytes }. contentType comes from the response header. Args: - consignmentIds (number[]): Consignment IDs (max 40) - printA4 (boolean, optional): Print in A4 format

NameTypeReqDescription
consignmentIdsarrayyesConsignment IDs (max 40)
printA4boolean–Print in A4 format
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_search_consignments ~58

Searches consignments by reference numbers (Reference 1, Reference 2, or carrier IDs). Args: - references (string[]): Array of reference strings to search for

NameTypeReqDescription
referencesarrayyesReference values to search
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_search_locations ~220

Returns up to 10 Machship locations matching a suburb or postcode search string. Use this to look up valid delivery/pickup locationIds before creating consignments. Args: - s (string): Search string — suburb name, postcode, or both (e.g. "Melbourne 3000") - response_format ('json' | 'markdown'): Output format (default: 'json') Returns: Array of location objects: { "id": number, "suburb": string, "postcode": string, "state": string, "country": string } Examples: - Use when: "What location ID is for Sydney 2000?" -> search "Sydney 2000", pick from results - Use when: Validating a delivery address before creating a consignment

NameTypeReqDescription
response_formatstring–Output format: 'json' (default) or 'markdown'
sstringyesSearch string: suburb name, postcode, or both (e.g. 'Melbourne 3000')
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_send_labels_to_printer ~70

Sends labels directly to a configured printer in Machship. Args: - requests (array): Array of print requests, each with consignmentId, printerId, labelType, etc.

NameTypeReqDescription
requestsarrayyesPrint requests (consignmentId, printerId, labelType)
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_unlink_identities_from_companies ~68

Remove company access from identities. Each entry specifies an identity and the company to revoke access from. Args: - unlinks (array): Array of objects with identityId and companyId to unlink

NameTypeReqDescription
unlinksarrayyesIdentity-company pairs to unlink
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_update_consignment_statuses ~65

Manually updates tracking statuses for consignments (e.g. mark as delivered). Args: - statuses (array): Array of manual tracking status objects, each with consignmentId, status, and datetime

NameTypeReqDescription
statusesarrayyesTracking status updates
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_update_custom_schema ~74

Updates an existing custom schema by its DotNet class ID. Args: - id (string): DotNet class ID of the schema to update - schema (object): Updated JSON schema definition

NameTypeReqDescription
idstringyesDotNet class ID
schemaobjectyesUpdated JSON schema definition
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_update_despatch_dates ~75

Updates despatch dates and estimated time of arrival (ETA) for a set of consignments. Args: - updates (array): Array of objects with consignmentId and new despatch date/ETA

NameTypeReqDescription
updatesarrayyesDespatch date updates (consignmentId, despatchDate, eta)
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_update_identity ~257

Updates properties on an identity. All fields except password are required; omitted fields are set to null. Args: - id (number): Identity ID (required) - givenName (string): First name (required) - familyName (string): Last name (required) - displayName (string): Display name (required) - emailAddress (string): Email address (required) - owningCompanyId (number): Owning company ID (required) - password (string, optional): New password - phone / businessPhone / mobile / position / notes (optional)

NameTypeReqDescription
businessPhonestring–Business phone number
displayNamestringyesDisplay name
emailAddressstringyesEmail address
familyNamestringyesLast name
givenNamestringyesFirst name
idintegeryesIdentity ID
mobilestring–Mobile number
notesstring–Additional notes about the identity
owningCompanyIdintegeryesOwning company ID
passwordstring–New password (optional)
phonestring–Phone number
positionstring–Job position or title
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_update_reprice_consignment ~68

Updates consignment items on a carrier invoice entry and triggers repricing. Use for reconciling carrier invoice discrepancies. Args: - body (object): Repricing request payload (consignmentId, items, etc.)

NameTypeReqDescription
bodyobjectyesRepricing request payload
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_upload_attachments ~105

Uploads one or more attachments to Machship. Args: - attachments (array): Array of attachment objects. Each object should contain: - consignmentId (number): Consignment to attach to - fileName (string): File name with extension - fileBase64 (string): Base64-encoded file content - attachmentTypeId (number, optional): Type of attachment

NameTypeReqDescription
attachmentsarrayyesAttachments to upload
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

machship_upload_commercial_invoice ~101

Uploads one or more commercial invoice files for a consignment (for international shipments). Files are provided as base64-encoded content. Args: - consignmentId (number): The consignment to attach the invoice to - files (array): Array of files, each with fileName and fileBase64 content

NameTypeReqDescription
consignmentIdintegeryesConsignment ID
filesarrayyesInvoice files to upload
NameTypeReqDescription
errors––Validation errors returned by Machship, if any
object––Response payload from the Machship API

No examples provided.

Install

How do I install the Machship MCP server?

Machship MCP runs locally as an npm package, launched with npx -y @devkind/machship-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @devkind/machship-mcp

# add to Claude Code
claude mcp add devkindhq-machship-mcp -- npx -y @devkind/machship-mcp
Common questions

What is the Machship MCP server?

Machship MCP is listed in the public MCP registry as io.github.devkindhq/machship-mcp. Model Context Protocol server for the Machship freight management platform. This page covers its npm package (@devkind/machship-mcp).

Is the Machship MCP server safe to use?

Machship MCP scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Machship MCP server expose?

Machship MCP exposes 125 tools: machship_ping, machship_get_attachment, machship_get_attachment_pod_report, machship_get_attachments_by_consignment_ids, machship_upload_attachments, and 120 more. Their descriptions and schemas cost roughly 11,729 tokens of context every time the server is loaded.

Is the Machship MCP server still maintained?

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

What licence is the Machship MCP server under?

Machship MCP declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.