Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

offload

NPM · OFFLOAD-MCP-SERVER

Hand heavy read-only work to a background agent CLI (Antigravity) and read back a short report.

Available components

+2 this week 74 Trust /100

Last scanned (19 hours ago)

Scores higher than 49% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security97
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 4 of 9 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1393 tokens (~278/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • Dependency health: 0.88 → 0.79 ▼ functional
  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.4.1 → 0.4.2 functional
  • 9 Nov 26 +15
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.4.0 → 0.4.1 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/offload-mcp-server@0.4.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 9 packages
Packages resolved 9
Stale 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,393 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
offload_cancel_task ~47

Stop a queued or running offloaded job and its worker process tree. Finished jobs are left as they are.

NameTypeReqDescription
job_idstringyesJob ID from offload_submit_task.

No output schema declared.

No examples provided.

offload_followup ~158

Continue a finished job's worker conversation: ask about its report, or answer the question it ended with (an "ASK:" line). The worker keeps what it already read, so this is much cheaper than a new job. Returns a new job_id; collect it with offload_get_status. Works only with backends that can resume a conversation (agy).

NameTypeReqDescription
job_idstringyesThe finished job to continue.
messagestringyesYour question or answer, e.g. "Does api/v1/user/profile.php:26 reject an expired token? Quote the check."
output_hintstring–Shape of the Findings for this answer.
timeout_secinteger–Kill the worker after this many seconds.

No output schema declared.

No examples provided.

offload_get_result ~143

Read the worker's report for a finished job, in pages of up to 25000 characters. part="summary" (short answer), "findings" (evidence list), "steps" (Step log: done/partial/not done per step), "uncertain", "full" (whole report), "stderr" (backend error output, for debugging a failed job).

NameTypeReqDescription
job_idstringyesJob ID from offload_submit_task.
max_charsinteger–Maximum characters to return.
offsetinteger–Character offset, for paging through long parts.
partstring–Which part of the report to read.

No output schema declared.

No examples provided.

offload_get_status ~124

Get the status of one offloaded job, optionally waiting up to 50s for it to finish. When the job is done this already includes the worker's Summary, so you usually do not need offload_get_result. Without job_id, lists the most recent jobs.

NameTypeReqDescription
job_idstring–Job ID from offload_submit_task. Omit to list recent jobs.
limitinteger–How many recent jobs to list when job_id is omitted.
wait_secinteger–Seconds to wait for completion before answering (max 50).

No output schema declared.

No examples provided.

offload_submit_task ~921

Hand a heavy READ-ONLY task to a background worker agent (default: agy) and get a job_id back immediately. Use it when the work means reading a lot but the answer is small: scanning many files, filtering large logs, analyzing a big bundle or resource file, inventorying APIs/strings/config across a tree. The worker replies with a short Summary plus Findings with path:line evidence, so you read a few hundred words instead of the files. Do NOT use it for edits, for small lookups you can do in one or two reads, or for anything security-sensitive you must verify line by line yourself. The worker is another model: treat its findings as leads and spot-check the ones you act on. Write a complete BRIEF. The worker executes it literally and does nothing else, so anything you leave vague it will skip or guess: - task: the goal as one concrete question. - steps: ordered, concrete actions; each names what to open or search and what to record. - output_hint: the exact shape of the Findings (columns, grouping, sort order, what goes in each column). - done_when: the stop condition, so the worker neither stops early nor wanders. - context (optional): what you already know (conventions, file roles), so the worker does not rediscover it. - exclude (optional): files, folders or kinds of results to leave out. The worker returns a Step log; the status tells you which steps it did not finish and which in-scope files it never opened. Each job costs the worker a fixed preamble (about 20k tokens for agy) before it reads anything, so do small lookups yourself. A brief identical to a finished job, over unchanged files, returns that job instead of running again (reuse=false to force a new run). Next: call offload_get_status with the job_id and wait_sec=50 until it finishes. To ask the worker more about its report, use offload_followup: it keeps what the worker already read. Example: task="Which HTTP endpoints does api/v1 register, and what auth does each require?" steps=["List every .php…

NameTypeReqDescription
backendstring–Backend name from the config. Available: agy.
contextstring–Facts you already know that save the worker time: conventions, which file does what, names to look for.
done_whenstringyesStop condition, e.g. "every file under api/v1 is read and every route is listed".
excludearray–What to leave out: files, folders, or kinds of results, e.g. ["tests/", "commented-out code"].
modelstring–Exact worker model id; overrides tier.
output_hintstringyesExact shape of the Findings, e.g. "table: name | path:line | purpose, sorted by path".
pathsarray–Files or folders to focus on, relative to the workspace, e.g. ["api/core", "dist/app.js"]. Empty = whole workspace.
reuseboolean–Return a finished job with the same brief over unchanged files instead of running again.
stepsarrayyesOrdered actions for the worker, each concrete: what to open or search, what to record. The worker performs exactly these, in order, and logs each as done/partial/not done.
taskstringyesThe goal: one concrete question the report must answer, e.g. "Which endpoints in api/v1 skip the CSRF check?"
tierstring–Worker model tier, when the backend defines tiers: low for mechanical inventories, medium by default, high for hard reading or a retry after a weak result.
timeout_secinteger–Kill the worker after this many seconds. Defaults to the backend's timeoutSec.
workspacestring–Absolute workspace path. Defaults to the current project; other paths must be listed in allowedRoots.

No output schema declared.

No examples provided.

Install

How do I install the offload MCP server?

offload runs locally as an npm package, launched with npx -y offload-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · offload-mcp-server

# add to Claude Code
claude mcp add tailucanh-offload-mcp-server -- npx -y offload-mcp-server
Common questions

What is the offload MCP server?

offload is an MCP server listed in the public MCP registry as io.github.tailucanh/offload-mcp-server. Hand heavy read-only work to a background agent CLI (Antigravity) and read back a short report. This page covers its npm package (offload-mcp-server).

Is the offload MCP server safe to use?

offload scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the offload MCP server expose?

offload exposes 5 tools: offload_submit_task, offload_followup, offload_get_status, offload_get_result, offload_cancel_task. Their descriptions and schemas cost roughly 1,393 tokens of context every time the server is loaded.

Is the offload MCP server still maintained?

offload is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the offload MCP server under?

offload declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the offload MCP server?

VerifyMCP ran 16 checks on offload, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.