Driverfile is an MCP server with 5 tools an agent can call, among them export_dq_report, get_dq_summary, get_items_due. It answers at https://driverfile.artificl.us/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
DOT driver qualification file tracking for small motor carriers — read-only demo tools.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
export_dq_report | Export the full driver qualification file report as CSV text (driver, item, due date, status, chase history). |
get_dq_summary | 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_due | List DQ file items coming due within the next N days (default 30), including medical cards, MVR reviews, and Clearinghouse queries. Inputs: days |
list_audit_risks | 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_items | 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). Inputs: query |
Every block below points at https://driverfile.artificl.us/mcp. Pick your client and copy.
claude mcp add --transport http driverfile https://driverfile.artificl.us/mcp
{
"mcpServers": {
"driverfile": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://driverfile.artificl.us/mcp"]
}
}
}{
"mcpServers": {
"driverfile": {
"url": "https://driverfile.artificl.us/mcp"
}
}
}{
"servers": {
"driverfile": {
"type": "http",
"url": "https://driverfile.artificl.us/mcp"
}
}
}{
"context_servers": {
"driverfile": {
"url": "https://driverfile.artificl.us/mcp"
}
}
}{
"mcpServers": {
"driverfile": {
"serverUrl": "https://driverfile.artificl.us/mcp"
}
}
}{
"mcpServers": {
"driverfile": {
"url": "https://driverfile.artificl.us/mcp"
}
}
}name: Driverfile
version: 0.0.1
schema: v1
mcpServers:
- name: Driverfile
type: streamable-http
url: https://driverfile.artificl.us/mcp{
"mcpServers": {
"driverfile": {
"httpUrl": "https://driverfile.artificl.us/mcp"
}
}
}{
"mcpServers": {
"driverfile": {
"type": "http",
"url": "https://driverfile.artificl.us/mcp"
}
}
}{
"mcpServers": {
"driverfile": {
"url": "https://driverfile.artificl.us/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fdriverfile.artificl.us%2Fmcp&type=streamable_http&id=driverfile&name=Driverfile
It answered our last check on 24 October 2026 in 213 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by artificl.us and served from driverfile.artificl.us, the vendor's own domain: https://driverfile.artificl.us/mcp.
5, as returned by the server's own tools/list on 23 September 2026: export_dq_report, get_dq_summary, get_items_due, list_audit_risks, search_dq_items.
It answered our last check on 24 October 2026 in 213 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://driverfile.artificl.us/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: us.artificl. Endpoint host: driverfile.artificl.us. ARD identifier: urn:air:us.artificl:mcp:driverfile.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.