Skip to content

driverfile MCP server

us.artificl/driverfileartificl.usstreamable-httpv1.0.0Scanned

DOT driver qualification file tracking for small motor carriers — read-only demo tools.

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 4
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 driverfile MCP server can do

The driverfile MCP server is published by artificl.us, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: export_dq_report), but cannot delete data. 4 tools only read.

4 tools read private data (search_dq_items, list_audit_risks, get_items_due and 1 more); 2 tools bring in text other people can write (list_audit_risks and get_items_due).

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

Changes things 1Claude Code: ask
  • export_dq_reportExport the full driver qualification file report as CSV text (driver, item, due date, status, chase history).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Export the full driver qualification file report as CSV text (driver, item, due date, status, chase history).
Only reads 4Show 4 read-only tools
  • get_dq_summaryGet the driver qualification file summary: totals for tracked items, missing from file, out of date, due in 14 days, and awaiting filing.Reads private dataNo findings

    Why it is in this group

    • The name "get_dq_summary" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "file": it reads files.
    Description, as the server wrote it
    Get the driver qualification file summary: totals for tracked items, missing from file, out of date, due in 14 days, and awaiting filing.
  • get_items_dueList DQ file items coming due within the next N days (default 30), including medical cards, MVR reviews, and Clearinghouse queries.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_items_due" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    • untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    List DQ file items coming due within the next N days (default 30), including medical cards, MVR reviews, and Clearinghouse queries.
  • list_audit_risksList driver qualification file items that are missing or out of date — the items that would be findings in a DOT compliance review today.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_audit_risks" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    • untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    List driver qualification file items that are missing or out of date — the items that would be findings in a DOT compliance review today. Most serious first.
  • search_dq_itemsSearch driver qualification file items by driver name or item type.Reads private dataNo findings

    Why it is in this group

    • The name "search_dq_items" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "file": it reads files.
    Description, as the server wrote it
    Search driver qualification file items by driver name or item type. Returns matching records with due date and status (in file, to file, missing, out of date).

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 outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 19:23 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://driverfile.artificl.us/.well-known/oauth-protected-resource
RFC 9728 protected resource metadata
https://driverfile.artificl.us/.well-known/oauth-protected-resource
Authorization servers
https://driverfile.artificl.us
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 20, 2026
    • Authorization servers: none to https://driverfile.artificl.us
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://driverfile.artificl.us/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://driverfile.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.

  1. PostureRemote posture changed. Authorization servers: none -> https://driverfile.artificl.us; Dynamic client registration: not observed -> yes; Client ID metadata documents: not observed -> no.View diff
    • Authorization servers: none to https://driverfile.artificl.us
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 4 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://driverfile.artificl.us/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://driverfile.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 driverfile https://driverfile.artificl.us/mcp
claude mcp add --transport http driverfile https://driverfile.artificl.us/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__driverfile__search_dq_items",
      "mcp__driverfile__list_audit_risks",
      "mcp__driverfile__get_items_due",
      "mcp__driverfile__get_dq_summary"
    ],
    "ask": [
      "mcp__driverfile__export_dq_report"
    ],
    "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 driverfile. Review it before you use it.

Capability tags behind 4 rules
  • mcp__driverfile__search_dq_items private-data
  • mcp__driverfile__list_audit_risks private-data, untrusted-input
  • mcp__driverfile__get_items_due private-data, untrusted-input
  • mcp__driverfile__get_dq_summary private-data

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/driverfile/verify?hash=7805f11a70ff88d6211a1d00e663d0e13eb41aca2d3904426be94ba6a9e74d18" | jq -e '.changed == false'

Pinned hash 7805f11a70ff, from Nov 7, 2026, 03: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/driverfile/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for us.artificl/driverfile
[![Anlyon Radar](https://radar.anlyon.com/badge/us.artificl/driverfile.svg)](https://radar.anlyon.com/servers/us.artificl/driverfile)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

driverfile MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the driverfile MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the driverfile MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the driverfile 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 driverfile MCP server have?

5 tools: 1 write, 4 read. export_dq_report, search_dq_items, list_audit_risks, get_items_due and get_dq_summary.

Does the driverfile 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 driverfile MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the driverfile MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 7, 2026.