# MCP Manifest Drift Check

> MCP Manifest Drift Check is a paid API for AI agents from attester.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Checks whether an MCP (Model Context Protocol) server's live manifest has drifted from its expected or previously recorded state

## Facts

- Endpoint: POST https://attester.dev/v2/mcp/check
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-manifest-drift-check-74f7069f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rXm_PnqRYOR47m9Y81T6m

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability mcp-manifest-drift-check-74f7069f -d '<json body>'
```

Example prompt: Check if the MCP server at https://myserver.example.com has drifted from its last known manifest — I want to know if any tools or capabilities have been added, removed, or changed.

## When to prefer this

Use this endpoint when you need to programmatically verify that an MCP server's manifest has not changed unexpectedly — especially in CI/CD pipelines, agent health checks, or security audits where unauthorized drift in tool definitions could break downstream agents or introduce risk. Prefer this over manual inspection or generic HTTP diffing tools because it understands MCP manifest semantics.

## Known failure modes

- MCP server URL is unreachable or returns an error — endpoint may return a connectivity failure response
- Manifest cannot be fetched or parsed — returns parse error
- No baseline manifest provided for comparison — may return an error requiring prior snapshot
- Service returns 402 if payment header is missing or insufficient
- Rate limiting or timeout if the target MCP server is slow to respond

## How this service works

MCP manifest drift check (use POST; metadata on POST).

## Output

Returns a structured result indicating whether the MCP server's current manifest has drifted from the expected or baseline state, including details about what specifically changed (tools added, removed, or modified), a drift status flag, and any relevant metadata about the comparison.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "server_url"
     ],
     "properties": {
      "since": {
       "type": [
        "string",
        "null"
       ],
       "description": "ISO date or 64-char manifest sha256; empty = latest pin"
      },
      "server_url": {
       "type": "string",
       "description": "Remote streamable-http MCP server URL"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcp-manifest-drift-check-74f7069f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from attester.dev](https://www.zero.xyz/host/attester.dev/llms.txt)