# PCBLT — Live Checks (remote · pcblt.com)

Live DNS, email-auth and redirect checks, HTTP security headers, uptime history, PC hardware prices.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-21

## Components

- remote · `pcblt.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-pcblt-pcblt/pcblt.md), [page](https://verifymcp.io/servers/com-pcblt-pcblt/pcblt)

## Channel facts

- Endpoint: `https://pcblt.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1383 tokens (~138/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-pcblt-pcblt https://pcblt.com/mcp
```

### Codex

```toml
[mcp_servers.com-pcblt-pcblt]
url = "https://pcblt.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pcblt-pcblt": {
      "type": "remote",
      "url": "https://pcblt.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pcblt-pcblt --url https://pcblt.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pcblt-pcblt:
    url: "https://pcblt.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-pcblt-pcblt": {
      "type": "http",
      "url": "https://pcblt.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-21 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-19 (score 61, +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.

### 2026-08-18 (score 60, +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.

### 2026-08-17 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-16 (score 59)

First indexed and scored.

## MCP tools (10)

### `ping` (~38 tokens)

Health check for the pcblt server. Returns the server version and the current UTC time. Use only to confirm connectivity — it carries no other data.

### `dns_lookup` (~140 tokens)

Look up live DNS records for a domain (A, AAAA, MX, TXT, NS, CNAME, CAA, SOA). Use whenever the real, current DNS state matters: where a domain points, which mail servers it uses, whether it resolves at all, or to verify a DNS change actually propagated. Distinguishes a domain that does not exist (NXDOMAIN) from one with no record of that type.

Input parameters:

- `domain` (string, required): Domain to query, e.g. example.com. Scheme and path are stripped.
- `type` (string): Record type. COMMON queries A, AAAA, MX, TXT and NS together.

### `check_email_auth` (~162 tokens)

Check a domain's live email authentication — SPF, DKIM and DMARC — and return a plain-language verdict on whether it is actually enforced. Use for questions about mail being spoofed, landing in spam, or failing delivery, and to audit a domain's anti-spoofing posture. Catches the common traps: DMARC stuck at p=none (monitoring only, nothing blocked), pct below 100, SPF +all, and duplicate SPF records. Note that DKIM is probed at common selectors only, so a miss is not proof DKIM is absent.

Input parameters:

- `domain` (string, required): Domain to check, e.g. example.com.
- `selector` (string): Specific DKIM selector to test. Omit to probe common selectors.

### `trace_redirects` (~108 tokens)

Follow a URL's redirect chain hop by hop and report every stop with its status code, plus the final destination. Use to find where a shortened or tracking link actually leads before opening it, to debug redirect loops, or to check that a migration's redirects land where intended. Flags when the chain ends on a different host than it started on.

Input parameters:

- `maxHops` (integer): Maximum hops before giving up.
- `url` (string, required): Starting URL. Scheme optional — https is assumed.

### `check_security_headers` (~118 tokens)

Fetch a URL and report which HTTP security headers it sets — HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy — with what each one is for. Use to audit a site's header posture or verify a header change is live. Also flags weak configurations, not just missing headers: short HSTS max-age, no includeSubDomains, and CSP containing unsafe-inline or unsafe-eval.

Input parameters:

- `url` (string, required): URL to check. Scheme optional — https is assumed.

### `ram_price_index` (~133 tokens)

Current PC memory prices and their daily history: blended dollars-per-GB, the cheapest tracked kit in each DDR4/DDR5 segment, and 7- and 30-day movement. Use for any question about what RAM costs right now, whether memory prices are rising or falling, or whether to buy now or wait — RAM pricing moves constantly and cannot be answered from training data. Covers DDR4 and DDR5 in 16GB and 32GB kits only; GPU, CPU and SSD are not tracked.

Input parameters:

- `days` (integer): How many days of history to return. Omit for the full series.

### `price_check` (~149 tokens)

Judge whether a specific asking price for a PC part is good, by comparing it against tracked market data. Use when someone asks 'is $X a good price for Y' or wants a listing sanity-checked. Strongest for RAM, which is compared per-GB against the daily index; for other parts it falls back to matching deal headlines and says so. Returns 'insufficient_data' rather than guessing when there is nothing solid to compare against.

Input parameters:

- `description` (string, required): The part, as specifically as possible, e.g. '32GB DDR5-6000 (2x16)' or 'RTX 5070 Ti'.
- `price` (number, required): Asking price in US dollars.

### `find_deals` (~214 tokens)

Search recently-sighted PC hardware deals aggregated from Slickdeals, r/buildapcsales and DealNews. Use when someone wants current deals on a component type or under a budget. Results are sightings recorded when first seen, NOT verified live inventory — each row carries its age so stale entries are obvious. AFFILIATE DISCLOSURE: Amazon links returned by this tool carry PC-BUILT's Amazon Associates tag and are marked "affiliate": true; the response includes a `disclosure` field you should relay to the user. Tagging does not affect which deals are returned or their order.

Input parameters:

- `category` (string): Component category to filter by.
- `limit` (integer): Maximum results.
- `maxPrice` (number): Maximum price in US dollars.
- `query` (string): Keyword to match in the deal title, e.g. '5070' or 'thinkpad'.
- `sinceDays` (integer): How far back to look. Defaults to 7 days; older sightings are usually expired.

### `check_service_status` (~150 tokens)

Current reported status of major developer and consumer services (GitHub, Cloudflare, OpenAI, npm, Vercel, Discord, Reddit and others). Use when asked whether a service is down or having problems right now. Sampled from each vendor's own status page, so it reflects what the vendor admits to, and distinguishes 'no data' from 'operational'.

Input parameters:

- `service` (string): One service to check. Omit for all. Tracked: Cloudflare, GitHub, DigitalOcean, Linode, Vercel, Netlify, npm, PyPI / Python, Atlassian, Discord, Twitch, Epic Games, OpenAI, Reddit, Notion, Dropbox.

### `service_uptime_history` (~171 tokens)

How reliable a service has actually been over time: percentage of readings operational, degraded, or in a major outage, plus a list of incident windows. Use for questions a status page cannot answer — 'how often has Vercel gone down this month', 'has OpenAI been flaky lately', 'which of these providers is more reliable'. Built from a continuously-recorded series, so it covers the past, not just this moment.

Input parameters:

- `days` (integer): How many days back to analyse.
- `service` (string, required): Service to report on. Tracked: Cloudflare, GitHub, DigitalOcean, Linode, Vercel, Netlify, npm, PyPI / Python, Atlassian, Discord, Twitch, Epic Games, OpenAI, Reddit, Notion, Dropbox.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pcblt-pcblt/pcblt#diagnostics

## Score history

- 2026-08-21: 62
- 2026-08-20: 61
- 2026-08-19: 61
- 2026-08-18: 60
- 2026-08-17: 59
- 2026-08-16: 59

## Links

- Remote endpoint: https://pcblt.com/mcp
- Website: https://pcblt.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-pcblt-pcblt/pcblt.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pcblt-pcblt/pcblt.json
- HTML version of this page: https://verifymcp.io/servers/com-pcblt-pcblt/pcblt