LiftLog MCP

LiftLog is a compliance tracking tool for forklift and aerial lift records, including OSHA operator evaluations, annual equipment inspections, ANSI A92 cycles, and maintenance intervals. The MCP endpoint allows AI assistants to query live, read-only records to answer questions about operator status, inspection due dates, and missing documentation for safety investigations.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Artificl

MCP endpoint (Streamable HTTP)

https://liftlog.artificl.us/mcp

Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (5)

search_requirements
list_citable_items
get_requirements_due
get_lift_summary
export_lift_log

5 of 5 have a description · 0 of 5 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 7, 2026, 10:56 AM UTC
Passed Official MCP Registry namespace is tied to artificl.us · Nov 7, 2026, 6:23 AM UTC
Passed Endpoint is on the registry namespace domain · Nov 7, 2026, 6:23 AM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Check if specific equipment like a Genie S-45 is cleared for use today
Identify potential OSHA violations or overdue inspections
Determine which operator evaluations and inspections are due this week
Retrieve missing records for lift incident investigations

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: us.artificl/liftlog@1.0.0 Project website

Protocol and capabilities

Server: liftlog 0.1.0
MCP protocol negotiated in check: 2025-11-25
Tools: 5 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": true
  }
}

Tools

5 advertised

search_requirements

Advertised by the server during the last successful anonymous check.

Search lift compliance requirements by operator name, machine, or requirement type. Returns matching records with next due date and status.

search_requirements input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "query": {
      "type": "string",
      "description": "Text to match against operator, machine, or requirement (case-insensitive; shorthand like \"PM\" or \"aerial lift\" works). Omit to list everything."
    }
  }
}

list_citable_items

Advertised by the server during the last successful anonymous check.

List overdue or missing compliance items — the ones that would be citable in an OSHA inspection or damaging in an injury investigation. Most serious first.

list_citable_items input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

get_requirements_due

Advertised by the server during the last successful anonymous check.

List operator evaluations, inspections, and maintenance intervals due within the next N days (default 30).

get_requirements_due input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "days": {
      "type": "number",
      "description": "Look-ahead window in days (default 30)."
    }
  }
}

get_lift_summary

Advertised by the server during the last successful anonymous check.

Get the lift compliance summary: totals for tracked requirements, not done, overdue and citable, due this week, and awaiting records.

get_lift_summary input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

export_lift_log

Advertised by the server during the last successful anonymous check.

Export the full lift compliance log as CSV text (operator or machine, requirement, next due, status, chase history).

export_lift_log input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 338 ms
95th percentile latency: 338 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 7, 2026, 10:56 AM UTC · probe · passed · 338 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http liftlog-mcp https://liftlog.artificl.us/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add liftlog-mcp --url https://liftlog.artificl.us/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable liftlog-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "liftlog-mcp": {
      "url": "https://liftlog.artificl.us/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "liftlog-mcp": {
      "type": "streamableHttp",
      "url": "https://liftlog.artificl.us/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start liftlog-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "liftlog-mcp": {
      "type": "http",
      "url": "https://liftlog.artificl.us/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http liftlog-mcp https://liftlog.artificl.us/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://liftlog.artificl.us/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "liftlog-mcp": {
      "serverUrl": "https://liftlog.artificl.us/mcp"
    }
  }
}

Let your agent find its tools

Find servers like LiftLog MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run LiftLog MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing