Show Novelty MCP status: which reasoning model is wired in and the tools available.

Send an HTTP(S) request and log it to history (like Burp Repeater + Logger).

Args: method: GET, POST, PUT, DELETE, … url: full target URL (a target you're authorized to test) headers_json: optional JSON object of request headers body: optional request body (for POST/PUT) Returns the logged entry id, status, timing, and a response preview.

List recently logged requests (the HTTP history / Logger view).

Show the full request and response (headers + body) for one logged entry.

Re-send a logged request with optional edits (Repeater tweak-and-resend).

Any argument left blank keeps the original request's value. Supplied headers are merged onto the original. Logs a new history entry.

Replay a logged request substituting marker with each payload (Intruder-lite).

Bounded to a small list — for enumeration/IDOR/auth checks, not stress testing. Args: request_id: a logged request to base the attack on marker: the placeholder string to replace (put it in the URL/body first) payloads_json: a JSON array of payload strings (e.g. ["1","2","3"])

Read-only recon of a web target: tech stack, headers, forms, script bundles, backend/third-party services, missing security headers, and exposed-file checks.

Run recon then an AI vulnerability hunt over the high-value classes (BOLA/BFLA/XSS/SQLi/business logic/RCE/auth). Non-destructive; authorized targets only. Returns findings with exploit scenarios, impact, a confirm test, and a fix.

Security-review a source file's contents with Claude (BOLA/BFLA/XSS/SQLi/ business-logic/RCE/auth). Pass the file text you have open; returns line-referenced findings with exploit + fix. Whole-file reasoning, not regex.

Same as review_code, but reads the file from a local path first.

Hunt a web target and produce a polished security-assessment report.

Runs recon + the AI hunt, then renders a Markdown report (returned) and, if save_html is given, a styled self-contained HTML report written to that path. Authorized, non-destructive; authorized targets only. Args: url: the target to assess save_html: optional path for the styled HTML report (e.g. "reports/dvwa.html")

Security-review a source file and produce a polished report (Markdown + optional HTML).

Args: path: local source file to review save_html: optional path for the styled HTML report

Render a report from findings you have ALREADY collected — e.g. the output of hunt/review combined with your own http_send/intruder evidence.

Args: findings_json: a JSON array of finding objects (Novelty or your own shape: title, severity, vuln_class, endpoint/file, exploit, impact, confirm_test, fix) target: the assessed target's name/URL (for the report header) kind: "web" or "source" save_html: optional path for the styled HTML report

Set the authorized testing scope — an allowlist of hosts. Once set, the traffic tools (http_send, recon, hunt, secrets_hunt, param_discover) refuse anything out of scope. Supports wildcards, e.g. ["*.example.com","api.foo.io"]. Args: hosts_json: a JSON array of hostnames/domains (or a plain comma list)

Show the current authorized scope (empty = not enforced).

Pull a target's page + JS bundles and flag leaked secrets (cloud keys, tokens, JWTs, private keys, provider keys). Read-only, non-destructive.

Mine parameters, endpoints, and forms from a target's HTML + JS — the attack surface you then probe with http_send / intruder. Read-only.

Consult Novelty's arsenal — a HackTricks-style bypass/technique reference — when a hunt is blocked by a control. Pull a class page or search all pages. Args: vuln_class: one of sqli, xss, idor-bola-bfla, auth-jwt, rce, ssrf, traversal, logic, waf (aliases like "idor","jwt","lfi" also work) query: free-text search across the arsenal if you don't know the class Call with neither to list the available pages.

Read Novelty's persistent hunt memory — recent milestones (recon/hunt/ finding/report), optionally filtered to a target. Secrets are never logged.

Append a milestone/lead to Novelty's hunt memory so a later session can pick it up. Do NOT put credentials/tokens here (they'd be scrubbed anyway).

Reason across findings for exploit CHAINS that raise impact (self-XSS + login-CSRF = ATO, info-leak + SSRF = cloud creds, …). Args: findings_json: a JSON array of finding objects (from hunt/review/report)

Adversarially triage ONE finding: is it real, exploitable and non-duplicate? Returns a verdict, dup-likelihood, adjusted severity, and the SAFE negative control to run to confirm or kill it. Args: finding_json: a single finding object as JSON

Create a throwaway inbox (mail.tm) for registering a test account on an app you're authorized to test. Returns an address to poll with mail_inbox().

Poll a throwaway inbox created by mail_new(). Returns messages and any links found (e.g. the verification link to finish signup).