PulseWatch MCP server

Which servers in the official MCP registry are PulseWatch's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to PulseWatch

Whose server it is

Registry nametop.pulsewatch/public-knowledgeverified in the MCP registry

The registry name sits under pulsewatch.top. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools3
Server calls itselfpulsewatch-public-knowledge
Server version1.0.0
Protocol version2025-11-25

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 184 ms.

Tools it offers3 tools · read 2026-10-13

list_offers
Read the three public service packages, prices, scope, conditions and written enquiry process. Not live capacity or a purchase.
search_knowledge
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.
read_knowledge
Read an exact public document ID returned by search_knowledge. Only catalogue IDs are accepted; no URL fetching or file access.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.