PulseWatch public knowledge

top.pulsewatchPublished by pulsewatch.topOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote MCP endpoint that exposes PulseWatch's public offers and monitoring guides to an assistant.

What you can do
PulseWatch public knowledge is a remote MCP server reachable at a hosted endpoint. According to its registry description, it serves public PulseWatch offers and monitoring guides. It is explicitly described as containing no private customer data and no monitor controls, so it is a read-only public information source rather than a management interface.
When to use it
Worth adding when an assistant needs to answer questions about PulseWatch's publicly listed offers or its monitoring guides. It is not intended for managing monitors or accessing customer-specific data.
Requirements
A remote streamable HTTP MCP endpoint; no package installation is needed. The manifest declares no authentication, no environment variables and no headers, so no credentials appear to be required. Network access to the hosted endpoint is necessary.
Before you install
The manifest declares no authentication and no credentials, and the description states the server holds no private customer data and no monitor controls. Because it is a third-party hosted endpoint, requests and any query content are sent to that provider; avoid sending sensitive information in queries.

Installation

In SourceWeft

  1. Open PulseWatch public knowledge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/top.pulsewatch%2Fpublic-knowledge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

3

list_offers

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

Parameterslocale

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.

Parameterslimitqueryrequiredlocale

read_knowledge

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

Parametersidrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.