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.markswendsen-code/target

NPM · @STRIDERLABS/MCP-TARGET

MCP server for Target - search products, manage cart, track orders

0 this week 82 Trust /100

Last scanned (7 hours ago)

Scores higher than 70% of npm servers

Category E-commerce

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 519 tokens (~43/item across 12 items; 12 tools + 0 resources), lean.Pass
  • 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_cart" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 12 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 2 Nov 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 1 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 0
    • Stability: pass → 0.97 functional
  • 19 Oct 26 0
    • Stability: 0.97 → pass security
  • 18 Oct 26 +1

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

  • 15 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
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 7 Nov 2026 · Analysed npm/@striderlabs/mcp-target@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 →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~519 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
add_to_cart ~72

Add a product to the Target cart for pickup or delivery

NameTypeReqDescription
fulfillmentstring–Fulfillment method (default: shipping)
quantitynumber–Quantity to add (default: 1)
tcinstring–Target product TCIN
urlstring–Target product URL

No output schema declared.

No examples provided.

check_store_availability ~67

Check if a product is available for in-store pickup at nearby Target stores

NameTypeReqDescription
tcinstring–Target product TCIN/item ID
urlstring–Product URL (alternative to TCIN)
zip_codestring–ZIP code to find nearby stores

No output schema declared.

No examples provided.

checkout ~41

Preview or place a Target order. Use confirm=false to preview first.

NameTypeReqDescription
confirmboolean–Set true to actually place the order. Default false (preview only).

No output schema declared.

No examples provided.

clear_cart ~16

Remove all items from the Target cart

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_orders ~31

Get Target order history

NameTypeReqDescription
limitnumber–Number of recent orders to return (default: 10)

No output schema declared.

No examples provided.

get_product ~60

Get detailed product information including price, description, and availability

NameTypeReqDescription
tcinstring–Target product TCIN/item ID (alternative to URL)
urlstring–Full Target product URL (e.g., https://www.target.com/p/...)

No output schema declared.

No examples provided.

login ~64

Authenticate with Target account using email and password via browser automation

NameTypeReqDescription
emailstringyesTarget account email
headlessboolean–Run browser in headless mode (default: true). Set false to see browser window.
passwordstringyesTarget account password

No output schema declared.

No examples provided.

logout ~14

Clear Target session and stored cookies

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_products ~98

Search Target products by query with optional filters

NameTypeReqDescription
categorystring–Category filter (e.g., 'electronics', 'clothing')
limitnumber–Maximum number of results (default: 10, max: 24)
max_pricenumber–Maximum price filter
min_pricenumber–Minimum price filter
querystringyesSearch term
sort_bystring–Sort order

No output schema declared.

No examples provided.

status ~15

Check Target authentication status and session info

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

track_order ~25

Track a Target order status

NameTypeReqDescription
order_idstringyesTarget order ID

No output schema declared.

No examples provided.

view_cart ~16

View current Target cart contents and totals

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.markswendsen-code/target MCP server?

io.github.markswendsen-code/target runs locally as an npm package, launched with npx -y @striderlabs/mcp-target. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @striderlabs/mcp-target

# add to Claude Code
claude mcp add markswendsen-code-target -- npx -y @striderlabs/mcp-target
Common questions

What is the io.github.markswendsen-code/target MCP server?

io.github.markswendsen-code/target is an MCP server listed in the public MCP registry as io.github.markswendsen-code/target. MCP server for Target - search products, manage cart, track orders. This page covers its npm package (@striderlabs/mcp-target).

Is the io.github.markswendsen-code/target MCP server safe to use?

io.github.markswendsen-code/target scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 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 io.github.markswendsen-code/target MCP server expose?

io.github.markswendsen-code/target exposes 12 tools: status, login, logout, search_products, get_product, and 7 more. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

Is the io.github.markswendsen-code/target MCP server still maintained?

io.github.markswendsen-code/target is still listed as active in the MCP registry. We last reached this channel on 7 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 io.github.markswendsen-code/target MCP server under?

io.github.markswendsen-code/target 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 io.github.markswendsen-code/target MCP server?

VerifyMCP ran 16 checks on io.github.markswendsen-code/target, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.