Shots for Bots
NPM · SHOTSFORBOTS-MCP
Search 3,790 photographs free; buy full-resolution originals with USDC over HTTP 402 (x402).
Available components
Last scanned (18 hours ago)
Scores higher than 46% of npm servers
Category Design and Media
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 59 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 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.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
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 Nov 2026 · Analysed npm/shotsforbots-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
buy_photo Buy a photo original ~282
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 <id>.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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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 <id>.jpg in |
No output schema declared.
No examples provided.
catalog_info Catalog info ~38
Catalog head: item count, prices in use, license URL, contact, x402 endpoint and protocol, plus this client's wallet status and spend caps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_photo Get photo details and price ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Catalog id: 12 lowercase hex characters (first 12 of the original's SHA-256) |
No output schema declared.
No examples provided.
search_photos Search photos ~293
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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') |
No output schema declared.
No examples provided.
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.
npm · shotsforbots-mcp
claude mcp add com-shotsforbots-shotsforbots-mcp -- npx -y shotsforbots-mcp
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 73 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 21 November 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 21 November 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.
What did VerifyMCP test on the Shots for Bots MCP server?
VerifyMCP ran 15 checks on Shots for Bots, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Shots for Bots: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.