CAA Record Parser Skill

The tool

The API parses CAA record strings and provides detailed information about issuance policies, including recognized CA providers and critical flags.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as CAARecordParserSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

{
  "name": "CAARecordParserSkill",
  "arguments": {
    "record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about example.com. 3600 IN CAA 0 issue "letsencrypt.org" in the terms this source covers is enough for it to reach for CAARecordParserSkill on its own.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

{
  "status": "ok",
  "error": null,
  "data": {
    "raw_record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\"",
    "parsed": {
      "domain": "example.com",
      "ttl": 3600,
      "class": "IN",
      "flags": 0,
      "tag": "issue",
      "value": "letsencrypt.org"
    },
    "ca_info": {
      "name": "Let's Encrypt",
      "type": "Free",
      "wildcard_support": true
    },
    "interpretation": {
      "meaning": "Only letsencrypt.org is authorized to issue certificates",
      "restriction": "Restricted to specific CA",
      "critical": false,
      "critical_explanation": "Non-critical - CA may proceed if not understood"
    },
    "tag_description": "Authorizes a CA to issue certificates (any type)",
    "is_valid": true
  }
}

Fields

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

Other ways to use CAA Record Parser Skill

Set up CAA Record Parser Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Frequently asked questions