Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/JustinBStrong/agent-push-kit-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/justinbstrong/agent-push-kit-mcp/agent-push-kit)<a href="https://agentmods.dev/mcp/justinbstrong/agent-push-kit-mcp/agent-push-kit"><img src="https://agentmods.dev/badge/mcp/justinbstrong/agent-push-kit-mcp/agent-push-kit.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-push-kit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"agent-push-kit": {
"command": "npx",
"args": [
"-y",
"agent-push-kit-mcp"
],
"env": {
"AGENT_PUSH_KIT_TOKEN": "",
"AGENT_PUSH_KIT_API_BASE": "https://api.chatdna.co/agent-push-kit/v1"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 13 lines scan A f2f300919ed0
agent-push-kit is an MCP server published in the GitHub repository JustinBStrong/agent-push-kit-mcp (0 stars, last pushed 19d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
ntfy-mcp
Publish ntfy notifications, read the message cache, and manage users and topic access. Runs locally from the @ni-c/ntfy-mcp npm package. Needs 9 environment variables to run.
paging-mcp
MCP server "paging-mcp" as configured in adelaidasofia/paging-mcp. Launched with https://github.com/adelaidasofia/paging-mcp/releases/download/v0.1.0/paging-mcp.. Needs 1 environment variable to run.
ntfy-notify
A Python package for sending notifications via the very fabolous ntfy from CLI or Python code with stored credentials. Runs locally from the ntfy-notify Python package.
ntfy-mcp
MCP server "ntfy-mcp" as configured in MahdiHedhli/ntfy-mcp. Runs locally from the ntfy-mcp Python package.
mcp
MCP server that lets AI agents send Blipr push alerts to your phone — your agent can page you. Runs locally from the @blipr/mcp npm package.
raycast
Raycast workflow automation MCP server with 9 tools. Runs locally from the raycast-mcp-server npm package.