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.

io.github.thuupx/lunge

NPM · LUNGE-MCP · SCANNED SEP 20

Agent-native API client: execute/test REST/GraphQL/WS/SSE with assertions, extraction, collections

Available components

0 this week 81 Trust /100
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 Security98
  • 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
  • 31 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2743 tokens (~124/item across 22 items; 22 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 Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ws_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.thuupx/lunge MCP server?

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

npm · lunge-mcp

# add to Claude Code
claude mcp add thuupx-lunge -- npx -y lunge-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "thuupx-lunge": {
      "command": "npx",
      "args": [
        "-y",
        "lunge-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "thuupx-lunge": {
      "command": "npx",
      "args": [
        "-y",
        "lunge-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add thuupx-lunge -- npx -y lunge-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thuupx-lunge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "lunge-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add thuupx-lunge --command npx --arg -y --arg lunge-mcp
# ~/.hermes/config.yaml
mcp_servers:
  thuupx-lunge:
    command: "npx"
    args: ["-y", "lunge-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "thuupx-lunge": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lunge-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add thuupx-lunge -t stdio -c npx -a -y lunge-mcp
// mcp.json
{
  "mcpServers": {
    "thuupx-lunge": {
      "command": "npx",
      "args": [
        "-y",
        "lunge-mcp"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.80 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 20 Sept 2026 · Analysed npm/lunge-mcp@1.3.1

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 105 packages
Packages resolved 105
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~2,743 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
collection_format ~84

Return the Lunge collection format reference: top-level fields, step schema, request specs per protocol (http/graphql/ws/sse), full assertion vocabulary (status/header/jsonpath/timeMs/schema/not + matchers), WS/SSE-specific assertions, variable chaining (extract + {{var}}), and JSONPath syntax. Call this BEFORE writing explicit steps for save_collection or reviewing saved output.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

graphql_introspect ~73

Introspect GraphQL endpoint, return summarized schema with field signatures (args + return types) and input types.

NameTypeReqDescription
authobject
envstring
headersobject
timeoutMsinteger
urlstringyesGraphQL endpoint URL.

No output schema declared.

No examples provided.

graphql_request ~213

GraphQL query/mutation over HTTP. Supports {{var}} extraction. Note: `ok` reflects HTTP status only (200 = ok). GraphQL-level errors are returned in `graphqlErrors` — always check both. Use extract with $.data.* for success data and $.errors.* for error details.

NameTypeReqDescription
assertarraye.g. [{status:200},{jsonpath:'$.x',equals:1},{timeMs:{lt:500}}].
authobject
envstring
extractobjectCapture vars: { token: '$.data.login.accessToken' }.
headersobject
querystringyesGraphQL query/mutation document.
timeoutMsinteger
urlstringyesGraphQL endpoint URL.
variablesobject
verbositystringsummary (default, token-efficient), headers, or full. Auto-downgraded to summary when extract is set.

No output schema declared.

No examples provided.

http_request ~214

REST/HTTP request with auth, assertions, {{var}} extraction. Returns token-efficient summary.

NameTypeReqDescription
assertarraye.g. [{status:200},{jsonpath:'$.x',equals:1},{timeMs:{lt:500}}].
authobject
bodyRequest body (object=json, string=text).
bodyTypestringDefault json.
envstringEnvironment name for variable resolution.
extractobjectCapture vars: { token: '$.token' }. Use via {{token}} later.
followRedirectsboolean
headersobject
methodstringHTTP method (default GET).
queryobject
timeoutMsinteger
urlstringyesFull URL. May contain {{variables}}.
verbositystringsummary (default, token-efficient), headers, or full. Auto-downgraded to summary when extract is set.

No output schema declared.

No examples provided.

import_curl ~76

Parse curl into structured request. Optionally execute it.

NameTypeReqDescription
curlstringyesThe full curl command, e.g. "curl -X POST https://... -H '...' -d '...'".
executebooleanIf true, run the parsed request and return the result.
verbositystring

No output schema declared.

No examples provided.

import_har ~166

Parse HAR file → Lunge collection. Splits query/headers/body. Optional 2xx filter. Params: path (required, .json HAR file), out (optional, write to .json/.yaml/.yml), only2xx (optional, only keep 2xx responses), maxSteps (optional, cap step count, default 200). Returns {ok, imported, name, steps, writtenTo}.

NameTypeReqDescription
maxStepsintegerCap the number of generated steps (default 200).
only2xxbooleanOnly include requests that returned a 2xx response.
outstringWrite the resulting collection to this path (.yaml/.yml/.json).
pathstringyesPath to the HAR file (.json).

No output schema declared.

No examples provided.

import_openapi ~165

Parse OpenAPI/Swagger (JSON/YAML) → Lunge collection. One step per operation with 2xx assertion. Params: path (required, file path), out (optional, write collection to .json/.yaml/.yml), includeTags (optional, only ops with these tags), maxSteps (optional, cap step count, default 200). Returns {ok, imported, name, steps, writtenTo}.

NameTypeReqDescription
includeTagsarrayOnly import operations with any of these tags.
maxStepsintegerCap the number of generated steps (default 200).
outstringWrite the resulting collection to this path (.yaml/.yml/.json).
pathstringyesPath to the OpenAPI/Swagger file.

No output schema declared.

No examples provided.

inspect_response ~220

Drill into a stored response by handle without re-running the request. Use jsonpath to pull only the slice you need. Supports RFC 9535 filters ($.items[?@.id==1]) and slices ($.items[0:5]). Use double quotes in filters. Omit jsonpath to return the full stored body — for graphql_introspect this is the enriched `schema` (so $.queries, $.mutations, $.inputTypes work directly); for ws_session it's the `frames` array; for sse_session it's the `events` array; otherwise it's the parsed bodyJson/bodyText.

NameTypeReqDescription
handlestringyesresponseHandle from a prior tool call.
jsonpathstringRFC 9535 JSONPath. Filters need double quotes: [?@.name=="x"]. Omit for full body.
maxItemsintegerCap array elements returned (default 50). Excess shown as truncation marker.
maxStrintegerCap string length in chars (default 2000).

No output schema declared.

No examples provided.

list_collections ~41

Find collection files (.yaml/.yml/.json) under a directory.

NameTypeReqDescription
dirstringDirectory to scan. Defaults to the current working directory.

No output schema declared.

No examples provided.

list_envs ~36

List env names and (masked) variables of the active or specified one.

NameTypeReqDescription
namestringShow variables for this env.

No output schema declared.

No examples provided.

list_history ~98

List all requests recorded in this session with full specs (method, url, query, headers, body, auth, assert, extract) and extracted values. Use this to review what happened before saving a multi-step collection. Each entry has an id (req_1, req_2, ...) for use with save_collection. Returns {count, entries:[{id, type, request, assert, extract, extractedValues, responseHandle}]}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

run_collection ~95

Run declarative collection file. Threads extracted vars between steps. Optional JUnit XML export.

NameTypeReqDescription
envstringEnvironment to resolve variables from.
junitPathstringWrite a JUnit XML report to this path.
onlyarrayOnly run steps with these ids.
pathstringyesPath to the collection file.
tagsarrayOnly run steps having any of these tags.

No output schema declared.

No examples provided.

save_collection ~269

Save multiple requests as a multi-step collection file. Params: path (required, .json/.yaml/.yml), fromHistory (optional, array of history ids from list_history — saves in specified order; omit to save ALL history), steps (optional, explicit step specs — overrides fromHistory; call collection_format first for the schema), name (optional, collection name), description (optional), vars (optional), defaults (optional). Steps preserve extraction chaining ({{var}} from earlier steps' extract). Returns {saved, path, stepCount, stepIds}.

NameTypeReqDescription
defaultsobjectDefault settings applied to every step (e.g. {timeoutMs: 10000, headers: {Accept: 'application/json'}}).
descriptionstringCollection description.
fromHistoryarrayHistory entry ids to save (e.g. ['req_1','req_3']). Omit to save ALL history.
namestringCollection name.
pathstringyesCollection file path (.json/.yaml/.yml).
stepsarrayExplicit step specs. Overrides fromHistory if provided.
varsobjectCollection-level variables (e.g. {baseUrl: 'https://...', apiKey: '{{env.API_KEY}}'}).

No output schema declared.

No examples provided.

save_request ~215

Persist last ad-hoc request (or explicit spec) as a new step in a collection file. Params: path (required, .json/.yaml/.yml), id (optional, step id), type (optional, http|graphql|ws|sse), request (optional, explicit spec; defaults to last call's request), assert, extract, tags, name (optional, set collection name). Returns {saved, path, stepId, stepCount} or isError if no prior request and no explicit request.

NameTypeReqDescription
assertarray
extractobject
idstringStep id. Defaults to a generated one.
namestringSet/replace the collection name.
pathstringyesCollection file path (.yaml/.yml/.json).
requestobjectExplicit request spec. Defaults to the last call's request.
tagsarray
typestringStep type; defaults to the last request's type.

No output schema declared.

No examples provided.

set_env ~65

Create/update named env. Values may be {value, secret:true}. Use via {{name}}.

NameTypeReqDescription
namestringyesEnvironment name, e.g. 'dev'.
varsobjectyesMap of variables. Use { value, secret: true } to mark secrets.

No output schema declared.

No examples provided.

set_policy ~110

Configure host allow/deny lists + dry-run mode. Glob patterns: *, *.example.com. Pass an empty array to allow/deny to clear that list. Returns {policy:{allow,deny,dryRun}}.

NameTypeReqDescription
allowarrayAllowed host patterns. Empty = allow any non-denied host.
denyarrayDenied host patterns; takes precedence over allow. Pass [] to clear.
dryRunbooleanIf true, validate requests but do not send them.

No output schema declared.

No examples provided.

sse_session ~164

Subscribe to SSE, collect events until stop condition. Returns summarized batch with assertions. Event shape: {event:string, data:string, id:string|null, json:object|null}. Assertions: anyEvent {jsonpath,equals} matches any event; eventCount {gte/lte/eq}. Example: assert=[{anyEvent:{jsonpath:'$.event',equals:'notification'}},{eventCount:{gte:1}}].

NameTypeReqDescription
assertarraye.g. [{anyEvent:{jsonpath:'$.type',equals:'tick'}},{eventCount:{gte:1}}]
collectobject
envstring
headersobject
urlstringyesSSE endpoint URL.
verbositystring

No output schema declared.

No examples provided.

ws_close ~31

Close a persistent WebSocket connection and release its handle.

NameTypeReqDescription
handlestringyesHandle returned by ws_open.

No output schema declared.

No examples provided.

ws_open ~82

Open long-lived WS, return handle. Use ws_send/ws_recv/ws_close to interact.

NameTypeReqDescription
envstring
headersobject
sendarrayMessages to send immediately after connecting.
subprotocolsarray
urlstringyesws:// or wss:// URL. May contain {{variables}}.

No output schema declared.

No examples provided.

ws_recv ~74

Drain buffered frames from persistent WS. Blocks up to maxDurationMs for first frame.

NameTypeReqDescription
handlestringyesHandle returned by ws_open.
maxDurationMsintegerMax wait for the first frame (default 1000ms).
maxMessagesintegerMax frames to drain (default 50).

No output schema declared.

No examples provided.

ws_send ~64

Send a single message on a persistent WebSocket connection opened with ws_open.

NameTypeReqDescription
handlestringyesHandle returned by ws_open.
jsonSend as a JSON message (mutually exclusive with text).
textstringSend as a raw text message.

No output schema declared.

No examples provided.

ws_session ~188

Connect WS, send messages, collect frames until stop condition. Returns summarized batch. Frame shape: {type:'text'|'binary', text:string, json:object|null}. Assertions: anyFrame {jsonpath,equals} matches any frame; frameCount {gte/lte/eq}. Example: assert=[{anyFrame:{jsonpath:'$.type',equals:'text'}},{frameCount:{gte:1}}].

NameTypeReqDescription
assertarraye.g. [{anyFrame:{jsonpath:'$.type',equals:'ack'}},{frameCount:{gte:1}}]
collectobject
envstring
headersobject
sendarrayMessages to send after connecting.
subprotocolsarray
urlstringyesws:// or wss:// URL.
verbositystring

No output schema declared.

No examples provided.

Common questions

What is the io.github.thuupx/lunge MCP server?

io.github.thuupx/lunge is an MCP server listed in the public MCP registry as io.github.thuupx/lunge. Agent-native API client: execute/test REST/GraphQL/WS/SSE with assertions, extraction, collections. This page covers its npm package (lunge-mcp).

Is the io.github.thuupx/lunge MCP server safe to use?

io.github.thuupx/lunge scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.thuupx/lunge MCP server expose?

io.github.thuupx/lunge exposes 22 tools: http_request, graphql_request, ws_session, sse_session, inspect_response, and 17 more. Their descriptions and schemas cost roughly 2,743 tokens of context every time the server is loaded.

Is the io.github.thuupx/lunge MCP server still maintained?

io.github.thuupx/lunge is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.thuupx/lunge MCP server under?

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