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

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

0 this week 89 Trust /100

Last scanned (1 day ago)

Scores higher than 97% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Education and Research

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 Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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 Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1632 tokens (~272/item across 6 items; 5 tools + 1 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 7 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 28 Oct 26 +2
    • Tool “stackexchange_get_tag_faq” rewrote its description, which is the text the model reads security
    • Tool “stackexchange_get_thread” rewrote its description, which is the text the model reads security
    • Schema quality: 1372 → 1632 ▼ functional
    • Schema quality: unverified → 100 ▲ functional
    • New resource “stackexchange-guide” functional
    • Server version: 0.1.17 → 0.2.0 functional
    • “stackexchange_search_questions” reworded the description of “site” cosmetic
    • “stackexchange_get_thread” reworded the description of “site” cosmetic
    • “stackexchange_get_user” reworded the description of “site” cosmetic
    • “stackexchange_get_thread” reworded the description of “questionIdOrUrl” cosmetic
    • “stackexchange_get_tag_faq” reworded the description of “site” cosmetic
  • 25 Oct 26 0
    • Server version: 0.1.16 → 0.1.17 functional
  • 10 Oct 26 0
    • Server version: 0.1.15 → 0.1.16 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 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 0
    • Tool “stackexchange_get_tag_faq” 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
    • Tool “stackexchange_get_user” 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_tag_faq” added an optional parameter “page” cosmetic
    • “stackexchange_get_thread” added an optional parameter “includeComments” cosmetic
    • “stackexchange_get_user” reworded the description of “userId” cosmetic
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
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 · 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 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 995a30681ab772540e934241ca1d576c
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. DS published 19718 13 Verified
caseyjhand.com. DS published 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,499 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 ~310

Fetch the frequently asked questions for a tag on a Stack Exchange site — Stack Exchange's own "frequently asked" selection, returned in its order, not ranked by score; compare the scores yourself. 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 questions a community keeps coming back to on a topic (e.g. tag "javascript" on stackoverflow). Use stackexchange_search_questions for free-text search rather than tag-based browsing.

NameTypeReqDescription
pageinteger–Page 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…
pageSizeinteger–Number of results to return (1–30, default 10).
sitestring–Stack Exchange site — the api_site_parameter (e.g. "stackoverflow", "superuser") or the site's domain (e.g. "superuser.com"). Defaults to "stackoverflow". Call stackexchange_list_sites to discover va…
tagstringyesTag to look up (e.g. "python", "javascript", "docker"). Must match exactly.
NameTypeReqDescription
attributionstring–Content license notice. Stack Exchange content is licensed under CC BY-SA 4.0 and requires attribution.
capnumber–The pageSize cap applied to this request.
errorobject–Present when the call failed. Absent on success.
noticestring–Actionable guidance when results are empty or filtered.
pageinteger–The 1-based page these results came from — 1 when the input omitted page.
questionsarray–The frequently asked questions for the specified tag, in Stack Exchange's order — not sorted by score.
quotaMaxnumber–Maximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumber–Remaining API quota calls for the current day.
shownnumber–Number of results returned.
sitestring–Stack Exchange site used for this lookup, as passed in site.
tagstring–Tag name used for this FAQ lookup.
truncatedboolean–True when results were capped at pageSize.

No examples provided.

stackexchange_get_thread ~453

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 a full Stack Exchange question URL, which is read from the site its host names (e.g. "https://unix.stackexchange.com/questions/88490/how-do-i-use-a-heredoc"), or an integer question ID read from site (e.g. "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
includeCommentsboolean–Fetch 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…
maxAnswersinteger–Maximum 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"). A URL carries its own site:…
sitestring–Stack Exchange site a numeric question ID belongs to — the api_site_parameter (e.g. "stackoverflow", "unix") or the site's domain (e.g. "unix.stackexchange.com"). Defaults to "stackoverflow". Not nee…
NameTypeReqDescription
acceptedAnswerIdinteger–ID of the accepted answer when one exists.
answerCountinteger–Total answers the question has upstream. When greater than the returned answers[] length, more answers exist — raise maxAnswers to fetch them.
answersarray–Answers sorted: accepted answer first, then by score descending.
authorLinkstring–Question author profile URL when available.
authorNamestring–Question author display name when available.
authorUserIdinteger–Question author numeric user ID when available — pass to stackexchange_get_user to fetch the full profile.
bodyMarkdownstring–Question body normalized from HTML to markdown.
capnumber–The maxAnswers cap applied to this request.
commentsarray–Comments 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…
commentsCapnumber–Maximum comments carried per post — a post at this count reports commentsTruncated.
commentsTruncatedboolean–True when the question's comments[] is a partial list — more exist upstream than were returned.
creationDatestring–ISO 8601 timestamp of when the question was asked — use it to judge whether the advice is still current.
errorobject–Present when the call failed. Absent on success.
lastActivityDatestring–ISO 8601 timestamp of the most recent activity on the question (edit, answer, or comment).
linkstring–Direct URL to the question.
questionIdinteger–Numeric question ID — identifies this thread on the site.
quotaMaxnumber–Maximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumber–Remaining API quota calls for the current day.
scoreinteger–Question score (upvotes minus downvotes).
shownnumber–Number of answers returned.
siteConflictobject–Present only when questionIdOrUrl is a URL and site names a different site — says which of the two the question was read from.
tagsarray–Tags applied to this question.
titlestring–Question title.
truncatedboolean–True when answers were capped at maxAnswers.

No examples provided.

stackexchange_get_user ~200

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
sitestring–Stack Exchange site the user ID belongs to — the api_site_parameter (e.g. "stackoverflow", "superuser") or the site's domain (e.g. "superuser.com"). User IDs are per-site, so pass the site of the thr…
userIdintegeryesNumeric user ID (at most 2147483647) — use the authorUserId field from a question or answer in stackexchange_get_thread output.
NameTypeReqDescription
answerCountinteger–Total number of answers posted when provided by the API.
badgeCountsobject–Badge counts when provided by the API.
creationDatestring–ISO 8601 timestamp of when the account was created — the account age.
displayNamestring–Display name shown on the site.
errorobject–Present when the call failed. Absent on success.
lastAccessDatestring–ISO 8601 timestamp of the last time the user accessed the site — a stale value means the author is unlikely to respond.
linkstring–Direct URL to the user profile.
locationstring–User-provided location string when available.
questionCountinteger–Total number of questions posted when provided by the API.
quotaMaxnumber–Maximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumber–Remaining API quota calls for the current day.
reputationinteger–User reputation score.
topTagsarray–Top tags by answer score (up to 10). Empty array for new users with no answers.
userIdinteger–Numeric user ID on this Stack Exchange site.
websiteUrlstring–User-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
filterstring–Optional case-insensitive name filter — returns only sites whose name contains all provided tokens. Omit to return all sites.
NameTypeReqDescription
errorobject–Present when the call failed. Absent on success.
noticestring–Actionable guidance when results are empty or filtered.
quotaMaxnumber–Maximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumber–Remaining API quota calls for the current day.
sitesarray–Stack Exchange network sites matching the optional name filter.
totalCountnumber–Total number of sites returned after filtering.

No examples provided.

stackexchange_search_questions ~418

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
acceptedOnlyboolean–When true, return only questions that have an accepted answer.
minScoreinteger–Minimum question score — excludes questions with lower scores. Setting minScore orders results by score (votes), which may differ from the requested sort.
pageinteger–Page 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…
pageSizeinteger–Number of results to return (1–30, default 10).
querystringyesFull-text search query (e.g. "python async generator send value").
sitestring–Stack Exchange site to search — the api_site_parameter (e.g. "stackoverflow", "superuser", "serverfault") or the site's domain (e.g. "serverfault.com"). Defaults to "stackoverflow". Call stackexchang…
sortstring–Result ordering: "relevance" (default, best match), "votes" (highest score first), "activity" (most recently active), "newest" (most recently created).
tagsarray–Filter results to questions with all specified tags.
NameTypeReqDescription
appliedSortstring–Sort Stack Exchange applied to these results.
attributionstring–Content license notice. Stack Exchange content is licensed under CC BY-SA 4.0 and requires attribution.
capnumber–The pageSize cap applied to this request.
errorobject–Present when the call failed. Absent on success.
noticestring–Actionable guidance when results are empty or filtered.
pageinteger–The 1-based page these results came from — 1 when the input omitted page.
questionsarray–Questions matching the search query, ordered by the specified sort.
quotaMaxnumber–Maximum API quota calls per day (300 keyless, ~10,000 with API key).
quotaRemainingnumber–Remaining API quota calls for the current day.
shownnumber–Number of results returned.
sortOverrideReasonstring–Present only when appliedSort differs from the requested sort; says why.
truncatedboolean–True when results were capped at pageSize.

No examples provided.

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'
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 89 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,499 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.cyanheads/stackexchange-mcp-server server?

VerifyMCP ran 13 checks on io.github.cyanheads/stackexchange-mcp-server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.