Track.Name for agents
Bring your agent.
Follow the changes.
Ask about the domains you track. Review what changed. Set up monitoring from the agent you already use.
MCP access to your account. Read access by default. You choose whether an agent can change monitoring.
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.
The connection.
The instructions.
01 / MCP server
Give the agent access.
Read recorded results and make permitted changes to monitoring. Every request uses your account’s access and limits.
Set up the connection02 / Agent skill
Give the agent context.
A small instruction file explains supported checks, how to read evidence and how to review settings before changing them.
Download SKILL.mdGet connected
Three steps.
Then ask.
Use an MCP client that supports a remote Streamable HTTP server and a bearer Authorization header.
Clients that require an OAuth sign-in connection are not supported yet.
- 01
Create an agent token.
Sign in and open Connected agents. Name the connection and choose its expiry. Keep read access for reviewing results, or also allow monitoring changes.
Create agent token - 02
Add the MCP connection.
In your client’s MCP settings, use this server URL and set the Authorization header to a bearer token. Store the token using the client’s secret or environment settings.
https://staging.track.name/mcpCopy unavailable. Select the URL and copy it manually.
Connection reference
{ "url": "https://staging.track.name/mcp", "transport": "streamable-http", "headers": { "Authorization": "Bearer ${TRACKNAME_TOKEN}" } }This shows the connection values, not a universal client configuration. Adapt the format and environment-variable syntax to your client.
${TRACKNAME_TOKEN}is a placeholder; some clients do not expand it automatically. Never paste a token into a chat or commit it to a repository. - 03
Add the skill. Try a question.
Download the skill and save it as
Download the skilltrack-name/SKILL.mdin your agent’s skills directory. Follow your client’s instructions to load it. The file contains guidance; it does not grant account access.“List the domains I track and show any recent confirmed changes.”
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.