Answer Hub · Software & workflow

Are actions taken through an AI assistant logged in RAZE?

Reviewed by
Reviewed by RAZE
Last reviewed

Short answer

Yes. Actions taken through the RAZE MCP are logged in RAZE. An order placed from an assistant creates the same inspection record as an order placed in the Ordering Engine or by API, with the same history of status changes and who made them.

What is logged.

The Model Context Protocol (MCP) is an open specification, published at modelcontextprotocol.io, for how an AI assistant connects to outside software through a defined set of tools. The RAZE MCP is RAZE's server on that protocol, and actions taken through it are logged in RAZE.

Each person signs in to the RAZE MCP with their own RAZE credentials, so the assistant works as that user and inside that user's RAZE permissions. There is no shared login for a team to pass around.

One record, three ways to order.

There are three ways to order a RAZE draw inspection: the Ordering Engine, the RAZE API and the RAZE MCP. All three reach the same inspection workflow, the same report and the same record. An order placed from an assistant creates the same inspection record as an order placed in the Ordering Engine or by API, with the same history of status changes and who made them.

A team does not keep a second file for work done from an assistant. A reviewer who opens the inspection in the Ordering Engine sees the order, the status history, the report and the photos, whichever way it was ordered.

Why it matters for lenders.

A lender has to be able to show who ordered an inspection, when its status changed and who reviewed it. Work done from an AI assistant should not leave a gap in that story.

Two records are involved, and they sit in different places:

  • The inspection record stays in RAZE. The order, the history, the report and the photos are in RAZE however the work was started.
  • The conversation stays with the assistant. How the assistant stores or uses what your team asks it is governed by your agreement with its provider and your plan's administrator settings. Include those terms in your vendor review.

How RAZE handles it.

By default, the RAZE MCP shows a summary and waits for your confirmation before it creates or changes anything. A user can tell the assistant to skip that step, so set your team's rule: keep confirmation on. Either way, the action is logged in RAZE.

A reviewer can ask the assistant for an inspection's status and history, then read the same history in RAZE. Your reviewer still accepts or rejects each submitted inspection, unless your institution has turned on the auto-approve workflow setting, and the funding decision stays with the lender.

The RAZE MCP FAQs cover access, confirmation and controls, and the compliance and audit FAQs cover the inspection record. To begin, Get Started.

Sources

Primary sources only. Where a figure appears on this page, it comes from one of these.

  1. 1.Model Context Protocol specification (revision 2026-07-28)Model Context Protocol · modelcontextprotocol.io
  2. 2.RAZE MCP FAQsRAZE
  3. 3.Set Up the RAZE MCPRAZE
  4. 4.Draw Inspection Compliance and Audit FAQsRAZE

See the workflow behind the answer.

RAZE standardizes how draw inspections are ordered, dispatched, captured and delivered, inside the loan administration workflow a lender already runs.

Get Started