ThreadCraft Community Research
REMOTE · THREADFOX.VIP
Compare community research, check $20 and $99 licenses, and request private Bitcoin invoices.
Available components
Last scanned (12 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
Category News and Social
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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 →
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.
- 21 Nov 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 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.
- 18 Nov 26 −4
- Authorization: pass → partial ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 48 → 60 ▼ functional
- Tool coverage: 0% → 33% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Tool coverage: 40 functional
- New tool “get_research_offers” functional
- New tool “prepare_research_bitcoin_invoice” functional
- 17 Nov 26 76
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 21 Nov 2026 · Probed https://threadfox.vip/tc/bitcoin/research/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=threadfox.vip | CN=YE2,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6b3477ee8d7f113214bbc5ccfbf464324c3 |
| SANs: *.threadfox.vip, threadfox.vip | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of threadfox.vip. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| vip. | DS published | 61573 | 13 | Verified |
| threadfox.vip. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://threadfox.vip/tc/bitcoin/research/mcp | HTTP error | 530 | |
| http (plaintext) | http://threadfox.vip/tc/bitcoin/research/mcp | HTTPS enforced | 301 | https://threadfox.vip/tc/bitcoin/research/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_communities Compare Reddit communities ~66
Compare up to eight community names. Returns observed count ranges and the percentage of communities with fewer threads found. Public sample rows also include exact counts. Accepts names with or without r/. Results follow input order and are case-insensitive.
| Name | Type | Req | Description |
|---|---|---|---|
| communities | array | yes | – |
No output schema declared.
No examples provided.
describe_dataset Describe the research dataset ~39
Return the observation methodology, field definitions, exact sample size, distribution of all communities by observed threads found, and URLs for the sample and dataset page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
describe_threadcraft_bundle Inspect the ThreadCraft system and local plugin ~27
Show the contents and purchase options when a user asks about the full ThreadCraft product.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_research_offers Compare research licenses and prices ~39
Get current USD prices, availability, license terms, card checkout and free sample links. Use for price or purchase questions. Creates no order.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
prepare_research_bitcoin_invoice Prepare a private Bitcoin invoice ~101
Create or retrieve a private on-chain Bitcoin invoice after the buyer requests checkout for a specific research edition. This reserves a quote and never sends funds. Reuse the same edition and key to check payment and get paid downloads. Keep the key and receipt private.
| Name | Type | Req | Description |
|---|---|---|---|
| order_key | string | yes | A fresh private random UUIDv4 for this intended order. Save and reuse it for retries or payment status. |
| sku | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the ThreadCraft Community Research MCP server?
ThreadCraft Community Research is a hosted endpoint at https://threadfox.vip/tc/bitcoin/research/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 · threadfox.vip
claude mcp add --transport http vip-threadfox-community-research 'https://threadfox.vip/tc/bitcoin/research/mcp'
What is the ThreadCraft Community Research MCP server?
ThreadCraft Community Research is an MCP server listed in the public MCP registry as vip.threadfox/community-research. Compare community research, check $20 and $99 licenses, and request private Bitcoin invoices. This page covers its hosted endpoint (https://threadfox.vip/tc/bitcoin/research/mcp).
Is the ThreadCraft Community Research MCP server safe to use?
ThreadCraft Community Research scores 23 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 ThreadCraft Community Research MCP server expose?
ThreadCraft Community Research exposes 5 tools: compare_communities, describe_dataset, describe_threadcraft_bundle, get_research_offers, prepare_research_bitcoin_invoice. Their descriptions and schemas cost roughly 272 tokens of context every time the server is loaded.
Does the ThreadCraft Community Research MCP server require authentication?
Its publisher declares no required credentials for ThreadCraft Community Research. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ThreadCraft Community Research MCP server still maintained?
ThreadCraft Community Research is still listed as active in the MCP registry. We last reached this channel on 21 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 ThreadCraft Community Research MCP server?
VerifyMCP ran 5 checks on ThreadCraft Community Research, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about ThreadCraft Community Research: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.