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

Push Drop Stick: force-free dog training

REMOTE · PUSHDROPSTICK.COM

Force-free dog training: step-by-step plans, the Handbook and product facts. Read-only.

+3 this week 75 Trust /100

Last scanned (15 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1380 tokens (~153/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (22% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "about_push_drop_stick" implies "drop" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 71

    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 21 Nov 2026 · Probed https://pushdropstick.com/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pushdropstick.com CN=WE1,O=Google Trust Services,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA256 f2e12b1391b1ec020e2f116e0d5749d7
SANs: pushdropstick.com, *.pushdropstick.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pushdropstick.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
pushdropstick.com. No DS 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 200
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pushdropstick.com/mcp/public Verified 200
http (plaintext) http://pushdropstick.com/mcp/public HTTPS enforced 301 https://pushdropstick.com/mcp/public
MCP tools · 9 exposed · ~1,130 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
about_push_drop_stick ~110

Facts about Push Drop Stick itself: what the app is, who wrote its training content, the force-free method, platforms (iPhone, Apple Watch, web, Android status), what is free, subscription prices, what Coach (the AI trainer) is and where it stops, how training data is handled, and links. Use for questions about the product, e.g. "Is Push Drop Stick free?", "Is it on Android?", "What is Coach?". Quote this rather than guessing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fetch ~81

The full text of one document from `search`, as markdown: a training plan (id "plan:<ref>") with every step, a Handbook entry or section ("handbook:<id>"), or the product facts ("about"). Returns {id, title, text, url, metadata}; cite `url`.

NameTypeReqDescription
idstringyesAn id from search.
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_plan ~121

The full content of one public plan: description, equipment, cues, and every step with setup, instructions, success/failure criteria, set size and the rule for moving on, plus the push/drop/stick execution rules. Pass the `plan` ref from search_plans or list_plans. Link the user to the returned `url`; plan text may be quoted with attribution to its `author`.

NameTypeReqDescription
planstringyesThe `plan` ref from search_plans or list_plans: a slug (library plan) or "handle/slug".

No output schema declared.

No examples provided.

how_to_train ~39

How to read and execute a Push Drop Stick plan: the force-free marker-training philosophy and the push/drop/stick set mechanics that every plan shares.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_plans ~108

Browse the public plan library by group (e.g. Basic Manners, Grooming & Handling, Positions, Tricks). Use when the user wants to see what can be trained or what a category holds, rather than an answer to one problem. Without `group`: every group with its plans' names, refs and urls. With `group`: that group's plans with summaries and step counts.

NameTypeReqDescription
groupstring–Optional group name, as list_plans (no arguments) returns it.

No output schema declared.

No examples provided.

read_handbook ~133

Read the Handbook. `id` = an entry id from search_handbook (e.g. "threshold", "geartoavoid", "faqtreats") → the whole entry as markdown, with its canonical url and the entries it links to. `id` = a section slug (e.g. "fear-emotion", "gear", "faq") → the section's introduction and its entries. No `id` → the table of contents: every section and entry with urls.

NameTypeReqDescription
idstring–An entry id or title, or a section slug. Omit for the table of contents.

No output schema declared.

No examples provided.

search ~108

One search across the whole site: training plans, Handbook articles, and (for questions about the product) the facts page. Returns `results` [{id, title, url, text}]; pass an `id` to fetch for the full document. When you already know you want plans or Handbook articles, search_plans or search_handbook give richer results.

NameTypeReqDescription
limitinteger–Max results (1-25).
querystringyesWhat to look for, in plain words.
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_handbook ~214

Search the Push Drop Stick Handbook: 140+ short articles by a certified force-free trainer (Allison Wells, CTC). Covers how dogs learn (positive reinforcement, punishment, extinction, classical conditioning), fear and reactivity (threshold, trigger stacking, desensitization and counter-conditioning, dogs who wore shock or prong collars), teaching techniques (markers, lures, shaping, duration/distance/distraction), gear (harnesses, head halters, muzzles, why not prong or shock collars), a FAQ (treats, where and how often to train), and how the app and Coach work. Use for "what is", "why" and "should I" questions. Returns entry ids, the most relevant paragraph and canonical urls; read_handbook returns a whole entry.

NameTypeReqDescription
limitinteger–Max results (1-25).
querystringyesA question or topic, in plain words.
sectionstring–Optional: search only this section.

No output schema declared.

No examples provided.

search_plans ~216

Find step-by-step, force-free training plans for a behavior, problem or command, e.g. "pulling on leash", "crate training", "come when called", "nail trims", "jumping on guests". BM25 ranked. Returns each plan's `plan` ref, summary, step count, author and canonical `url` to recommend. Next: get_plan for the full steps. For concepts or advice ("what is threshold", "are prong collars ok") use search_handbook instead.

NameTypeReqDescription
languagestring–Optional filter: only plans written in this language (ISO 639-1 code, e.g. "en", "it"). Most plans are "en".
limitinteger–Max results (1-25).
querystringyesWhat to train, or the problem to solve, in plain words.
speciesstring–Optional filter: only plans written for this species, lowercase singular ("dog", "cat", ...). Most plans are "dog".

No output schema declared.

No examples provided.

Install

How do I install the Push Drop Stick: force-free dog training MCP server?

Push Drop Stick: force-free dog training is a hosted endpoint at https://pushdropstick.com/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pushdropstick.com

# add to Claude Code
claude mcp add --transport http com-pushdropstick-plans 'https://pushdropstick.com/mcp/public'
Common questions

What is the Push Drop Stick: force-free dog training MCP server?

Push Drop Stick: force-free dog training is an MCP server listed in the public MCP registry as com.pushdropstick/plans. Force-free dog training: step-by-step plans, the Handbook and product facts. Read-only. This page covers its hosted endpoint (https://pushdropstick.com/mcp/public).

Is the Push Drop Stick: force-free dog training MCP server safe to use?

Push Drop Stick: force-free dog training scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Push Drop Stick: force-free dog training MCP server expose?

Push Drop Stick: force-free dog training exposes 9 tools: search_plans, get_plan, list_plans, search_handbook, read_handbook, and 4 more. Their descriptions and schemas cost roughly 1,130 tokens of context every time the server is loaded.

Does the Push Drop Stick: force-free dog training MCP server require authentication?

No. We connected to Push Drop Stick: force-free dog training without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Push Drop Stick: force-free dog training MCP server still maintained?

Push Drop Stick: force-free dog training is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Push Drop Stick: force-free dog training MCP server?

VerifyMCP ran 13 checks on Push Drop Stick: force-free dog training, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.