# Watch MCP Server Versions and Endpoints

**Use case:** 

Get the current version, packages, remote endpoints, transports and declared auth headers of MCP servers from the official MCP Registry on every run. Replace the sample names with exact Registry names (namespace/name). With changesOnly off, every run writes the full normalized snapshot of each server, so the Dataset can feed an inventory or allowlist export.

## Input

```json
{
  "mode": "watchlist",
  "monitorKey": "inventory",
  "servers": [
    "io.github.github/github-mcp-server",
    "io.github.microsoft/playwright-mcp",
    "com.stripe/mcp"
  ],
  "changesOnly": false,
  "baselineMode": "emitSnapshot",
  "includeDeleted": true,
  "maxResults": 1000,
  "lookbackDays": 1
}
```

## Output

```json
{
  "record_type": {
    "label": "Record type",
    "format": "string"
  },
  "server_name": {
    "label": "Server name",
    "format": "string"
  },
  "status": {
    "label": "Status",
    "format": "string"
  },
  "registry_status": {
    "label": "Registry status",
    "format": "string"
  },
  "version": {
    "label": "Version",
    "format": "string"
  },
  "change_types": {
    "label": "Change types",
    "format": "array"
  },
  "server": {
    "label": "Server snapshot",
    "format": "object"
  },
  "source_url": {
    "label": "Source URL",
    "format": "string"
  },
  "scraped_at": {
    "label": "Observed at",
    "format": "string"
  },
  "error": {
    "label": "Error",
    "format": "object"
  }
}
```

## About this Actor

This example demonstrates how to use [MCP Server Governance & Change Monitor](https://apify.com/automa-flow/mcp-server-governance-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/automa-flow/mcp-server-governance-monitor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
This Task's input is already configured above — use it as-is rather than inventing a new one.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/automa-flow/mcp-server-governance-monitor.md

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).