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.

io.github.Gunsmith-Academy/woody-mcp

PYPI · WOODY-MCP · SCANNED SEP 21

Woody, the AI firearms expert. Verified specs, legal lookups, and knowledge base.

Available components

−15 this week 68 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 494 tokens (~98/item across 5 items; 3 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Install

How do I install the io.github.Gunsmith-Academy/woody-mcp server?

io.github.Gunsmith-Academy/woody-mcp runs locally as a PyPI package, launched with uvx woody-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · woody-mcp

# add to Claude Code
claude mcp add gunsmith-academy-woody-mcp -- uvx woody-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "gunsmith-academy-woody-mcp": {
      "command": "uvx",
      "args": [
        "woody-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "gunsmith-academy-woody-mcp": {
      "command": "uvx",
      "args": [
        "woody-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add gunsmith-academy-woody-mcp -- uvx woody-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gunsmith-academy-woody-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "woody-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add gunsmith-academy-woody-mcp --command uvx --arg woody-mcp
# ~/.hermes/config.yaml
mcp_servers:
  gunsmith-academy-woody-mcp:
    command: "uvx"
    args: ["woody-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "gunsmith-academy-woody-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "woody-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add gunsmith-academy-woody-mcp -t stdio -c uvx -a woody-mcp
// mcp.json
{
  "mcpServers": {
    "gunsmith-academy-woody-mcp": {
      "command": "uvx",
      "args": [
        "woody-mcp"
      ]
    }
  }
}
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.

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 −15
    • Malware scan: pass → unverified security
    • Stability: 0.97 → pass security
  • 16 Sept 26 +16
    • Malware scan: unverified → pass security
  • 15 Sept 26 −15
    • Malware scan: pass → unverified security
  • 14 Sept 26 +16
    • Malware scan: unverified → pass security
  • 12 Sept 26 +1

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

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 Sept 2026 · Analysed pypi/woody-mcp@1.0.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~384 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
ask_woody ~191

Ask Woody any firearms question and get an expert answer with citations. Covers: builds, maintenance, legal/regulatory, ballistics, product specs, compatibility, NFA rules, state law, suppressor setups, and more. Args: question: The firearms question (max 2000 characters). state: US state code for jurisdiction-specific legal answers (e.g. "TX", "CA"). Leave empty for general questions. user_tier: User tier — "free", "operator", "patriot", or "armorer". Affects answer depth and model selection. Returns: Woody's expert answer. If a legal_disclaimer is present, surface it to the user — it means the answer touches on legal or regulatory content.

NameTypeReqDescription
questionstringyes
statestring
user_tierstring
NameTypeReqDescription
resultstringyes

No examples provided.

check_woody_status ~56

Check Woody's current capabilities, KB version, and API status. Use this to verify the connection is working or to see what Woody supports. Returns: Woody's name, version, available tools, and KB stats.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

search_knowledge_base ~137

Search Woody's verified firearms knowledge base directly. Pure vector retrieval — no AI inference, no extra token cost. Returns raw document chunks with relevance scores. Good for fact-checking, looking up specific specs, or finding source material before asking a follow-up question with ask_woody. Args: query: Search query (e.g. "Geissele SSA-E trigger pull weight"). top_k: Number of results to return (1-10, default 3). Returns: Matching knowledge base chunks with relevance scores and metadata.

NameTypeReqDescription
querystringyes
top_kinteger
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the io.github.Gunsmith-Academy/woody-mcp server?

io.github.Gunsmith-Academy/woody-mcp is listed in the public MCP registry as io.github.Gunsmith-Academy/woody-mcp. Woody, the AI firearms expert. Verified specs, legal lookups, and knowledge base. This page covers its PyPI package (woody-mcp).

Is the io.github.Gunsmith-Academy/woody-mcp server safe to use?

io.github.Gunsmith-Academy/woody-mcp scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 io.github.Gunsmith-Academy/woody-mcp server expose?

io.github.Gunsmith-Academy/woody-mcp exposes 3 tools: ask_woody, search_knowledge_base, check_woody_status. Their descriptions and schemas cost roughly 384 tokens of context every time the server is loaded.

Is the io.github.Gunsmith-Academy/woody-mcp server still maintained?

io.github.Gunsmith-Academy/woody-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Gunsmith-Academy/woody-mcp server under?

io.github.Gunsmith-Academy/woody-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.