Cert Spotter MCP integration for AI agents.
Connect AI agents to Cert Spotter through 5 structured actions, including get monitored domain, upsert monitored domain, and delete monitored domain. Review…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Cert Spotter integration exposes
The Cert Spotter Agent App exposes 5 provider-backed actions for security and data work. Its current contract lets an authorized agent get one monitored domain configuration from the connected cert spotter account, create or update one monitored domain configuration in the connected cert spotter account, and delete one monitored domain configuration from the connected cert spotter account. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Cert Spotter account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Cert Spotter capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_monitored_domainREADGet one monitored domain configuration from the connected Cert Spotter account.
INPUTS: name
upsert_monitored_domainWRITECreate or update one monitored domain configuration in the connected Cert Spotter account.
INPUTS: name / enabled
delete_monitored_domainHIGH IMPACTDelete one monitored domain configuration from the connected Cert Spotter account.
INPUTS: name
list_certificate_issuancesREADList certificate issuances for one domain from the Cert Spotter CT Search API.
INPUTS: domain / after / include_subdomains / match_wildcards / expand
list_monitored_domainsREADList monitored domains configured in the connected Cert Spotter account.
INPUT CONTRACTS
Know what the action needs before it runs.
get_monitored_domain
nameREQUIRED- The monitored domain name. Prefix with a leading dot to cover the entire subdomain tree.
upsert_monitored_domain
nameREQUIRED- The monitored domain name. Prefix with a leading dot to cover the entire subdomain tree.
enabledOPTIONAL- Whether monitoring should be enabled for this domain.
delete_monitored_domain
nameREQUIRED- The monitored domain name. Prefix with a leading dot to cover the entire subdomain tree.
list_certificate_issuances
domainREQUIRED- The registered domain or subdomain to search in the CT Search API.
afterOPTIONAL- Return issuances discovered after the issuance with this Cert Spotter ID.
include_subdomainsOPTIONAL- Whether to include issuances for subdomains of the requested domain.
match_wildcardsOPTIONAL- Whether to include wildcard certificates that match the requested domain.
expandOPTIONAL- Repeatable Cert Spotter expand fields to include in the response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Monitored Domain
Get one monitored domain configuration from the connected Cert Spotter account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_monitored_domainControl Upsert Monitored Domain
Create or update one monitored domain configuration in the connected Cert Spotter account. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
upsert_monitored_domainVerify with List Certificate Issuances
List certificate issuances for one domain from the Cert Spotter CT Search API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_certificate_issuancesSAFETY BOUNDARY
Operate Cert Spotter with explicit limits
- Authorize Cert Spotter with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_monitored_domain` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Cert Spotter rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Cert Spotter task completed successfully.
CONNECTION MODEL
API key
SSLMate API key used with the Authorization Bearer header for Cert Spotter. Find it on your SSLMate API keys page: https://sslmate.com/account/api_keys
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Cert Spotter.