Pushinator MCP

Created By
appricosa year ago
Official Pushinator MCP server
Overview

what is Pushinator MCP?

Pushinator MCP is an official server designed to facilitate push notifications using the Model Context Protocol (MCP).

how to use Pushinator MCP?

To use Pushinator MCP, install the necessary dependencies using bun install, build the project with bun run build, and then configure your MCP client with the API token from the Pushinator API tokens page.

key features of Pushinator MCP?

  • Supports push notifications through MCP.
  • Easy installation and setup process.
  • Configurable server settings for integration with clients.

use cases of Pushinator MCP?

  1. Integrating push notifications into web applications.
  2. Managing real-time notifications for mobile apps.
  3. Utilizing MCP for efficient communication between services.

FAQ from Pushinator MCP?

  • What is the purpose of Pushinator MCP?

Pushinator MCP is designed to streamline the process of sending and managing push notifications using the Model Context Protocol.

  • Is there a cost associated with using Pushinator MCP?

Pushinator MCP is free to use, but you may need to manage your API tokens through the Pushinator console.

  • What programming language is Pushinator MCP built with?

Pushinator MCP is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
appricos
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

42 minutes ago