Other · Remote MCP server

PulseGate

Identifiers PulseGate holds for a software project, and where each one came from.

Visit PulseGate's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
ai.pulsegate/provenance
Version
0.1.0
Status
Active
Category
other
Transport
Streamable HTTP
Published
2026-10-02
Updated
2026-10-02
Publisher
ai.pulsegate
Namespace
Namespace verified by the MCP Registry via the domain pulsegate.ai · how
Website
www.pulsegate.ai/developers
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://www.pulsegate.ai/api/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
pulsegate-provenance 0.1.0 · protocol 2025-06-18
Tools discovered
2: lookup_project, list_identifier_platforms
Checked on
2026-10-05

How the live check works

How to connect PulseGate

PulseGate is a remote MCP server: there is nothing to install. Its endpoint is https://www.pulsegate.ai/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
Pulse - heartbeat & status monitor for AI agentsYour agent pings once per run; get a public up/late/down status page. Auto-creates checks. One call.Remote · HTTPpulse.notdown-app.workers.dev
Pulse FetchMCP server for fetching web resources with content extraction and anti-bot bypass.Local · stdionpm: @pulsemcp/pulse-fetch
Pulse MCPFree, agent-first social-post metrics - a post URL in, views/likes/comments out.Local · stdionpm: pulse-mcp
Pulse SubregistryMCP server providing access to the PulseMCP Sub-Registry for browsing and discovering MCP servers.Local · stdionpm: @pulsemcp/pulse-subregistry
Pumperly MCPMCP server for Pumperly - query fuel prices, find stations, and plan routes.Local · stdionpm: pumperly-mcp
PuppetflowBuild, run, monitor, and control Puppetflow browser automations from AI clients.Remote · HTTPx
purchaseiq.ioPre-purchase trust checks for AI agents: recalls, scam signals, proceed/caution/avoid verdict.Remote · HTTPLive check: ✓ handshakepurchaseiq.io
PursersCoordinate AI-agent work on a local-first, owner-controlled MCP board.Local · HTTP, stdioPyPI: pursers-central