For AI agents
Connect your agent.
Follow the changes.
Ask about the domains you track. Review what changed. Set up monitoring from the agent you already use.
Get the setup commandMCP access to your account. Read access by default. You choose whether an agent can change monitoring.
Start in your agent
Connect Track.Name to your agent
Paste this into your agent. The guide covers the skill, connection and secure token setup.
Prefer to set it up yourself?
1. Install the skill
Run this in a terminal with Node.js installed, then choose your agent. The ZIP includes the skill and supporting setup instructions. Account access comes next.
2. Create a read-only token
In Connected agents, name the connection and choose an expiry. Leave monitoring changes off to start. Save the token in your client’s secure settings, or an environment variable named TRACKNAME_TOKEN available to the agent process.
Never paste the token into an agent conversation. An environment variable set in a terminal may not be available to a desktop app; follow that client’s setup instructions.
Open Connected agents3. Connect MCP and check access
Once the token is available to your client, use its connection command below. If a connection named track-name already exists, review it before adding another.
Transport: Streamable HTTP. Set the Authorization header to Bearer followed by the token using your client’s secure connection settings. Header and environment-variable syntax vary by client.
Reconnect or restart your agent if needed, then ask: “List the domains I track and show recent confirmed changes.” If setup is incomplete, the agent should tell you what remains.
Clients that require an OAuth sign-in connection are not supported yet.
Once connected
Start with
a question.
Ask what changed, inspect the evidence or review monitoring settings. Your agent works with the same records you see in Track.Name.
What changed across the domains I track?
Read recent changes
example.com has a confirmed nameserver change. Here are the previous and latest records, with the times they were observed.
- Before
- ns1.old.example
- After
- ns1.new.example
A record change does not establish a change of ownership.
Show me the evidence for the website change on example.com.
Read recorded evidence
The website response changed from 200 to 503. The confirmed record includes both results. Check the latest observation before assuming the issue is ongoing.
- Before
- 200 · Responding
- After
- 503 · Service unavailable
Results describe recorded checks, not continuous availability.
Watch /pricing on example.com and include content changes in the daily summary.
Review settings before applying
I will set the monitored page to /pricing and include content updates in the daily summary. Other checks continue. Review these changes before I save them.
- Before
- Page · /
- After
- Page · /pricing
Requires permission to change monitoring settings.
You set the access
Start with a look.
Allow changes when ready.
Revoke a connection from the dashboard at any time. Agent access does not include billing or registrar controls.
- Read monitoringDefault
- List tracked domains, check their status and read recorded changes. See the evidence and observation times behind a result.
- Change monitoringOptional
- Preview and add domains within the available allowance. Update the monitored page, watched words, supported technical settings and email topics.
- The same monitoring rules
- Email topics decide which updates reach the inbox; they do not turn off checks. Scheduled checks continue after an agent disconnects. One configured website page is monitored per domain.
A question is a good place to start.
Connect an agent to an existing account, or start by tracking a domain.