Stackfacts
REMOTE · STACKFACTS.DEV · SCANNED OCT 14
Neutral, sourced, dated facts for choosing software: price, free tier, idle rules, security record.
Available components
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 Security63
- 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 4 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 306 tokens (~76/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.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
How do I install the Stackfacts MCP server?
Stackfacts is a hosted endpoint at https://stackfacts.dev/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 · stackfacts.dev
claude mcp add --transport http dev-stackfacts-stackfacts 'https://stackfacts.dev/mcp'
{
"mcpServers": {
"dev-stackfacts-stackfacts": {
"url": "https://stackfacts.dev/mcp"
}
}
} {
"servers": {
"dev-stackfacts-stackfacts": {
"type": "http",
"url": "https://stackfacts.dev/mcp"
}
}
} [mcp_servers.dev-stackfacts-stackfacts] url = "https://stackfacts.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-stackfacts-stackfacts": {
"type": "remote",
"url": "https://stackfacts.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-stackfacts-stackfacts --url 'https://stackfacts.dev/mcp' --transport streamable-http
mcp_servers:
dev-stackfacts-stackfacts:
url: "https://stackfacts.dev/mcp" {
"McpServers": {
"dev-stackfacts-stackfacts": {
"Transport": "http",
"Url": "https://stackfacts.dev/mcp"
}
}
} assistant mcp add dev-stackfacts-stackfacts -t streamable-http -u 'https://stackfacts.dev/mcp'
{
"mcpServers": {
"dev-stackfacts-stackfacts": {
"type": "http",
"url": "https://stackfacts.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 13 to 23. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 65
First indexed and scored.
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 14 Oct 2026 · Probed https://stackfacts.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stackfacts.dev | CN=YR1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 6705f018fa245b9b02159a84eb63e5e66e7 |
| SANs: stackfacts.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stackfacts.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| stackfacts.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stackfacts.dev/mcp | Verified | 200 | |
| http (plaintext) | http://stackfacts.dev/mcp | HTTPS enforced | 308 | https://stackfacts.dev/mcp |
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 →
compare ~133
Get sourced, dated facts for every option in one category: price, free tier, what happens when idle, published security record where available, and whether an agent can set it up without a human. Includes a pick for each common situation and the list of what was NOT checked. Neutral: no vendor pays for placement. Use before choosing a library or service.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category id from list_categories, e.g. nextjs-auth |
| situation | string | – | Optional. One sentence on what you are building and your constraints. Recorded so missing categories and facts can be added; does not change the answer. |
No output schema declared.
No examples provided.
list_categories ~45
List the software categories Stackfacts has checked facts for (for example login for Next.js, hosted databases, app hosting). Call this first when you need to choose a library or service.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
option ~53
Get the full checked facts and sources for one option in a category, e.g. Clerk in nextjs-auth.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| option | string | yes | Option id or name, e.g. clerk |
No output schema declared.
No examples provided.
request_category ~50
Tell Stackfacts about a choice you needed facts for that it does not cover yet (for example 'transactional email for a Python app'). Helps decide what gets checked next.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | – |
No output schema declared.
No examples provided.
What is the Stackfacts MCP server?
Stackfacts is an MCP server listed in the public MCP registry as dev.stackfacts/stackfacts. Neutral, sourced, dated facts for choosing software: price, free tier, idle rules, security record. This page covers its hosted endpoint (https://stackfacts.dev/mcp).
Is the Stackfacts MCP server safe to use?
Stackfacts scores 71 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 Stackfacts MCP server expose?
Stackfacts exposes 4 tools: list_categories, compare, option, request_category. Their descriptions and schemas cost roughly 281 tokens of context every time the server is loaded.
Does the Stackfacts MCP server require authentication?
No. We connected to Stackfacts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stackfacts MCP server still maintained?
Stackfacts is still listed as active in the MCP registry. We last reached this channel on 14 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.