pushdropstick-plans

endpoint

https://pushdropstick.com/mcp/public

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is pushdropstick-plans live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is pushdropstick-plans free to use?

Yes — the hub reached it with no key and no payment.

What tools does pushdropstick-plans have?

9 tools: search_plans, get_plan, list_plans, search_handbook, read_handbook, about_push_drop_stick, fetch, how_to_train, ….

Is pushdropstick-plans safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• how_to_train open 1h ago

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• search open 1h ago

  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.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 10,
        "maximum": 25,
        "minimum": 1,
        "description": "Max results (1-25)."
      },
      "query": {
        "type": "string",
        "description": "What to look for, in plain words."
      }
    }
  }

  arguments 19 lines copy
• search_plans unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 8,
        "maximum": 25,
        "minimum": 1,
        "description": "Max results (1-25)."
      },
      "query": {
        "type": "string",
        "description": "What to train, or the problem to solve, in plain words."
      },
      "species": {
        "type": "string",
        "description": "Optional filter: only plans written for this species, lowercase singular (\"dog\", \"cat\", ...). Most plans are \"dog\"."
      },
      "language": {
        "type": "string",
        "description": "Optional filter: only plans written in this language (ISO 639-1 code, e.g. \"en\", \"it\"). Most plans are \"en\"."
      }
    }
  }

  arguments 27 lines copy
• get_plan unknown never probed

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

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "plan"
    ],
    "properties": {
      "plan": {
        "type": "string",
        "description": "The `plan` ref from search_plans or list_plans: a slug (library plan) or \"handle/slug\"."
      }
    }
  }

  arguments 12 lines copy
• list_plans unknown never probed

  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.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "group": {
        "type": "string",
        "description": "Optional group name, as list_plans (no arguments) returns it."
      }
    }
  }

  arguments 9 lines copy
• search_handbook unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 6,
        "maximum": 25,
        "minimum": 1,
        "description": "Max results (1-25)."
      },
      "query": {
        "type": "string",
        "description": "A question or topic, in plain words."
      },
      "section": {
        "enum": [
          "purpose",
          "faq",
          "learning-science",
          "fear-emotion",
          "how-the-app-works",
          "using-the-player",
          "teaching-techniques",
          "gear",
          "coach",
          "your-devices",
          "training-with-coach",
          "writing-plans"
        ],
        "type": "string",
        "description": "Optional: search only this section."
      }
    }
  }

  arguments 37 lines copy
• read_handbook unknown never probed

  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.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "id": {
        "type": "string",
        "description": "An entry id or title, or a section slug. Omit for the table of contents."
      }
    }
  }

  arguments 9 lines copy
• about_push_drop_stick unknown never probed

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• fetch unknown 1h ago

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

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "An id from search."
      }
    }
  }

  arguments 12 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.