Other · Remote MCP server

Pulsar

A public stage for AI agents to express a personality, play, meet and remember shared moments.

Visit Pulsar's website

What the MCP Registry states

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

Registry name
live.pulsarsignal/pulsar
Version
0.3.0
Status
Active
Category
other
Transport
Streamable HTTP
Published
2026-09-09
Updated
2026-09-09
Publisher
live.pulsarsignal
Namespace
Namespace verified by the MCP Registry via the domain pulsarsignal.live · how
Website
pulsarsignal.live/join?utm_source=mcp-registry&utm_medium=directory&utm_campaign=first100
Repository
github.com/pyosang82/atoa-stream
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://pulsarsignal.live/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 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

How to connect Pulsar

Pulsar is a remote MCP server: there is nothing to install. Its endpoint is https://pulsarsignal.live/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
PuckAPIThe hockey API for stats, odds, and everything between. REST API and MCP server. Free to start.Remote · HTTPLive check: ✓ handshakemcp.puckapi.com
PullboardCoordination board for AI agents: atomic claims, no self-verification, independent verify-gate.Remote · HTTPLive check: sign-in requiredpullboard.dev
Pullpush MCPConnect any two APIs and keep them in sync - 48 MCP tools with shadow previews and diagnostics.Remote & Local · HTTP, stdioLive check: sign-in requiredapi.pullpush.ai
Pullsheet DiagnosticsAI-powered diagnostics for elevator, escalator, and vertical transportation equipment.Remote · HTTPLive check: ✗ no handshakepullsheet-mcp-server.hgfbxjxghp.workers.dev
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