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)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Pushary) · how
- 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) |
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.
- Endpoint
https://pushary.com/api/mcp/mcp(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- Pushary 1.0.0 · protocol 2025-06-18
- Tools discovered
- 5:
send_notification,ask_user,propose_scope,wait_for_answer,cancel_question - Checked on
- 2026-10-05
- Endpoint
https://pushary.com/api/mcp/sse(SSE)- Reachable
- Yes (HTTP 200)
- SSE stream
- Opened and named its message endpoint (not used further)
- Checked on
- 2026-10-05
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; 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
| Server | Runs |
|---|---|
| Pumperly MCPMCP server for Pumperly - query fuel prices, find stations, and plan routes. | Local · stdio |
| 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 · HTTPLive check: ✓ handshake |
| PursersCoordinate AI-agent work on a local-first, owner-controlled MCP board. | Local · HTTP, stdio |
| Pusher ChannelsTrigger events, query channels, and manage realtime messaging on Pusher Channels. | Local · 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 |
| puter.comPuter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more. | Remote · HTTPLive check: sign-in required |