Data · Remote MCP server
Agent Push Kit
Send, search, and manage notifications, accounts, and push preferences.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.JustinBStrong/agent-push-kit- Version
- 0.1.1
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- JustinBStrong (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/JustinBStrong) · how
- Website
- agentpushkit.com/docs/mcp
- Repository
- github.com/JustinBStrong/agent-push-kit-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.chatdna.co/agent-push-kit/v1/mcp | Authorization |
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
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | agent-push-kit-mcp | 0.1.1 | stdio |
How to connect Agent Push Kit
Agent Push Kit is a remote MCP server: there is nothing to install. Its endpoint is https://api.chatdna.co/agent-push-kit/v1/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.
The registry entry declares an HTTP header for the connection: Authorization. clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: agent-push-kit-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y agent-push-kit-mcp@0.1.1. It reads these environment variables: AGENT_PUSH_KIT_TOKEN (required, secret) and AGENT_PUSH_KIT_API_BASE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agent-push-kit": {
"command": "npx",
"args": [
"-y",
"agent-push-kit-mcp@0.1.1"
],
"env": {
"AGENT_PUSH_KIT_TOKEN": "<secret>",
"AGENT_PUSH_KIT_API_BASE": "<value>"
}
}
}
}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 data servers
| Server | Runs |
|---|---|
| Agent KnowledgeCross-session memory for AI agents - knowledge graph, scoring, semantic search. | Local · stdio |
| Agent ModuleDeterministic compliance and vertical knowledge bases for autonomous agents. Free 24hr trial. | Remote · HTTPLive check: ✓ handshake |
| Agent ObservatoryLive census of AI agents: prove you can reason (reverse CAPTCHA), check in, talk to other agents. | Remote · HTTPLive check: ✓ handshake |
| Agent OnlySearch and exchange troubleshooting knowledge across persistent AI-agent identities. | Local · stdio |
| Agent RadarSearch, inspect, recommend, and explain rated AI tools through Agent Radar. | Remote · HTTPLive check: ✓ handshake |
| Agent Revenue NetworkPaid deterministic data-quality and execution-verification tools for AI agents. | Remote · HTTPLive check: ✓ handshake |
| Agent Search MCPFree-first Chinese and English web search MCP using zero-key sources and inspectable evidence. | Local · stdio |
| Agent Search ProLive web search and research synthesis for agents, with free samples and x402 USDC payments. | Remote · HTTPLive check: ✗ no handshake |