Query Profundis through the API and MCP.
Use the API in your scripts or connect an MCP client to search Profundis. Restrict service credentials to the clients they need, set credit limits for batch jobs and receive events through webhooks.
Steps
Restrict the service credential
Configure access from the account or organization integration settings. For organization automation, create a service credential restricted to the required clients or asset scopes and capabilities. Keep it in your secret store, not in a shared prompt or report.
Set a budget for batch searches
Use the documented API or connect the MCP server to a compatible client. Organization batch workflows let you define a credit limit before submitting work and follow the resulting job. Results remain bounded by your access and available data.
Receive webhook events
Configure an organization webhook destination for supported events. Verify the signature in your receiver, handle repeated deliveries safely and inspect delivery history when an endpoint fails. Use the documentation to implement the event contract.
Example: research domains with a fixed budget
Give an automation credential access to one client. Submit the domains you want to research with a fixed credit limit, follow the job and review the source records before using them in a report. Publish the report after an analyst has reviewed it.
Data and service limitations
MCP lets a compatible client call Profundis tools. Check model-generated conclusions against the source records. API and MCP use the applicable permissions and credits. An integration does not grant unrestricted access to other clients or to datasets outside the account’s entitlements.
Practical questions
Does using MCP make searches free?
No. The underlying actions use the applicable access rules and credits. Check the operation and budget before running automated research.
Do we need a custom integration project?
The API, MCP setup and webhook documentation support self-service integration. You remain responsible for configuring the client and implementing your own receiver where needed.
Tools and documentation
Related guides
Monitor changes across your company’s domains.
Organize company domains by scope, monitor observed DNS, hosts and certificates, review changes and prepare recurring reports with your security team.
Pentest and cybersecurity consultanciesResearch your pentest targets and save the evidence.
Prepare a pentest with host, DNS, WHOIS and certificate research. Follow infrastructure connections and keep source evidence in client engagements.
MSSPs and recurring client servicesManage monitoring and reports for each client.
Keep research separate for each client, assign credit allowances and review scheduled infrastructure changes with reports and delivery diagnostics.