GAIP Watch

Know the moment something your agent depends on changes.

An agent asks: Has https://huggingface.co/mcp changed since 1 October?
GAIP answers: Yes or no; what changed (tools, schema, sign-in, price); when GAIP read it; a signed receipt.
The call: GET /v1/free/watch/check?urls=https://huggingface.co/mcp&since=2026-10-01 or the MCP tool gaip_dependency_check

GAIP re-reads the agents, MCP servers and APIs you name every day and tells you what changed, with a receipt. Free, no account, no email.

Name what you depend on. An MCP server, an A2A card or an API, by URL.
GAIP reads it every day. It joins the dated, hash-chained record.
You get the change, not an opinion. By GitHub Action, HTTPS check or feed, with a receipt.

Watch an agent See a live example

GAIP receipt · Watchd8be…d69e

gateway.pipeworx.io

Observed 17 Oct 2026, 23:27:03 UTC

Change: 1 tool added: company_register_search
Class: tool added · schema changed
Manifest: 802ee9d0d7f0… → fde19b43fa33…
entry_sha256: d8bed0b35d91f88473948faddf1147ba64dfc9bc70ae27301ab918a7b573d69e

Read the whole entry: the signed receipt · the change log.

What a Watch receipt looks like: facts at a stated time, not advice.

Details everything else about this product

Watch the agents your agent depends on

Every agent calls other agents and MCP servers, and any of them can change its tools, schemas, sign-in or prices after you approved it. GAIP already reads the public ones about daily and keeps a dated, hash-chained record of what each one published. Watch turns that record into a check your own pipeline can run: has anything my agent depends on changed since I last looked, and is it the kind of change I have to act on?

Free, no account, no email: give it URLs and a date.
Facts with receipts, never a score or a verdict.
Runs where you build: a GitHub Action, a webhook, a feed.

In short

What it is: A check your build or agent runs: has anything it depends on (an agent, an MCP server, an API) changed its tools, schemas, sign-in or prices since you last looked, from GAIP's dated record.
What to do first: Call GET /v1/free/watch/check?urls=<the URLs you depend on> (the last seven days, or add since=YYYY-MM-DD), or add the GAIP Watch GitHub Action to a workflow. No account or key.
What the answer looks like: Each URL with the kinds of change recorded since the date, the newest changes with a receipt link each, any notice about it, and one breaking flag across them all.
What it does not say: GAIP does not say whether a change breaks your integration; it lists what each server published and when it changed.

One of GAIP's three doors; every question GAIP answers is on what GAIP is and in the record.

Three ways to use it

1. In your build (GitHub Action). Add gaip-watch to a workflow with the URLs your agent depends on. It calls this check and fails the job when a breaking change was recorded since the last run, with the receipt links in the log.

- uses: tjcgraham-rgb/gaip-agents/watch@main
  with:
    urls: |
      https://mcp.example.com/mcp
      https://agent.example.org/.well-known/agent-card.json
    since: 7d
    capture-unknown: true

2. From anything that can make an HTTPS request.

GET https://www.gaipagents.com/v1/free/watch/check?urls=https://mcp.example.com/mcp,https://agent.example.org/.well-known/agent-card.json&since=2026-10-01

The answer lists each target with the change classes recorded since the date, the newest change rows with their receipt links, and one breaking flag across all targets. Send X-GAIP-Continuity with the handle from an earlier answer to link your checks.

3. As a feed. Each watched target has an Atom and JSON feed of its dated changes at /v1/free/changes/feed.atom?url=<target url>; put it in any feed reader or alerting tool.

For providers: show your own record

If you run an agent or MCP server, you can show the dated record GAIP keeps of it on your README or docs: a badge that says when GAIP last recorded a change to what you publish, linking to the full change log. It is your own record, attested by an independent reader; it is not a mark of approval, and it says nothing about behaviour.

[![GAIP watch](https://www.gaipagents.com/v1/free/watch/badge.svg?url=https://mcp.example.com/mcp)](https://www.gaipagents.com/v1/free/observatory/lookup?url=https://mcp.example.com/mcp)

The badge reads "no change recorded since <date>" or "change recorded <date>", or "no record" until GAIP has one (save one with capture_unknown above, or the Observatory's capture tool). Operators who do not want their server read at all can opt out at corrections.

What counts as breaking

A change class a dependent client usually has to act on: a tool removed, an input schema changed, authentication changed, a price changed, or a tool changed beyond what GAIP stores. Tools added, descriptions, annotations and version strings are recorded but not flagged. The labels come from GAIP's capability record and are facts about what the server published, not an assessment of the server; an unchanged record says nothing about behaviour.

Notices

Each target in a check also lists any active notice GAIP has recorded about it: the Official MCP Registry marking the server deleted or deprecated, the operator's own withdrawal or advisory (published at /.well-known/gaip-notices.json on its host, read weekly), or an OSV advisory for the server's declared package. Every notice names its issuer and carries the issuer's words and the operator's reply verbatim; GAIP originates none of them. Query the record directly: GET /v1/free/notices?urls=<endpoint>&since=YYYY-MM-DD; public index at /.well-known/gaip-notices.json.

What GAIP does and does not do

GAIP reads a server's published card or MCP tool list as any client would (robots.txt respected, never a tool call), stores hashes and a short excerpt, and signs each day's chain head through a public transparency log. It publishes no rankings, scores or verdicts, and sends adverse facts about a named server only to the caller who asked. A target GAIP has no record of cannot be said to have changed; pass capture_unknown to save a first dated record now. Method: Agent Observatory. Corrections and opt-out: corrections. Privacy (draft) and terms (draft).