BIMI Record Skill
The tool
Let your agent check BIMI records. Call it as an MCP tool to confirm a domain publishes a valid BIMI logo and VMC in DNS — in real time.
Once your client is connected to the VerveKit MCP server, this appears in its tool list as BIMIRecordSkill. 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": "BIMIRecordSkill",
"arguments": {
"domain": "ebay.com"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about ebay.com in the terms this source covers is enough for it to reach for BIMIRecordSkill 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/mcpPer-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.
| Argument | Type | Example | Description |
|---|---|---|---|
domainRequired | string | ebay.com | The domain to validate the BIMI record for |
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": {
"host": "ebay.com",
"bimi_host": "default._bimi.ebay.com",
"has_bimi_record": true,
"bimi_record": "v=BIMI1;l=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg;a=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem",
"bimi_records_count": 1,
"version": "BIMI1",
"svg_logo": {
"url": "https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg",
"status_code": 200,
"valid": true,
"file_size_bytes": 1518
},
"vmc_certificate": {
"url": "https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem",
"status_code": 200,
"valid": true
},
"issues_found": [],
"valid": true
}
}Fields
| Field | Type | Example | Description |
|---|---|---|---|
host | string | ebay.com | The domain name that was validated |
bimi_host | string | default._bimi.ebay.com | The BIMI DNS record host location |
has_bimi_record | boolean | true | Whether a BIMI record exists for domain |
bimi_recordPremium | string | v=BIMI1;l=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg;a=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem | The complete BIMI DNS record content |
bimi_records_count | number | 1 | Number of BIMI records found in DNS |
version | string | BIMI1 | BIMI protocol version identifier |
svg_logoPremium | object | {…} | SVG logo validation details |
svg_logo.url | string | https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg | URL where the SVG logo is hosted |
svg_logo.status_code | number | 200 | HTTP status code when fetching SVG logo |
svg_logo.valid | boolean | true | Whether the SVG logo file is valid |
svg_logo.file_size_bytes | number | 1518 | Size of SVG logo file in bytes |
vmc_certificatePremium | object | {…} | VMC certificate validation details |
vmc_certificate.url | string | https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem | URL where the VMC certificate is hosted |
vmc_certificate.status_code | number | 200 | HTTP status code when fetching certificate |
vmc_certificate.valid | boolean | true | Whether the VMC certificate is valid |
issues_found | array | [] | List of validation issues discovered during check |
valid | boolean | true | Overall validity status of BIMI record |
Failure modes
Errors come back as tool errors with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This skill isn't part of VerveKit. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
Other ways to use BIMI Record Skill
Set up BIMI Record 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
Do I have to tell the agent to use BIMIRecordSkill?
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 VerveKit 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?
5 credits 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.