# MCP Registry Monitor - AI Integrations & Version Changes — workflow

## Choose this tool

AI platform teams maintaining an integration catalog.

<!-- B18-REAL-SAMPLE --> Detect version, package and transport changes before updating an agent integration.

Useful output columns: `title`, `serverName`, `version`, `registryStatus`, `repositoryUrl`, `comparisonStatus`.

## Practical workflow

**Useful output:** A catalog of candidate MCP integrations for an AI platform team, with the declared version, package identifiers and transport types.

1. Start with the small example input on this page and replace its targets with your watchlist. Review the result cap and set an Apify maximum run charge before running.
2. Review the dataset and Run report together. Use `recordId` (the registry server name) as the destination identity, preserving source links and null values.
3. Map `serverName`, `version`, `registryStatus`, `packages`, `transports` and `repositoryUrl` into an integration register. Route version, package or transport changes to an owner for compatibility and security review before connecting the server. Registry presence is a discovery signal, not an approval.

**Repeat safely.** Enable `comparePrevious`, keep the same input scope and `snapshotName`, and run one writer at a time. The first saved comparison establishes history; `new` means first observed in this history, not newly published. Later, `onlyChanges: true` skips unchanged rows. Check SUMMARY for failures, limits and history updates before interpreting zero output. Missing records in a bounded window do not establish deletion.

**Delivery:** Export JSON for nested fields or map selected columns into your own sheet/database. Upsert by the row identity below; retain the run ID and observation time for replay. Scheduling and destination delivery are separate setup steps.

## Check the fit

Official registry search, latest versions only, one page per query. Catalog metadata is not a security assessment or uptime check. Remote servers are never contacted and header values are never collected.

At most ten input values and five hundred saved rows per run. Results requested per query controls a single source page (1–50, default five); there is no pagination. Each input performs one bounded public source request; Requests are paced. Responses are capped at 8 MiB and share the run deadline. No authentication bypass or code execution is performed. HTTP 429 stops further requests. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

## Real output sample

One selected row from a 2026-10-18 run. One saved row, selected scalar columns only. Contact details, patient demographics and long text are omitted. Original values and nulls are preserved.

Run: 4iRO4QUy4v9j3KqP8. Summary status: ok. Incomplete: false.

Historical output from this run; the current example input is a separate starting configuration and may produce different records.

```json
{
  "title": "ai.smithery/Hint-Services-obsidian-github-mcp",
  "serverName": "ai.smithery/Hint-Services-obsidian-github-mcp",
  "version": "0.4.0",
  "registryStatus": "active",
  "repositoryUrl": "https://github.com/Hint-Services/obsidian-github-mcp",
  "comparisonStatus": "not_requested",
  "url": "https://registry.modelcontextprotocol.io/v0.1/servers/ai.smithery%2FHint-Services-obsidian-github-mcp/versions/latest",
  "recordId": "ai.smithery/Hint-Services-obsidian-github-mcp",
  "sourceUrl": "https://registry.modelcontextprotocol.io/v0.1/servers?search=github&limit=5&version=latest",
  "observedAt": "2026-10-18T04:09:57.244Z"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [GitHub Repository Change Monitor - Stars, Forks & Activity](https://mayd-it.com/data-tools/actors/github-repository-change-monitor/)

Track the exact public repository’s metadata, license and activity dates alongside the discovery or release signal.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

A registry entry does not prove endpoint availability or establish a repository/OpenAPI identity. Follow the publisher’s actual links and review identifiers manually.

### [OpenAPI Contract Monitor - Operation & Schema Changes](https://mayd-it.com/data-tools/actors/openapi-operation-change-monitor/)

Inspect changes in an actual published OpenAPI document before assuming an integration’s operations and schemas stayed compatible.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

A registry entry does not prove endpoint availability or establish a repository/OpenAPI identity. Follow the publisher’s actual links and review identifiers manually.
