Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Pushary

REMOTE · PUSHARY.COM · 2 COMPONENTS · SCANNED AUG 3

Notify me when my agent needs me: approve from my phone, answer questions away from the terminal.

Available components

remote · pushary.com 76 remote · pushary.com 22
0 this week 22 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · pushary.com

# add to Claude Code
claude mcp add --transport http pushary-pushary https://pushary.com/api/mcp/sse
# ~/.codex/config.toml
[mcp_servers.pushary-pushary]
url = "https://pushary.com/api/mcp/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pushary-pushary": {
      "type": "remote",
      "url": "https://pushary.com/api/mcp/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pushary-pushary --url https://pushary.com/api/mcp/sse --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  pushary-pushary:
    url: "https://pushary.com/api/mcp/sse"
// mcp.json
{
  "mcpServers": {
    "pushary-pushary": {
      "type": "http",
      "url": "https://pushary.com/api/mcp/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 0
    • Transport: unverified → fail ▼ security
    • Authorization: fail → unverified ▼ security
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 22

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://pushary.com/api/mcp/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.pushary.com CN=YR2,O=Let's Encrypt,C=US 26 Jun 2026 24 Sept 2026 RSA 2048 SHA256-RSA 54a92c50c2df64b64318504c26cdcf5e969
SANs: *.pushary.com, pushary.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of pushary.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
pushary.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 405
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
Transports 2 probes
Transport URL Outcome Status Location
sse https://pushary.com/api/mcp/sse Unreachable
http (plaintext) http://pushary.com/api/mcp/sse HTTPS enforced 308 https://pushary.com/api/mcp/sse
MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

No tool schema has been captured from this endpoint yet.