Skip to content

Push Drop Stick: force-free dog training MCP server

com.pushdropstick/planspushdropstick.comstreamable-httpv1.1.0Scanned

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

9 tools: 2 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 2 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Push Drop Stick: force-free dog training MCP server can do

The Push Drop Stick: force-free dog training MCP server is published by pushdropstick.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (2 tools: about_push_drop_stick and how_to_train), but cannot delete data. 7 tools only read.

1 tool reads private data (fetch); 1 tool brings in text other people can write (list_plans).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 2Claude Code: ask
  • about_push_drop_stickFacts 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, subs…1 finding

    Why it is in this group

    • The name "about_push_drop_stick" says "push": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "about_push_drop_stick" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "about_push_drop_stick" says "push": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: About Push Drop Stick
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • how_to_trainHow 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: The push/drop/stick method
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 7Show 7 read-only tools
  • fetchThe 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 ("a…Reads private dataNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Fetch a document
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_planThe 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 …No findings

    Why it is in this group

    • The name "get_plan" says "get": a word for reading.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Read a training plan
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_plansBrowse the public plan library by group (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "list_plans" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Browse the plan library
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • read_handbookRead the Handbook.No findings

    Why it is in this group

    • The name "read_handbook" says "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read the Handbook
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_handbookSearch the Push Drop Stick Handbook: 140+ short articles by a certified force-free trainer (Allison Wells, CTC).No findings

    Why it is in this group

    • The name "search_handbook" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the Handbook
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_plansFind step-by-step, force-free training plans for a behavior, problem or command, e.g.No findings

    Why it is in this group

    • The name "search_plans" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search training plans
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:20 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://pushdropstick.com/mcp/public: tools/list returned 9 tools to an anonymous client, including about_push_drop_stick (write), how_to_train (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "about_push_drop_stick" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "about_push_drop_stick" says "push": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__plans__search_plans",
      "mcp__plans__get_plan",
      "mcp__plans__list_plans",
      "mcp__plans__search_handbook",
      "mcp__plans__read_handbook",
      "mcp__plans__search",
      "mcp__plans__fetch"
    ],
    "ask": [
      "mcp__plans__about_push_drop_stick",
      "mcp__plans__how_to_train"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as plans. Review it before you use it.

Capability tags behind 2 rules
  • mcp__plans__list_plans untrusted-input
  • mcp__plans__fetch private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.pushdropstick/plans/verify?hash=b826eb0dbd8b43c6818f5c9e15e8dbdd9d3b1c7f88be0328f441184a7236e12f" | jq -e '.changed == false'

Pinned hash b826eb0dbd8b, from Nov 13, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.pushdropstick/plans/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.pushdropstick/plans
[![Anlyon Radar](https://radar.anlyon.com/badge/com.pushdropstick/plans.svg)](https://radar.anlyon.com/servers/com.pushdropstick/plans)

Source: MCP Registry. Synced Nov 13, 2026, 18:17 UTC.

Push Drop Stick: force-free dog training MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 9 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Push Drop Stick: force-free dog training MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Push Drop Stick: force-free dog training MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

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

9 tools: 2 write, 7 read. about_push_drop_stick, how_to_train, search_plans, get_plan, list_plans, search_handbook, read_handbook, search and 1 more.

Does the Push Drop Stick: force-free dog training MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Push Drop Stick: force-free dog training MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Push Drop Stick: force-free dog training MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.