# MCP Annotation Consistency Detector

> MCP Annotation Consistency Detector is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-19).

Detects contradictory MCP tool annotation declarations where a tool is simultaneously marked as both read-only and destructive

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/mcp/mcp-annotation-consistency?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-annotation-consistency-detector-4d4377a7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1399XQwufQOqUQjOo-R7e

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-annotation-consistency-detector-4d4377a7 -d '<json body>'
```

Example prompt: Check this list of MCP tools for annotation contradictions — specifically find any tools where both readOnlyHint and destructiveHint are declared true at the same time, and give me evidence of those conflicts.

## When to prefer this

Choose this endpoint when you need to specifically detect the contradiction between readOnlyHint and destructiveHint in MCP tool annotations, particularly during tool catalog audits, CI/CD pipeline validation, or debugging agent routing issues caused by inconsistent tool metadata. It is purpose-built for MCP annotation consistency checking rather than general schema validation.

## Known failure modes

- Missing required 'tools' array in artifact returns validation error
- Tools missing required annotation fields (readOnlyHint or destructiveHint) may be skipped or cause schema errors
- Exceeding 2048 tool items in the array triggers a limit error
- Empty tools array returns no contradictions found
- Malformed annotation objects may cause parsing failures

## How this service works

An agent that catalogs MCP tools needs evidence of contradictory explicit read-only and destructive annotation declarations.

## Output

Returns evidence of MCP tools whose annotations declare both readOnlyHint=true and destructiveHint=true simultaneously, including the specific conflicting tool records and counts of such contradictions found within the submitted artifact.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "artifact": {
   "type": "object",
   "required": [
    "tools"
   ],
   "properties": {
    "tools": {
     "type": "array",
     "items": {
      "type": "object",
      "required": [
       "annotations"
      ],
      "properties": {
       "annotations": {
        "type": "object",
        "required": [
         "readOnlyHint",
         "destructiveHint"
        ],
        "properties": {
         "readOnlyHint": {
          "type": "boolean"
         },
         "destructiveHint": {
          "type": "boolean"
         }
        },
        "additionalProperties": true
       }
      },
      "additionalProperties": true
     },
     "maxItems": 2048
    }
   },
   "additionalProperties": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcp-annotation-consistency-detector-4d4377a7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from detect.halowerk.com](https://www.zero.xyz/host/detect.halowerk.com/llms.txt)