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.cyanheads/stackexchange-mcp-server

REMOTE · STACKEXCHANGE.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 21

Search Stack Exchange questions, fetch Q&A threads as markdown, look up tag FAQs and user profiles.

0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1372 tokens (~274/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 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
  • 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 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 current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.cyanheads/stackexchange-mcp-server server?

io.github.cyanheads/stackexchange-mcp-server is a hosted endpoint at https://stackexchange.caseyjhand.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · stackexchange.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-stackexchange-mcp-server 'https://stackexchange.caseyjhand.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cyanheads-stackexchange-mcp-server": {
      "url": "https://stackexchange.caseyjhand.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cyanheads-stackexchange-mcp-server": {
      "type": "http",
      "url": "https://stackexchange.caseyjhand.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cyanheads-stackexchange-mcp-server]
url = "https://stackexchange.caseyjhand.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-stackexchange-mcp-server": {
      "type": "remote",
      "url": "https://stackexchange.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-stackexchange-mcp-server --url 'https://stackexchange.caseyjhand.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-stackexchange-mcp-server:
    url: "https://stackexchange.caseyjhand.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cyanheads-stackexchange-mcp-server": {
      "Transport": "http",
      "Url": "https://stackexchange.caseyjhand.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cyanheads-stackexchange-mcp-server -t streamable-http -u 'https://stackexchange.caseyjhand.com/mcp'
// mcp.json
{
  "mcpServers": {
    "cyanheads-stackexchange-mcp-server": {
      "type": "http",
      "url": "https://stackexchange.caseyjhand.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 19 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.1.14 → 0.1.15 functional
  • 10 Sept 26 −1
    • Tool “stackexchange_get_tag_faq” rewrote its description, which is the text the model reads security
    • Tool “stackexchange_get_user” rewrote its description, which is the text the model reads security
    • Tool “stackexchange_search_questions” rewrote its description, which is the text the model reads security
    • Schema quality: 228 → 285 functional
    • Server version: 0.1.12 → 0.1.14 functional
    • Server version: 0.1.11 → 0.1.12 functional
    • Server version: 0.1.10 → 0.1.11 functional
    • “stackexchange_search_questions” added an optional parameter “page” cosmetic
    • “stackexchange_get_thread” added an optional parameter “includeComments” cosmetic
    • “stackexchange_get_tag_faq” added an optional parameter “page” cosmetic
    • “stackexchange_get_user” reworded the description of “userId” cosmetic
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 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.

  • 7 Sept 26 −1
    • Stability: pass → 0.93 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 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.

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 · Probed https://stackexchange.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 a6985204ed51ae050e7738aa6be668e9
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of stackexchange.caseyjhand.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
stackexchange.caseyjhand.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://stackexchange.caseyjhand.com/mcp Verified 200
http (plaintext) http://stackexchange.caseyjhand.com/mcp HTTPS enforced 301 https://stackexchange.caseyjhand.com/mcp
MCP tools · 5 exposed · ~1,316 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
stackexchange_get_tag_faq ~281

Fetch the highest-voted answered questions for a tag on a Stack Exchange site — the canonical "best answers in X" list. Returns a question list without bodies; use stackexchange_get_thread to read the full body and answers for any result. Results past the pageSize cap are reachable with the `page` parameter. Use this tool to find the authoritative community resources on a topic (e.g. tag "javascript" on stackoverflow). Use stackexchange_search_questions for free-text search rather than tag-based browsing.

NameTypeReqDescription
pageintegerPage of results to return, 1-based (default 1). Page 2 with pageSize 10 returns results 11–20. Each page is a separate upstream call and costs one API quota unit, which matters on the keyless 300/day…
pageSizeintegerNumber of results to return (1–30, default 10).
sitestringStack Exchange site — use the api_site_parameter value (e.g. "stackoverflow", "superuser"). Defaults to "stackoverflow". Call stackexchange_list_sites to discover valid values.
tagstringyesTag to look up (e.g. "python", "javascript", "docker"). Must match exactly.
NameTypeReqDescription
attributionstringContent license notice. Stack Exchange content is licensed under CC BY-SA 4.0 and requires attribution.
capnumberThe pageSize cap applied to this request.
errorobjectPresent when the call failed. Absent on success.
noticestringActionable guidance when results are empty or filtered.
pageintegerThe 1-based page these results came from — 1 when the input omitted page.
questionsarrayHighest-voted answered questions for the specified tag, ordered by votes.
quotaMaxnumberMaximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumberRemaining API quota calls for the current day.
shownnumberNumber of results returned.
sitestringStack Exchange site api_site_parameter used for this lookup.
tagstringTag name used for this FAQ lookup.
truncatedbooleanTrue when results were capped at pageSize.

No examples provided.

stackexchange_get_thread ~346

Fetch a complete Q&A thread — question body and all answers, accepted answer first then sorted by score, rendered as clean markdown with fenced code blocks. Accepts an integer question ID or a full Stack Exchange question URL (e.g. "https://stackoverflow.com/questions/11227809/why-is-processing-a-sorted-array-faster" or "11227809"). HTML is normalized to markdown automatically; attribution (author + link) included per CC BY-SA 4.0. Get question IDs from stackexchange_search_questions or stackexchange_get_tag_faq.

NameTypeReqDescription
includeCommentsbooleanFetch the comment thread under the question and under every returned answer (default false). Comments are where a stale answer usually gets corrected ("this breaks on v3", "use X instead now"), so se…
maxAnswersintegerMaximum number of answers to include (1–100, default 10). Answers are sorted: accepted first, then by score.
questionIdOrUrlstringyesNumeric question ID (e.g. "11227809") or a full Stack Exchange question URL (e.g. "https://stackoverflow.com/questions/11227809/why-is-processing-a-sorted-array-faster"). The integer immediately foll…
sitestringStack Exchange site — use the api_site_parameter value (e.g. "stackoverflow", "superuser"). Defaults to "stackoverflow". Must match the site where the question lives. Call stackexchange_list_sites to…
NameTypeReqDescription
acceptedAnswerIdintegerID of the accepted answer when one exists.
answerCountintegerTotal answers the question has upstream. When greater than the returned answers[] length, more answers exist — raise maxAnswers to fetch them.
answersarrayAnswers sorted: accepted answer first, then by score descending.
authorLinkstringQuestion author profile URL when available.
authorNamestringQuestion author display name when available.
authorUserIdintegerQuestion author numeric user ID when available — pass to stackexchange_get_user to fetch the full profile.
bodyMarkdownstringQuestion body normalized from HTML to markdown.
capnumberThe maxAnswers cap applied to this request.
commentsarrayComments on the question, newest first, present only when includeComments is true. An empty array means this post has no comments; an absent array means its comment state is unknown — either comments…
commentsCapnumberMaximum comments carried per post — a post at this count reports commentsTruncated.
commentsTruncatedbooleanTrue when the question's comments[] is a partial list — more exist upstream than were returned.
creationDatestringISO 8601 timestamp of when the question was asked — use it to judge whether the advice is still current.
errorobjectPresent when the call failed. Absent on success.
lastActivityDatestringISO 8601 timestamp of the most recent activity on the question (edit, answer, or comment).
linkstringDirect URL to the question.
questionIdintegerNumeric question ID — identifies this thread on the site.
quotaMaxnumberMaximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumberRemaining API quota calls for the current day.
scoreintegerQuestion score (upvotes minus downvotes).
shownnumberNumber of answers returned.
tagsarrayTags applied to this question.
titlestringQuestion title.
truncatedbooleanTrue when answers were capped at maxAnswers.

No examples provided.

stackexchange_get_user ~164

Fetch a Stack Exchange user profile by numeric user ID: reputation, badge counts, answer and question counts, account and last-access dates, and top tags by answer score. Useful for credibility context on an answer author — pass the authorUserId from any question or answer in stackexchange_get_thread output. Returns profile fields plus up to 10 top tags by answer score.

NameTypeReqDescription
sitestringStack Exchange site — use the api_site_parameter value (e.g. "stackoverflow", "superuser"). Defaults to "stackoverflow". Call stackexchange_list_sites to discover valid values.
userIdintegeryesNumeric user ID (at most 2147483647) — use the authorUserId field from a question or answer in stackexchange_get_thread output.
NameTypeReqDescription
answerCountintegerTotal number of answers posted when provided by the API.
badgeCountsobjectBadge counts when provided by the API.
creationDatestringISO 8601 timestamp of when the account was created — the account age.
displayNamestringDisplay name shown on the site.
errorobjectPresent when the call failed. Absent on success.
lastAccessDatestringISO 8601 timestamp of the last time the user accessed the site — a stale value means the author is unlikely to respond.
linkstringDirect URL to the user profile.
locationstringUser-provided location string when available.
questionCountintegerTotal number of questions posted when provided by the API.
quotaMaxnumberMaximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumberRemaining API quota calls for the current day.
reputationintegerUser reputation score.
topTagsarrayTop tags by answer score (up to 10). Empty array for new users with no answers.
userIdintegerNumeric user ID on this Stack Exchange site.
websiteUrlstringUser-provided website URL when available.

No examples provided.

stackexchange_list_sites ~118

Enumerate all sites in the Stack Exchange network — name, api_site_parameter, audience, and URL. The api_site_parameter value is what other tools accept as the `site` input (e.g. "stackoverflow", "superuser", "serverfault"). Results are fetched live and optionally filtered by name. Use this tool to discover valid site parameters before calling other stackexchange_* tools.

NameTypeReqDescription
filterstringOptional case-insensitive name filter — returns only sites whose name contains all provided tokens. Omit to return all sites.
NameTypeReqDescription
errorobjectPresent when the call failed. Absent on success.
noticestringActionable guidance when results are empty or filtered.
quotaMaxnumberMaximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumberRemaining API quota calls for the current day.
sitesarrayStack Exchange network sites matching the optional name filter.
totalCountnumberTotal number of sites returned after filtering.

No examples provided.

stackexchange_search_questions ~407

Search questions across a Stack Exchange site. Returns ranked questions with title, score, answer count, accepted status, tags, ask and last-activity dates, and a short excerpt of the question body — not the full body. Results supply question_id values for stackexchange_get_thread, which fetches the full question body and all answers. Results past the pageSize cap are reachable with the `page` parameter. Use the `site` parameter to target a specific community (e.g. "stackoverflow", "superuser", "unix"); call stackexchange_list_sites to discover valid site values.

NameTypeReqDescription
acceptedOnlybooleanWhen true, return only questions that have an accepted answer.
minScoreintegerMinimum question score — excludes questions with lower scores. Setting minScore orders results by score (votes), which may differ from the requested sort.
pageintegerPage of results to return, 1-based (default 1). Page 2 with pageSize 10 returns results 11–20. Each page is a separate upstream call and costs one API quota unit, which matters on the keyless 300/day…
pageSizeintegerNumber of results to return (1–30, default 10).
querystringyesFull-text search query (e.g. "python async generator send value").
sitestringStack Exchange site to search — use the api_site_parameter value (e.g. "stackoverflow", "superuser", "serverfault"). Defaults to "stackoverflow". Call stackexchange_list_sites to discover valid value…
sortstringResult ordering: "relevance" (default, best match), "votes" (highest score first), "activity" (most recently active), "newest" (most recently created).
tagsarrayFilter results to questions with all specified tags.
NameTypeReqDescription
attributionstringContent license notice. Stack Exchange content is licensed under CC BY-SA 4.0 and requires attribution.
capnumberThe pageSize cap applied to this request.
errorobjectPresent when the call failed. Absent on success.
noticestringActionable guidance when results are empty or filtered.
pageintegerThe 1-based page these results came from — 1 when the input omitted page.
questionsarrayQuestions matching the search query, ordered by the specified sort.
quotaMaxnumberMaximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumberRemaining API quota calls for the current day.
shownnumberNumber of results returned.
truncatedbooleanTrue when results were capped at pageSize.

No examples provided.

Common questions

What is the io.github.cyanheads/stackexchange-mcp-server server?

io.github.cyanheads/stackexchange-mcp-server is listed in the public MCP registry as io.github.cyanheads/stackexchange-mcp-server. Search Stack Exchange questions, fetch Q&A threads as markdown, look up tag FAQs and user profiles. This page covers its hosted endpoint (https://stackexchange.caseyjhand.com/mcp).

Is the io.github.cyanheads/stackexchange-mcp-server server safe to use?

io.github.cyanheads/stackexchange-mcp-server scores 80 out of 100 on VerifyMCP. 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.cyanheads/stackexchange-mcp-server server expose?

io.github.cyanheads/stackexchange-mcp-server exposes 5 tools: stackexchange_list_sites, stackexchange_search_questions, stackexchange_get_tag_faq, stackexchange_get_user, stackexchange_get_thread. Their descriptions and schemas cost roughly 1,316 tokens of context every time the server is loaded.

Does the io.github.cyanheads/stackexchange-mcp-server server require authentication?

No. We connected to io.github.cyanheads/stackexchange-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/stackexchange-mcp-server server still maintained?

io.github.cyanheads/stackexchange-mcp-server 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.