Veridomo -- DNS MCP Tools for GitHub Actions & Copilot

GitHub Actions workflow

Verify domains, check SSL certs, and audit email auth from your CI/CD pipeline. Perfect for pre-deployment checks, monitoring, and automated compliance.

Verify a domain before deploying

# .github/workflows/verify-domain.yml
name: Verify domain ownership
on:
  workflow_dispatch:
    inputs:
      domain:
        description: 'Domain to verify'
        required: true

jobs:
  verify:
    runs-on: ubuntu-latest
    steps:
      - name: Create challenge
        run: |
          RESPONSE=$(curl -s -X POST https://veridomo.xyz/challenge \
            -H "Authorization: Bearer ${{ secrets.VERIDOMO_KEY }}" \
            -H "Content-Type: application/json" \
            -d '{"domain":"${{ inputs.domain }}","method":"dns_txt"}')
          echo "Add this TXT record to prove ownership:"
          echo "$RESPONSE" | jq '.dns_txt'

Check SSL certs on a schedule

# .github/workflows/ssl-audit.yml
name: SSL certificate audit
on:
  schedule:
    - cron: '0 6 * * 1'  # Every Monday at 6am

jobs:
  ssl-check:
    runs-on: ubuntu-latest
    steps:
      - name: Check SSL for veridomo.xyz
        run: |
          curl -s -X POST https://veridomo.xyz/mcp \
            -H "Authorization: Bearer ${{ secrets.VERIDOMO_KEY }}" \
            -H "Content-Type: application/json" \
            -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ssl_check","arguments":{"host":"veridomo.xyz"}}}' \
            | jq '.result'

Email auth audit on every PR

# .github/workflows/email-audit.yml
name: Email auth audit on PR
on: [pull_request]

jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - name: Audit SPF/DKIM/DMARC
        run: |
          curl -s -X POST https://veridomo.xyz/mcp \
            -H "Authorization: Bearer ${{ secrets.VERIDOMO_KEY }}" \
            -H "Content-Type: application/json" \
            -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"email_auth_audit","arguments":{"domain":"veridomo.xyz"}}}' \
            | jq '.result'

GitHub Copilot integration

Veridomo speaks MCP natively. GitHub Copilot supports MCP servers as extensions. Add Veridomo to your Copilot agent and it can verify domains, query DNS, check SSL certs, and audit email auth -- all from natural language prompts.

What your Copilot can do with Veridomo:

"Verify that example.com is configured for email"

Copilot calls email_auth_audit, returns SPF/DKIM/DMARC status

"Check when veridomo.xyz SSL cert expires"

Copilot calls ssl_check, returns days remaining and expiry date

"Who owns this domain?"

Copilot calls whois_lookup, returns registrar and registration dates

"Prove this domain is mine before deploying"

Copilot calls verify_domain, creates challenge, guides you through setup

Setup is the same as any MCP client. Add your Veridomo API key and endpoint URL to Copilot's MCP configuration. See the full MCP setup guide for details.

GitHub Actions secret setup

Store your Veridomo API key as a GitHub secret so workflows can access it securely:

# 1. Go to your repo Settings > Secrets and variables > Actions
# 2. Add a new repository secret:
#    Name:  VERIDOMO_KEY
#    Value: vdo_YOUR_API_KEY
#
# 3. Reference it in workflows as: ${{ secrets.VERIDOMO_KEY }}

DevOps agent loops

Veridomo's MCP tools slot into DevOps agent frameworks like Kiro, Antigravity, and Cognition -- autonomous agents that provision infrastructure, configure DNS, issue certificates, and monitor production. These agents run in loops: observe, decide, act. Veridomo gives them the DNS layer.

Infrastructure provisioning loops

Before an agent provisions a new service on a custom domain, it verifies ownership. Before it issues an SSL cert, it checks what's already there. Before it configures email, it audits SPF/DKIM/DMARC. Veridomo gives the agent the DNS data it needs to act safely.

Monitoring & remediation loops

Agent detects expired SSL cert via ssl_check. Agent finds a misconfigured SPF record via email_auth_audit. Agent discovers a domain transfer via whois_lookup. Each tool returns structured JSON the agent can act on without shell scripting.

gRPC-native MCP (coming)

The MCP specification is evolving to support gRPC as a first-class transport alongside HTTP. When gRPC MCP lands, Veridomo's tool definitions map directly to protobuf service descriptors. Agents using Kiro, Antigravity, or custom gRPC-based runtimes will call Veridomo DNS tools with native gRPC performance -- multiplexed streams, binary framing, sub-millisecond overhead. Same five tools. Lower latency. Higher throughput.

GitHub Actions & Copilot integration.