liftlog MCP server
us.artificl/liftlogartificl.usstreamable-httpv1.0.0Scanned
Forklift & aerial-lift compliance records for warehouses — read-only demo tools.
5 tools: 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the liftlog MCP server can do
The liftlog MCP server is published by artificl.us, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 7, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Only reads 5Show 5 read-only tools
export_lift_logExport the full lift compliance log as CSV text (operator or machine, requirement, next due, status, chase history).No findings
Why it is in this group
- The name "export_lift_log" says "log": a word for reading.
Description, as the server wrote it Export the full lift compliance log as CSV text (operator or machine, requirement, next due, status, chase history).
get_lift_summaryGet the lift compliance summary: totals for tracked requirements, not done, overdue and citable, due this week, and awaiting records.No findings
Why it is in this group
- The name "get_lift_summary" says "get": a word for reading.
Description, as the server wrote it Get the lift compliance summary: totals for tracked requirements, not done, overdue and citable, due this week, and awaiting records.
get_requirements_dueList operator evaluations, inspections, and maintenance intervals due within the next N days (default 30).No findings
Why it is in this group
- The name "get_requirements_due" says "get": a word for reading.
Description, as the server wrote it List operator evaluations, inspections, and maintenance intervals due within the next N days (default 30).
list_citable_itemsList overdue or missing compliance items — the ones that would be citable in an OSHA inspection or damaging in an injury investigation.No findings
Why it is in this group
- The name "list_citable_items" says "list": a word for reading.
Description, as the server wrote it 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.
search_requirementsSearch lift compliance requirements by operator name, machine, or requirement type.No findings
Why it is in this group
- The name "search_requirements" says "search": a word for reading.
Description, as the server wrote it Search lift compliance requirements by operator name, machine, or requirement type. Returns matching records with next due date and status.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:24 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://liftlog.artificl.us/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata
- https://liftlog.artificl.us/.well-known/oauth-protected-resource
- Authorization servers
- https://liftlog.artificl.us
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Posture changes
- Nov 20, 2026
- Authorization servers: none to https://liftlog.artificl.us
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://liftlog.artificl.us/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: none to https://liftlog.artificl.us/.well-known/oauth-protected-resource
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Authorization servers: none -> https://liftlog.artificl.us; Dynamic client registration: not observed -> yes; Client ID metadata documents: not observed -> no.View diff
- Authorization servers: none to https://liftlog.artificl.us
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none (and 3 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://liftlog.artificl.us/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: none to https://liftlog.artificl.us/.well-known/oauth-protected-resource
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http liftlog https://liftlog.artificl.us/mcpclaude mcp add --transport http liftlog https://liftlog.artificl.us/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__liftlog__search_requirements",
"mcp__liftlog__list_citable_items",
"mcp__liftlog__get_requirements_due",
"mcp__liftlog__get_lift_summary",
"mcp__liftlog__export_lift_log"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as liftlog. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/us.artificl/liftlog/verify?hash=89c026f635e906bb1b02837a7e6014fecfa3cb9a686366a04a728c62480bbc08" | jq -e '.changed == false'Pinned hash 89c026f635e9, from Nov 7, 2026, 05:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/us.artificl/liftlog/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/us.artificl/liftlog)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
liftlog MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the liftlog MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the liftlog MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the liftlog MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the liftlog MCP server have?
- 5 tools: 5 read. search_requirements, list_citable_items, get_requirements_due, get_lift_summary and export_lift_log.
Does the liftlog MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the liftlog MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the liftlog MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 7, 2026.