Other · Remote MCP server
Pushary
The decision layer for AI agents. Your agent asks, a person approves or denies on their phone.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Pushary/pushary- Version
- 1.4.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- Pushary (GitHub)
- Repository
- github.com/Pushary/pushary-skill
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://pushary.com/api/mcp/mcp | Authorization (required, secret) |
| SSE (HTTP + Server-Sent Events) | https://pushary.com/api/mcp/sse | Authorization (required, secret) |
How to connect Pushary
Pushary is a remote MCP server: there is nothing to install. Its endpoint is https://pushary.com/api/mcp/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.
It also lists an endpoint on the older SSE transport https://pushary.com/api/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry, not tested here. 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
| Server | Runs |
|---|---|
| PulseGateIdentifiers PulseGate holds for a software project, and where each one came from. | Remote · HTTP |
| PuppetflowBuild, run, monitor, and control Puppetflow browser automations from AI clients. | Remote · HTTP |
| purchaseiq.ioPre-purchase trust checks for AI agents: recalls, scam signals, proceed/caution/avoid verdict. | Remote · HTTP |
| PursersCoordinate AI-agent work on a local-first, owner-controlled MCP board. | Local · HTTP, stdio |
| Pusher MCPQuery the Pusher HTTP API: channels, channel details, channel users. | Local · stdio |
| pushinpay.com.brMCP oficial da PushinPay: cobranças PIX, consulta de transações e saldo via IA. | Local · stdio |
| Putput MCPFile uploads for AI agents. Upload, list, and manage files. No signup required. | Remote & Local · HTTP, stdio |
| PXL8 verified fight recordsVerified fight records for AI assistants: look up a fighter or fight card, cite the pxl8.io page. | Remote · HTTP |