Autotask MCP Server (ThatDayneGuy/autotask-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Emerging
74/100
20 days ago

Autotask MCP Server

Enables AI assistants to directly interact with Autotask PSA for ticket triage, time logging, company lookups, project management, and more via natural language.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ThatDayneGuy

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: AUTOTASK_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: AUTOTASK_SECRET, X_API_KEY, X_API_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAUTH_MODEe =gateway \
configAUTOTASK_API_URLis auto-detected from AUTOTASK_USERNAME via Autotask's
configAUTOTASK_ENHANCE_CONCURRENCY❌ 3 Max concurrent Autotask API calls used to resolve company/resource names on search results. Kept low to stay under Autotask's concurrent-thread limit.
configAUTOTASK_INTEGRATION_CODEe =your-code \
🔐 secretAUTOTASK_SECRETe =your-secret \
configAUTOTASK_USERNAMEe =your-user@company.com \
configLAZY_LOADING
configLOG_FORMATsimple # simple, json
configLOG_LEVELinfo # error, warn, info, debug
configMCP_HTTP_HOST0.0.0.0 # HTTP transport bind address
configMCP_HTTP_PORT8080 # HTTP transport port (only used when MCP_TRANSPORT=http)
configMCP_SERVER_NAMEautotask-mcp
configMCP_SERVER_VERSION
configMCP_TRANSPORT"-e", "=stdio",
🔐 secretX_API_KEY
🔐 secretX_API_SECRET
configX_API_URL
configX_INTEGRATION_CODE
// quality suggestions

Tool annotations

6/98 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

92/98 tools missing one or more hints — autotask_test_connection (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); autotask_search_companies (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); autotask_create_company (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +89 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 15/98 tools referenced in tests (15%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

28 secret values sent to console.log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/thatdayneguy-autotask-mcp-1yf7s9)](https://m8ven.ai/mcp/thatdayneguy-autotask-mcp-1yf7s9)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2b2f177c472630cc5cf23e4657de0b082466cbdc
code hash: 5805f116e2ce606e36d4607076349a7d5a5dd413a6327e5c242c8a4e923901ef
verified: 8/7/2026, 4:17:24 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client