Entyrax
REMOTE · WWW.ENTYRAX.COM · SCANNED AUG 3
PC hardware decision engine for Brazil (pt-BR): compatibility, GPU recommendations, build analysis.
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 →
Endpoint Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 363 tokens (~121/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.entyrax.com
claude mcp add --transport http com-entyrax-entyrax https://www.entyrax.com/mcp
[mcp_servers.com-entyrax-entyrax] url = "https://www.entyrax.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-entyrax-entyrax": {
"type": "remote",
"url": "https://www.entyrax.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-entyrax-entyrax --url https://www.entyrax.com/mcp --transport streamable-http
mcp_servers:
com-entyrax-entyrax:
url: "https://www.entyrax.com/mcp" {
"mcpServers": {
"com-entyrax-entyrax": {
"type": "http",
"url": "https://www.entyrax.com/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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 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.
- 28 Jul 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.
- 27 Jul 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 Jul 26 64
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 3 Aug 2026 · Probed https://www.entyrax.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=entyrax.com | CN=YE1,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6ea47295f8460d2d692a59514cc851996f1 |
| SANs: *.entyrax.com, entyrax.com | ||||||
| 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 |
DNSSEC insecure
Validation of www.entyrax.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| entyrax.com. | 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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.entyrax.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.entyrax.com/mcp | Served over HTTP | 200 |
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.
analyze_build Analisar build completo ~120
Analisa um build CPU+Mobo+GPU. Retorna overall_quality, reasoning (why_this_mobo/why_this_gpu/budget_note), PSU recomendada e preços.
| Name | Type | Req | Description |
|---|---|---|---|
| cpu_slug | string | yes | Slug da CPU (ex: ryzen-7-7800x3d) |
| gpu_slug | string | yes | Slug da GPU (ex: geforce-rtx-5070-ti) |
| mobo_slug | string | yes | Slug da placa-mãe (ex: gigabyte-b650-aorus-pro-ax) |
| Name | Type | Req | Description |
|---|---|---|---|
| overall_quality | string | — | Qualidade geral do build (ex: excellent, unbalanced) |
| psu | object | — | PSU recomendada para o conjunto |
| reasoning | object | — | why_this_mobo, why_this_gpu, budget_note |
No examples provided.
check_compatibility Verificar compatibilidade ~120
Verifica compatibilidade e qualidade de pairing entre dois componentes (CPU+Mobo, CPU+GPU, GPU+Monitor). Retorna compatibility_status, pairing_quality, confidence e reasoning.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_a | string | yes | Slug do primeiro componente (ex: ryzen-7-7800x3d) |
| entity_b | string | yes | Slug do segundo componente (ex: gigabyte-b650-aorus-pro-ax) |
| pair_type | string | — | Tipo do par. Opcional; se omitido, tenta os três. |
| Name | Type | Req | Description |
|---|---|---|---|
| compatibility_status | string | — | Ex: native_supported, needs_bios_update |
| compatible | boolean | — | Se o par funciona junto |
| confidence | number | — | 0.0–1.0 |
| pair_type | string | — | cpu_mobo | cpu_gpu | gpu_monitor |
| pairing_quality | string | — | Ex: excellent, balanced, bottleneck_risk |
| reason | string | — | Justificativa em pt-BR |
No examples provided.
recommend_gpu_by_context Recomendar GPU por contexto ~94
Recomenda top GPUs dado contexto: resolução (1080p/1440p/4k), uso (gaming-aaa/gaming-competitive/produtividade) e orçamento em BRL.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_brl | number | yes | Orçamento máximo em BRL (ex: 3500) |
| resolution | string | yes | Resolução alvo do monitor |
| use_case | string | yes | Uso principal da máquina |
| Name | Type | Req | Description |
|---|---|---|---|
| picks | array | — | GPUs recomendadas em ordem de adequação |
| reasoning | object | — | Resumo do porquê do ranking |
No examples provided.