GBrain Skills
REMOTE · 43-134-36-21.DUCKDNS.ORG
Curated operational knowledge for AI agents. 2 tools. Paid.
Available components
Last scanned (12 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Memory and Knowledge
Recent critical change
TLS certificate (4 Oct 2026). See the changelog before you install this server.
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 Security46
- 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 enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 404. 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.
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.
- 10 Oct 26 0
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → fail ▼ security
- TLS certificate: fail → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. security
- Score status: failed → scored ▲ functional
- 4 Oct 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but the TLS certificate failed verification. security
- 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
- 26 Aug 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 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 98 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 18 Aug 26 0
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 24 Oct 2026 · Probed https://43-134-36-21.duckdns.org/mcp/gbrain
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=43-134-36-21.duckdns.org | CN=YE1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 667a0a21bd604af8e9dabf83c69cb622edc |
| SANs: 43-134-36-21.duckdns.org | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 43-134-36-21.duckdns.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| duckdns.org. | absent | 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 | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://43-134-36-21.duckdns.org/mcp/gbrain | HTTP error | 404 | |
| http (plaintext) | http://43-134-36-21.duckdns.org/mcp/gbrain | Inconclusive | 404 |
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 →
get_skill ~101
Fetch one GBrain knowledge skill as markdown. Pass the skill name (e.g. 'topic-trading-strategy', 'website-docs-user-guide-features-kanban') or the raw gbrain slug (e.g. 'auto/topics/交易策略'). Content is fetched live from GBrain. Returns {name, slug, title, description, content, digest, fetched_at}.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_name | string | yes | Skill name or gbrain slug to fetch |
No output schema declared.
No examples provided.
list_skills ~35
List all GBrain knowledge skills: skill name, gbrain slug, title, type. Returns metadata only (no page content).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the GBrain Skills MCP server?
GBrain Skills is a hosted endpoint at https://43-134-36-21.duckdns.org/mcp/gbrain, 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 · 43-134-36-21.duckdns.org
claude mcp add --transport http diyaluo-gbrain-skills 'https://43-134-36-21.duckdns.org/mcp/gbrain'
What is the GBrain Skills MCP server?
GBrain Skills is an MCP server listed in the public MCP registry as io.github.diyaluo/gbrain-skills. Curated operational knowledge for AI agents. 2 tools. Paid. This page covers its hosted endpoint (https://43-134-36-21.duckdns.org/mcp/gbrain).
Is the GBrain Skills MCP server safe to use?
GBrain Skills scores 18 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 GBrain Skills MCP server expose?
GBrain Skills exposes 2 tools: list_skills, get_skill. Their descriptions and schemas cost roughly 136 tokens of context every time the server is loaded.
Does the GBrain Skills MCP server require authentication?
Its publisher declares no required credentials for GBrain Skills. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the GBrain Skills MCP server still maintained?
GBrain Skills is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.