Inquiry Background Check MCP

get_background_check_report

Fetch RAW inquiry data by inquiry_id — use sparingly only for fields missing from a previously rendered business report.

Auth required: yes

Parameters

• inquiry_id: Required. Inquiry identifier supplied by the user.
• question: Optional. Topic/field the user is asking about, used to rank relevant tables first.

render_inquiry_report

Render an inquiry's data as a business-ready Markdown report — the DEFAULT first-call tool for viewing an inquiry.

Auth required: yes

Parameters

• inquiry_id: Required. Inquiry identifier supplied by the user.
• question: Optional. Topic forwarded to the raw-data layer to rank relevant tables. No effect on what is rendered.
• with_email: Optional. Include the reply-email block (default false).
• with_raw: Optional. Append a desensitized raw JSON dump (default false).

list_my_background_check_inquiries

List the inquiry_ids the current user is allowed to read.

Auth required: yes

Parameters

submit_background_check_inquiry

Submit a new background check inquiry on behalf of a customer.

Auth required: yes

Parameters

• email_title: Required. Subject/title of the inquiry email.
• email: Required. Customer email address.
• source: Required. Originating website/channel as a bare domain WITHOUT http(s):// or www. — NOT 'MCP' (MCP is the submission mechanism, not the source).
• ip: Optional. Customer IP address (sent as empty string if None).
• description: Optional. Brief description of the inquiry (default 'unknown').
• custom_fields: Optional. Key-value metadata about the inquiry itself (e.g. crm_id, source tag).
• prompt: Optional. Extra instructions/business context for the AI agent; only fill when the user's reply contains requirement-style or user-company-info content.