MCP connection guide

Connect your AI assistant to SecureMark’s DMARC MCP server

Ask your assistant about your domains, DMARC results and sending sources.

API documentation

Set up your connection

  1. Ask your organization owner or admin to enable API access on an eligible plan.
  2. In an assistant that supports remote MCP, add https://securemark.leadify.biz/mcp.
  3. If browser authorization is available, sign in and review the application name, callback, organization, domains and read permissions.
  4. Ask: "Summarize my domain's DMARC results for last week and show the data behind the answer."

Browser authorization is not enabled on this site. Use a client that supports an API key in its secure connection settings.

Client compatibility depends on its transport and authorization support. The server supports Streamable HTTP and public OAuth clients using PKCE when browser authorization is enabled.

Developer agents and scripts

Create a named API key in your organization's API access page. Start with domain and analytics read permissions and select the required domains. Add detailed report access only if needed.

Configure this header in your client's secret settings. Keep keys out of prompts, shared configuration and URLs.

Authorization: Bearer <api-key>

Agents that make HTTP requests can use https://securemark.leadify.biz/api/v1 directly. Read the API documentation or download its OpenAPI contract.

Your data and access

The assistant receives the selected data when it calls a tool. These tools read stored aggregate reports; they cannot change your DNS, send email or change billing. Reports contain sending IPs and authentication results, not email bodies.

Disconnect an agent from API access whenever needed. New requests stop immediately; data already shared remains subject to the assistant's own storage controls.

Results can arrive late and stored checks may be stale. Ask your agent to include dates, freshness and any incomplete pages. Read the machine-readable guide.