# Halowerk MCP Tool List Notification Refresh

> Halowerk MCP Tool List Notification Refresh is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-20).

Reconciles declared catalogue changes against the local client's notification and update state for MCP tool lists

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/integration/mcp-tool-list-notification-refresh?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-mcp-tool-list-notification-refresh-1f603364
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Y7IjFBM6tczkItJVoeKbh

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 halowerk-mcp-tool-list-notification-refresh-1f603364 -d '<json body>'
```

Example prompt: Check whether the latest catalogue events for my MCP tool list require a client notification or a refresh before the next call — list_changed_capability is true, notification_required_on_change is true, and refresh_required_before_call is true.

## When to prefer this

Use this endpoint when an AI agent needs to verify whether its local MCP tool list is synchronized with declared catalogue changes before making downstream tool calls, or when determining whether a notification event should be triggered due to a catalogue update. Prefer this over manual state tracking when operating in dynamic MCP environments where tool lists change frequently.

## Known failure modes

- Missing required artifact fields (catalogue_events, list_changed_capability, notification_required_on_change, refresh_required_before_call) cause validation errors
- Malformed or empty catalogue_events may result in inconclusive reconciliation
- Payment failure (x402) prevents endpoint access
- Stale or mismatched client state may yield unexpected refresh/notification outcomes

## How this service works

Deklarierte Katalogaenderungen mit Benachrichtigungs- und Aktualisierungsstand des lokalen Clients abgleichen.

## Output

Returns a reconciliation result indicating whether the local client's notification state and update status are aligned with declared catalogue changes, including whether a refresh or notification action is required.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "artifact": {
   "type": "object",
   "required": [
    "catalogue_events",
    "list_changed_capability",
    "notification_required_on_change",
    "refresh_required_before_call"
   ],
   "properties": {
    "catalogue_events": {},
    "list_changed_capability": {},
    "refresh_required_before_call": {},
    "notification_required_on_change": {}
   },
   "additionalProperties": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-mcp-tool-list-notification-refresh-1f603364/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)