# Shots for Bots (npm · shotsforbots-mcp) Search 3,790 photographs free; buy full-resolution originals with USDC over HTTP 402 (x402). - Trust score: 64/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-26 ## Components - npm · `shotsforbots-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-shotsforbots-shotsforbots-mcp/shotsforbots-mcp.md), [page](https://verifymcp.io/servers/com-shotsforbots-shotsforbots-mcp/shotsforbots-mcp) ## Channel facts - Registry: `npm` - Package: `shotsforbots-mcp` - Version: `0.1.2` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-26. - **Supply Chain Security**: 99/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - 31 of 115 dependencies flagged as unhealthy. - **Provenance & Transparency**: 19/100 - Repository check failed: no source repository is declared. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 3 days ago). - Security-disclosure policy not yet verified: we couldn't inspect the source repository. - **Schema Quality & AI Usability**: 71/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 816 tokens (~204/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **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. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 5 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. **Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the Shots for Bots MCP server? Shots for Bots runs locally as an npm package, launched with npx -y shotsforbots-mcp. 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 com-shotsforbots-shotsforbots-mcp -- npx -y shotsforbots-mcp ``` ### Cursor ```json { "mcpServers": { "com-shotsforbots-shotsforbots-mcp": { "command": "npx", "args": [ "-y", "shotsforbots-mcp" ] } } } ``` ### VS Code ```json { "servers": { "com-shotsforbots-shotsforbots-mcp": { "command": "npx", "args": [ "-y", "shotsforbots-mcp" ] } } } ``` ### Codex ```bash codex mcp add com-shotsforbots-shotsforbots-mcp -- npx -y shotsforbots-mcp ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-shotsforbots-shotsforbots-mcp": { "type": "local", "command": [ "npx", "-y", "shotsforbots-mcp" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-shotsforbots-shotsforbots-mcp --command npx --arg -y --arg shotsforbots-mcp ``` ### Hermes ```yaml mcp_servers: com-shotsforbots-shotsforbots-mcp: command: "npx" args: ["-y", "shotsforbots-mcp"] ``` ### Netclaw ```json { "McpServers": { "com-shotsforbots-shotsforbots-mcp": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "shotsforbots-mcp" ] } } } ``` ### Vellum ```bash assistant mcp add com-shotsforbots-shotsforbots-mcp -t stdio -c npx -a -y shotsforbots-mcp ``` ### Other ```json { "mcpServers": { "com-shotsforbots-shotsforbots-mcp": { "command": "npx", "args": [ "-y", "shotsforbots-mcp" ] } } } ``` ## 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-09-25 (score 64, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-09-23 (score 64) First indexed and scored. ## MCP tools (4) ### `search_photos` (~293 tokens) Search photos Search the shotsforbots.com catalog. Case-insensitive; every word of `query` must match. Returns catalog ids, prices in USD (= USDC), preview URLs (free, 800 px) and page URLs. Paged: `page` walks the result set, `limit` is the page size (default 20, max 100). `source` says how it was answered: "search-index" means the site's static search index served it in one request, and then `description`, `keywords`, `place` and `taken` are null (not carried by the index) -- call get_photo for the full record. `place` is only in the full catalog, so using it makes this walk every catalog page (slow, megabytes); prefer `query` and `keywords`. Input parameters: - `keywords` (array): Keywords that must all appear in the item's keywords (substring, case-insensitive) - `limit` (integer): Page size, default 20 - `max_price_usd` (number): Only items priced at or below this many USD - `min_megapixels` (number): Minimum width*height in megapixels - `page` (integer): 1-based result page - `place` (string): Place-name substring, e.g. 'Texas' - `query` (string): Free-text terms; all must match (e.g. 'red barn winter') ### `get_photo` (~79 tokens) Get photo details and price Full catalog record for one id plus the exact purchase terms, read from the live 402 without paying: original_url, amount in USDC, network, payTo, asset, and the license summary. Never spends anything. Input parameters: - `id` (string, required): Catalog id: 12 lowercase hex characters (first 12 of the original's SHA-256) ### `buy_photo` (~282 tokens) Buy a photo original Pay for and download the full-resolution original of one photo. Spends USDC from the wallet in SHOTSFORBOTS_PRIVATE_KEY (network eip155:8453); refuses without signing when the price exceeds max_price_usd (default 0.50) or would push today's spend over the daily cap (5.00 USD, UTC day). Saves .jpg under out_dir (default /tmp/Downloads/shotsforbots) and returns path, bytes, sha256, price_paid, tx_hash and network. The download is verified against the catalog's sha256; an interrupted transfer is retried with the server's redelivery token (no second payment, up to 3 attempts), and if it still fails the result is status "partial" with tx_hash, redelivery_remaining, token_expires and the licensing contact to email. A file already on disk with the catalog's sha256 is returned without paying. Call get_photo first to see the price. Input parameters: - `id` (string, required): Catalog id: 12 lowercase hex characters (first 12 of the original's SHA-256) - `max_price_usd` (number): Refuse if the price is above this (default 0.50 or SHOTSFORBOTS_MAX_PRICE_USD) - `out_dir` (string): Directory to save .jpg in ### `catalog_info` (~38 tokens) Catalog info Catalog head: item count, prices in use, license URL, contact, x402 endpoint and protocol, plus this client's wallet status and spend caps. ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-shotsforbots-shotsforbots-mcp/shotsforbots-mcp#diagnostics ## Score history - 2026-09-26: 64 - 2026-09-25: 64 - 2026-09-24: 64 - 2026-09-23: 64 ## Common questions ### What is the Shots for Bots MCP server? Shots for Bots is an MCP server listed in the public MCP registry as com.shotsforbots/shotsforbots-mcp. Search 3,790 photographs free; buy full-resolution originals with USDC over HTTP 402 (x402). This page covers its npm package (shotsforbots-mcp). ### Is the Shots for Bots MCP server safe to use? Shots for Bots scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. 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 Shots for Bots MCP server expose? Shots for Bots exposes 4 tools: search_photos, get_photo, buy_photo, catalog_info. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded. ### Is the Shots for Bots MCP server still maintained? Shots for Bots is still listed as active in the MCP registry. We last reached this channel on 26 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 Shots for Bots MCP server under? Shots for Bots declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - npm package: https://www.npmjs.com/package/shotsforbots-mcp - Socket report: https://socket.dev/npm/package/shotsforbots-mcp - Website: https://shotsforbots.com/ - Changelog RSS feed: https://verifymcp.io/servers/com-shotsforbots-shotsforbots-mcp/shotsforbots-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/com-shotsforbots-shotsforbots-mcp/shotsforbots-mcp.json - HTML version of this page: https://verifymcp.io/servers/com-shotsforbots-shotsforbots-mcp/shotsforbots-mcp