DingoDocs Book a call

MCP-connected assessment delivery

Test with the agent. File as you go.

Point the AI agent you already use at DingoDocs. As it probes, fuzzes, and reads scanner output, it captures the command, the output, and the finding draft on the engagement. You review. Then you issue the report.

Book a call How MCP files the work Product brief (PDF)
DingoDocs dingo carrying assessment evidence in the Australian outback

One record from scope to retest.

DingoDocs follows the work instead of splitting it across documents, tickets, storage drives, and client email.

  1. Scope

    Approve targets, rules, dates, and delivery responsibilities.

  2. Capture

    The agent files CLI output, scanner results, notes, and evidence while it tests.

  3. Review

    Prioritise findings through explicit authoring, peer review, and publication states.

  4. Report

    Issue controlled, white-label reports from the findings the work already produced.

  5. Verify

    Track client remediation and complete evidence-backed retests.

Model Context Protocol

The agent tests. DingoDocs files.

Connect Grok, Claude, Cursor, or any MCP client with a scoped credential. While it runs Nuclei, Nmap, Burp, ZAP, or a fuzzer, it can store the input, the output, the note, and the write-up without leaving the session.

  1. Agent probes and fuzzes in the tools you already run
  2. capture_evidence stores terminal output and files
  3. ingest_scanner_results drafts findings from Nuclei, Nmap, Nessus, OpenVAS, ZAP, and Burp
  4. create_finding_write_up keeps the report body in draft
  5. You review and publish. DingoDocs renders the client report

Credentials carry defined scopes. Nothing reaches a client until a person advances the draft.

Review the public MCP source
DingoDocs integrations and automation settings

See what needs attention.

The workspace surfaces delivery state, review work, risk, and deadlines without turning the assessment into another dashboard project.

DingoDocs dashboard showing active engagements, reports in review, findings, and tasks
Operational overview for assessment teams.

Built for defensible delivery.

Every important state is explicit: who can act, what clients can see, what changed, and which report version was approved.

Assessment work stays connected

Scope, assets, notes, evidence, findings, tasks, time, QA, and reports remain attached to the engagement that produced them.

DingoDocs engagement workspace showing delivery status and assessment progress

Evidence keeps its history

Classification, checksums, retention, legal holds, annotations, and links to findings remain visible and auditable.

Clients see only approved material

Named client contacts receive engagement-specific access to shared findings, reports, evidence, remediation, and retests.

Professional reports, under your brand

Render controlled PDF, DOCX, HTML, and Markdown deliverables from approved findings and evidence.

DingoDocs report workspace with an assessment report in internal review

Dates and deadlines follow each user

Store date-time values as UTC instants, then display and interpret them in each user’s chosen IANA time zone.

DingoDocs personal preferences showing the user time zone setting

The agent files while it tests

MCP captures terminal output, scanner imports, testing notes, timeline events, and finding drafts as the agent probes and fuzzes. Clients see none of it until a person publishes.

Runbooks make testing repeatable

Publish reusable procedures, apply immutable snapshots to engagements, and link each test step to evidence, findings, or follow-up work.

Risk views focus remediation

Filter severity, workflow state, age, deadlines, and client exposure so the next priority is clear.

DingoDocs finding authoring and review workspace

Publishing is a deliberate state change.

Findings carry structured technical detail, impact, remediation, evidence, comments, ownership, and review history.

  • Draft and review states remain visible
  • Reasoned overrides create audit records
  • Client visibility is separate from publication
  • Retests preserve the original finding version

Customer-controlled deployment

Your assessment data stays in your environment.

Operate DingoDocs inside your security boundary. Control identity, storage, access, backups, retention, integrations, and recovery.

Book a call View source

Contact Yuma IT for commercial and AWS Marketplace procurement.

Point the agent at the engagement.

See how DingoDocs captures testing work as it happens, then turns reviewed findings into the report you issue.

Book a call