# PulseWatch public knowledge (remote · pulsewatch.top)

Public PulseWatch offers and monitoring guides. No private customer data or monitor controls.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `pulsewatch.top`: 68/100 (this document), [markdown](https://verifymcp.io/servers/top-pulsewatch-public-knowledge/pulsewatch.md), [page](https://verifymcp.io/servers/top-pulsewatch-public-knowledge/pulsewatch)

## Channel facts

- Endpoint: `https://pulsewatch.top/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 39/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 187 tokens (~31/item across 6 items; 3 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the PulseWatch public knowledge MCP server?

PulseWatch public knowledge is a hosted endpoint at https://pulsewatch.top/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http top-pulsewatch-public-knowledge 'https://pulsewatch.top/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "top-pulsewatch-public-knowledge": {
      "url": "https://pulsewatch.top/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "top-pulsewatch-public-knowledge": {
      "type": "http",
      "url": "https://pulsewatch.top/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.top-pulsewatch-public-knowledge]
url = "https://pulsewatch.top/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "top-pulsewatch-public-knowledge": {
      "type": "remote",
      "url": "https://pulsewatch.top/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add top-pulsewatch-public-knowledge --url 'https://pulsewatch.top/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  top-pulsewatch-public-knowledge:
    url: "https://pulsewatch.top/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "top-pulsewatch-public-knowledge": {
      "Transport": "http",
      "Url": "https://pulsewatch.top/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add top-pulsewatch-public-knowledge -t streamable-http -u 'https://pulsewatch.top/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "top-pulsewatch-public-knowledge": {
      "type": "http",
      "url": "https://pulsewatch.top/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `list_offers` (~40 tokens)

Read the three public service packages, prices, scope, conditions and written enquiry process. Not live capacity or a purchase.

Input parameters:

- `locale` (string)

Output parameters:

- `revision` (string)
- `sources` (array)

### `search_knowledge` (~69 tokens)

Find public PulseWatch sources by keywords in EN or HR. Returns source URLs and excerpts, not generated advice. Try concise terms such as pilot, pricing, cijene or tjedni brief.

Input parameters:

- `limit` (integer)
- `locale` (string)
- `query` (string, required)

Output parameters:

- `revision` (string)
- `sources` (array)

### `read_knowledge` (~41 tokens)

Read an exact public document ID returned by search_knowledge. Only catalogue IDs are accepted; no URL fetching or file access.

Input parameters:

- `id` (string, required)

Output parameters:

- `revision` (string)
- `sources` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/top-pulsewatch-public-knowledge/pulsewatch#diagnostics

## Score history

- 2026-09-28: 68
- 2026-09-27: 68
- 2026-09-26: 67
- 2026-09-25: 67
- 2026-09-24: 67
- 2026-09-23: 66
- 2026-09-22: 66
- 2026-09-21: 65
- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 64
- 2026-09-17: 63
- 2026-09-16: 63
- 2026-09-15: 62

## Common questions

### What is the PulseWatch public knowledge MCP server?

PulseWatch public knowledge is an MCP server listed in the public MCP registry as top.pulsewatch/public-knowledge. Public PulseWatch offers and monitoring guides. No private customer data or monitor controls. This page covers its hosted endpoint (https://pulsewatch.top/mcp/).

### Is the PulseWatch public knowledge MCP server safe to use?

PulseWatch public knowledge scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the PulseWatch public knowledge MCP server expose?

PulseWatch public knowledge exposes 3 tools: list_offers, search_knowledge, read_knowledge. Their descriptions and schemas cost roughly 150 tokens of context every time the server is loaded.

### Does the PulseWatch public knowledge MCP server require authentication?

No. We connected to PulseWatch public knowledge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PulseWatch public knowledge MCP server still maintained?

PulseWatch public knowledge is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://pulsewatch.top/mcp/
- Website: https://pulsewatch.top/
- Changelog RSS feed: https://verifymcp.io/servers/top-pulsewatch-public-knowledge/pulsewatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/top-pulsewatch-public-knowledge/pulsewatch.json
- HTML version of this page: https://verifymcp.io/servers/top-pulsewatch-public-knowledge/pulsewatch