mcp deployment dns cdn verification agents 

Targetly

Deployment truth verification for AI agents. Targetly answers whether the live site is what you just built.

Version

v0.1.4

License

MIT

Platforms

Node 18 or newer, Any MCP client

Interfaces

CLI, MCP

View on GitHubnpm packageMCP server

Overview

Deploys lie. The build passes, the tool prints a production URL, and the live site still serves last week. The causes are ordinary: a domain proxied behind a CDN, a CNAME pointing at a platform you never deploy to, a cache holding old HTML, or two sites sharing a name. Targetly goes to the actual internet and checks, so the claim that something is live is verified, not assumed.

Setup

npm install -g targetly-mcp

Add the server to your MCP client.

{
  "mcpServers": {
    "targetly": {
      "command": "targetly-mcp",
      "args": []
    }
  }
}

Usage

  • targetly.origin resolve where a domain serves from. Returns the CNAME chain, A records, the detected platform, and whether the origin is hidden behind a CDN proxy.
  • targetly.verify fetch a live URL and check it against expectations. Provide markers the page must contain and markers that would prove it is stale. Returns LIVE_AND_CURRENT, MISMATCH, or UNREACHABLE.
  • targetly.cache inspect cache headers and judge whether a deploy is hidden behind a cached copy.
  • targetly.route compare what a domain points at with the deploy tooling in a build directory. Detects netlify.toml, wrangler.toml, and vercel.json, and returns ROUTE_ALIGNED or ROUTE_MISMATCH.

Typical agent instructions:

  • “Deploy this build and then verify the live site shows the new content.”
  • “Is this domain served by Cloudflare or Netlify?”
  • “Is the live homepage stale?”

Gains

  • Deploy loops close with proof, not a build log.
  • Misrouted deploys are caught before they waste a session.
  • Cache staleness is detected and named.
  • Proxied origins are reported honestly, so agents stop guessing where the truth lives.

Requirements

  • Node 18 or newer
  • Network access for DNS resolution and HTTP requests

Repository