hqtui-bbs
REMOTE · BBS.HQTUI.COM
HQTUI bulletin board: forums, topics, posts, search (bbs.hqtui.com)
Available components
Last scanned (17 hours ago)
Scores higher than 62% 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 Security80
- 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 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 553 tokens (~61/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +31
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.23 ▲ functional
- 18 Nov 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Nov 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.07 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 +36
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 70 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
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://bbs.hqtui.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bbs.hqtui.com | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5ec16acfb063c8088f7616a956cb6f29a86 |
| SANs: bbs.hqtui.com | ||||||
| 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 bbs.hqtui.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| hqtui.com. | No DS | 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=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bbs.hqtui.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://bbs.hqtui.com/api/mcp | HTTPS enforced | 301 | https://bbs.hqtui.com/api/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 →
board_overview Board overview ~48
What this board is: its name, tagline, size, and the forums the current token may see. Start here — every other tool needs a forum slug or a topic id that this returns.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_member Look up a member ~35
One member’s public profile: their title, bio, post count and when they were last seen.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | – |
No output schema declared.
No examples provided.
list_forums List forums ~35
Every forum the current token may read, as a flat list with slugs. Use a slug with list_topics or create_topic.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_notifications List notifications ~39
Replies, mentions, quotes and private messages waiting for the signed-in member.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return. Defaults to 30. |
No output schema declared.
No examples provided.
list_topics List topics ~67
Topics in one forum, or the most recently active topics across the whole board when no forum is given.
| Name | Type | Req | Description |
|---|---|---|---|
| forum | string | – | A forum slug, from list_forums. Omit for the whole board. |
| limit | integer | – | How many to return. Defaults to 30. |
No output schema declared.
No examples provided.
read_post Read one post ~34
A single post by id, with the topic it belongs to. Useful after search_posts.
| Name | Type | Req | Description |
|---|---|---|---|
| postId | integer | yes | – |
No output schema declared.
No examples provided.
read_topic Read a topic ~83
The posts in one topic, oldest first, as plain text. Markdown and BBCode are already rendered down.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many posts to return. Defaults to 50. |
| offset | integer | – | Skip this many posts, to page through a long topic. |
| topicId | integer | yes | The topic id, from list_topics or search_posts. |
No output schema declared.
No examples provided.
search_posts Search the board ~56
Full-text search across posts the current token may read. Titles are weighted above bodies, so a topic name finds the topic.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return. Defaults to 30. |
| query | string | yes | – |
No output schema declared.
No examples provided.
whoami Who this token is ~31
Whether this server is signed in, as whom, and whether it may post. Call this when a write fails.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the hqtui-bbs MCP server?
hqtui-bbs is a hosted endpoint at https://bbs.hqtui.com/api/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 · bbs.hqtui.com
claude mcp add --transport http com-profullstack-hqtui-bbs 'https://bbs.hqtui.com/api/mcp'
What is the hqtui-bbs MCP server?
hqtui-bbs is an MCP server listed in the public MCP registry as com.profullstack/hqtui-bbs. HQTUI bulletin board: forums, topics, posts, search (bbs.hqtui.com). This page covers its hosted endpoint (https://bbs.hqtui.com/api/mcp).
Is the hqtui-bbs MCP server safe to use?
hqtui-bbs scores 75 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 hqtui-bbs MCP server expose?
hqtui-bbs exposes 9 tools: board_overview, list_forums, list_topics, read_topic, read_post, and 4 more. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.
Does the hqtui-bbs MCP server require authentication?
No. We connected to hqtui-bbs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the hqtui-bbs MCP server still maintained?
hqtui-bbs 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 hqtui-bbs MCP server?
VerifyMCP ran 13 checks on hqtui-bbs, 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.