DANE Record Grounding Data for AI AgentsDANE Record Grounding Data for AI Agents

OnlineCredit Usage:1 per callTool:DANERecordGroundingDataforAIAgents

The tool

The API parses TLSA records and validates usage types, selector types, and matching types while providing detailed explanations of each field and security implications.

Once your client is connected to the VerveContext MCP server, this appears in its tool list as DANERecordGroundingDataforAIAgents. 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.

Tool call
{
  "name": "DANERecordGroundingDataforAIAgents",
  "arguments": {
    "record": "_443._tcp.example.com. 3600 IN TLSA 3 1 1 2bb183af273adee2e02d60ba7a0dc0efcf5e0a2af42dab7b3f8ba9c0def1f6c8"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about _443._tcp.example.com. 3600 IN TLSA 3 1 1 2bb183af273adee2e02d60ba7a0dc0efcf5e0a2af42dab7b3f8ba9c0def1f6c8 in the terms this source covers is enough for it to reach for DANERecordGroundingDataforAIAgents on its own.

Connecting

One server URL covers every source 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.

Client config
{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervecontext.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.

ArgumentTypeExampleDescription
recordRequiredstring_443._tcp.example.com. 3600 IN TLSA 3 1 1 2bb183af273adee2e02d60ba7a0dc0efcf5e0a2af42dab7b3f8ba9c0def1f6c8The DANE/TLSA record string to validate

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.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "raw_record": "_443._tcp.example.com. 86400 IN TLSA 3 1 1 0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF",
    "parsed": {
      "name": "_443._tcp.example.com.",
      "port": 443,
      "protocol": "tcp",
      "hostname": "example.com",
      "ttl": 86400,
      "class": "IN",
      "usage": 3,
      "selector": 1,
      "matching": 1,
      "certificate_data": "0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF",
      "certificate_data_length": 64
    },
    "interpretation": {
      "usage": {
        "name": "DANE-EE",
        "description": "Domain-issued certificate",
        "full_description": "Certificate must exactly match the provided association data (most common)"
      },
      "selector": {
        "name": "SPKI",
        "description": "SubjectPublicKeyInfo",
        "full_description": "Match against the Subject Public Key Info (recommended)"
      },
      "matching": {
        "name": "SHA-256",
        "description": "SHA-256 hash",
        "full_description": "SHA-256 hash of the selected content (recommended)"
      },
      "security_level": "Recommended",
      "recommendation": "This is the recommended DANE configuration (DANE-EE + SPKI + SHA-256)"
    },
    "validation": {
      "is_valid": true,
      "certificate_data_format": "Valid hexadecimal",
      "certificate_data_length_valid": true
    }
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
raw_recordstring_443._tcp.example.com. 86400 IN TLSA 3 1 1 0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEFOriginal DANE/TLSA record string input
parsedobject{…}
parsed.namestring_443._tcp.example.com.Fully qualified domain name from TLSA record
parsed.portnumber443Port number specified in TLSA record
parsed.protocolstringtcpProtocol type (tcp or udp) from record
parsed.hostnamestringexample.comExtracted hostname without service prefix
parsed.ttlnumber86400Time to live value in seconds
parsed.classstringINDNS class designation (typically IN)
parsed.usagenumber3TLSA usage field value (0-3)
parsed.selectornumber1TLSA selector field value (0-1)
parsed.matchingnumber1TLSA matching type field value (0-3)
parsed.certificate_datastring0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEFHexadecimal certificate association data
parsed.certificate_data_lengthnumber64Length of certificate data in characters
interpretationPremiumobject{…}Detailed interpretation and security analysis of DANE record
interpretation.usagePremiumobject{…}
interpretation.usage.namePremiumstringDANE-EEHuman-readable TLSA usage type name
interpretation.usage.descriptionPremiumstringDomain-issued certificateShort description of usage type meaning
interpretation.usage.full_descriptionPremiumstringCertificate must exactly match the provided association data (most common)Comprehensive explanation of usage field
interpretation.selectorPremiumobject{…}
interpretation.selector.namePremiumstringSPKIHuman-readable selector type designation
interpretation.selector.descriptionPremiumstringSubjectPublicKeyInfoShort description of selector meaning
interpretation.selector.full_descriptionPremiumstringMatch against the Subject Public Key Info (recommended)Detailed explanation of selector type
interpretation.matchingPremiumobject{…}
interpretation.matching.namePremiumstringSHA-256Human-readable matching algorithm name
interpretation.matching.descriptionPremiumstringSHA-256 hashShort description of matching algorithm
interpretation.matching.full_descriptionPremiumstringSHA-256 hash of the selected content (recommended)Detailed explanation of matching algorithm
interpretation.security_levelPremiumstringRecommendedSecurity assessment of configuration level
interpretation.recommendationPremiumstringThis is the recommended DANE configuration (DANE-EE + SPKI + SHA-256)Expert security recommendation for configuration
validationobject{…}
validation.is_validbooleantrueOverall validation result for DANE record
validation.certificate_data_formatstringValid hexadecimalCertificate data hexadecimal format validation result
validation.certificate_data_length_validbooleantrueValidation status of certificate data length

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value with a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at raw_record: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

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

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This source isn't part of VerveContext. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use DANE Record Grounding Data for AI Agents

Set up DANE Record Grounding Data for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKitReference →

Frequently asked questions

Do I have to tell the agent to use DANERecordGroundingDataforAIAgents?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveContext catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?