# 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.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `pushdropstick.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-pushdropstick-plans/mcp-public.md), [page](https://verifymcp.io/servers/com-pushdropstick-plans/mcp-public)

## Channel facts

- Endpoint: `https://pushdropstick.com/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (22% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-pushdropstick-plans 'https://pushdropstick.com/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "com-pushdropstick-plans": {
      "url": "https://pushdropstick.com/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-pushdropstick-plans": {
      "type": "http",
      "url": "https://pushdropstick.com/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-pushdropstick-plans]
url = "https://pushdropstick.com/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pushdropstick-plans": {
      "type": "remote",
      "url": "https://pushdropstick.com/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pushdropstick-plans --url 'https://pushdropstick.com/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pushdropstick-plans:
    url: "https://pushdropstick.com/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "com-pushdropstick-plans": {
      "Transport": "http",
      "Url": "https://pushdropstick.com/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-pushdropstick-plans -t streamable-http -u 'https://pushdropstick.com/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "com-pushdropstick-plans": {
      "type": "http",
      "url": "https://pushdropstick.com/mcp/public"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 75, +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.

### 2026-11-18 (score 74, +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.

### 2026-11-16 (score 73, +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.

### 2026-11-14 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 71)

First indexed and scored.

## MCP tools (9)

### `search_plans` (~216 tokens)

Search training plans

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.

Input parameters:

- `language` (string): Optional filter: only plans written in this language (ISO 639-1 code, e.g. "en", "it"). Most plans are "en".
- `limit` (integer): Max results (1-25).
- `query` (string, required): What to train, or the problem to solve, in plain words.
- `species` (string): Optional filter: only plans written for this species, lowercase singular ("dog", "cat", ...). Most plans are "dog".

### `get_plan` (~121 tokens)

Read a training plan

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`.

Input parameters:

- `plan` (string, required): The `plan` ref from search_plans or list_plans: a slug (library plan) or "handle/slug".

### `list_plans` (~108 tokens)

Browse the plan library

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.

Input parameters:

- `group` (string): Optional group name, as list_plans (no arguments) returns it.

### `search_handbook` (~214 tokens)

Search the Handbook

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.

Input parameters:

- `limit` (integer): Max results (1-25).
- `query` (string, required): A question or topic, in plain words.
- `section` (string): Optional: search only this section.

### `read_handbook` (~133 tokens)

Read the Handbook

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.

Input parameters:

- `id` (string): An entry id or title, or a section slug. Omit for the table of contents.

### `about_push_drop_stick` (~110 tokens)

About Push Drop Stick

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.

### `how_to_train` (~39 tokens)

The push/drop/stick method

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.

### `search` (~108 tokens)

Search everything

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.

Input parameters:

- `limit` (integer): Max results (1-25).
- `query` (string, required): What to look for, in plain words.

Output parameters:

- `results` (array)

### `fetch` (~81 tokens)

Fetch a document

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`.

Input parameters:

- `id` (string, required): An id from search.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pushdropstick-plans/mcp-public#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72
- 2026-11-14: 72
- 2026-11-13: 71

## 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.

## Links

- Remote endpoint: https://pushdropstick.com/mcp/public
- Website: https://pushdropstick.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-pushdropstick-plans/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pushdropstick-plans/mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-pushdropstick-plans/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/com-pushdropstick-plans/mcp-public
