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.

Stackexchange

NPM · @PIPEWORX/MCP-STACKEXCHANGE · 2 COMPONENTS

StackExchange MCP — wraps the StackExchange API v2.3 (free, no auth required for read)

+3 this week 82 Trust /100

Last scanned (5 hours ago)

Scores higher than 72% of npm servers

Category Search and Retrieval

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-stackexchange). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 997 tokens (~199/item across 5 items; 5 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.

  • 4 Nov 26 +3
    • Stability: unverified → 0.20 ▲ functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-stackexchange@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-stackexchange
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-stackexchange/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560274035
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:630d2321b1f0343b852e258454c622b1975d5e2f4ddcf2146fb7f3145aa010c49d7fc910307f05dc98679f9f66641c4508fb1cf125aa13b192cf8f3a6

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~945 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
get_answers ~105

Get answers for a specific StackExchange question by ID. Returns answer body, score, and whether it is accepted.

NameTypeReqDescription
_apiKeystring–Optional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.
question_idnumberyesThe numeric question ID from the question URL
sitestring–StackExchange site slug (default: stackoverflow)

No output schema declared.

No examples provided.

list_questions_by_tag ~269

Browse questions by TAG, sorted by votes or recency — answers "top questions tagged <tag>", "trending <tag> questions this week/month", "most-voted <tag> questions". Returns title, score, answer count, whether answered, view count, tags, and link (call get_answers with a returned question_id to read answers). Combine tags with ";" for AND (e.g. "kubernetes;helm"). Distinct from search_questions, which is keyword-based.

NameTypeReqDescription
_apiKeystring–Optional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.
limitnumber–Number of questions to return (1-20, default 10)
sitestring–StackExchange site slug (default: stackoverflow). Examples: serverfault, superuser, askubuntu, math, physics
sortstring–Sort order: votes (default, all-time top), month or week (trending recently), activity (recently active), creation (newest), hot.
tagstringyesTag to browse (e.g. "rust", "kubernetes"). Combine with ";" for AND ("react;typescript").

No output schema declared.

No examples provided.

search_questions ~138

Search for questions on StackOverflow or any StackExchange site. Returns title, body, score, answer count, tags, and link.

NameTypeReqDescription
_apiKeystring–Optional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.
limitnumber–Number of results to return (1-20, default 5)
querystringyesSearch query string
sitestring–StackExchange site slug (default: stackoverflow). Examples: serverfault, superuser, askubuntu, math, physics

No output schema declared.

No examples provided.

stack_get_user ~174

Look up a StackExchange user by numeric ID. Returns display name, reputation, badges (gold/silver/bronze counts), location, website, account age, last access, and per-site activity counts (questions/answers). Works on any StackExchange site (default: stackoverflow).

NameTypeReqDescription
_apiKeystring–Optional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.
sitestring–StackExchange site slug (default: stackoverflow). Examples: serverfault, superuser, askubuntu, math, physics
user_idnumberyesThe numeric StackExchange user ID (visible in profile URL, e.g., stackoverflow.com/users/17034 → 17034)

No output schema declared.

No examples provided.

stack_tags ~259

List or search StackOverflow / StackExchange tags with question counts and synonym info — top tags by popularity, tags matching a name fragment, or stats for specific tags. Answers "most popular StackOverflow tags", "how many questions are tagged X", "which tags have more than N questions". Example: stack_tags({ sort: "popular", limit: 20 }) or stack_tags({ inname: "python" })

NameTypeReqDescription
_apiKeystring–Optional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.
innamestring–Filter to tags whose name contains this fragment, e.g. "python"
limitnumber–Max tags to return, 1-100 (default 20)
min_countnumber–Only return tags with at least this many questions (server-side when sort=popular)
sitestring–StackExchange site (default stackoverflow)
sortstring–popular (question count, default) | name | activity
tagsstring–Exact tag names to look up, semicolon-separated, e.g. "java;python;rust"

No output schema declared.

No examples provided.

Install

How do I install the Stackexchange MCP server?

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

npm · @pipeworx/mcp-stackexchange

# add to Claude Code
claude mcp add pipeworx-io-stackexchange -- npx -y @pipeworx/mcp-stackexchange
Common questions

What is the Stackexchange MCP server?

Stackexchange is an MCP server listed in the public MCP registry as io.github.pipeworx-io/stackexchange. StackExchange MCP, wraps the StackExchange API v2.3 (free, no auth required for read). This page covers its npm package (@pipeworx/mcp-stackexchange).

Is the Stackexchange MCP server safe to use?

Stackexchange scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Stackexchange MCP server expose?

Stackexchange exposes 5 tools: search_questions, get_answers, stack_get_user, list_questions_by_tag, stack_tags. Their descriptions and schemas cost roughly 945 tokens of context every time the server is loaded.

Is the Stackexchange MCP server still maintained?

Stackexchange is still listed as active in the MCP registry. We last reached this channel on 5 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 Stackexchange MCP server under?

Stackexchange 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 Stackexchange MCP server?

VerifyMCP ran 16 checks on Stackexchange, 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.