# WebRef (paid) (remote · webref.johnaio281.workers.dev)

Web standards and time reference for agents: HTTP codes, retries, deadlines. Paid via x402.

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `webref.johnaio281.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-johnaio281-webref-webref/webref.md), [page](https://verifymcp.io/servers/dev-workers-johnaio281-webref-webref/webref)

## Channel facts

- Endpoint: `https://webref.johnaio281.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.8.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-11-05.

- **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 14 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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1180 tokens (~84/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the WebRef (paid) MCP server?

WebRef (paid) is a hosted endpoint at https://webref.johnaio281.workers.dev/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.

### Claude

```bash
claude mcp add --transport http dev-workers-johnaio281-webref-webref 'https://webref.johnaio281.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-johnaio281-webref-webref": {
      "url": "https://webref.johnaio281.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-johnaio281-webref-webref": {
      "type": "http",
      "url": "https://webref.johnaio281.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-johnaio281-webref-webref]
url = "https://webref.johnaio281.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-johnaio281-webref-webref": {
      "type": "remote",
      "url": "https://webref.johnaio281.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-johnaio281-webref-webref --url 'https://webref.johnaio281.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-johnaio281-webref-webref:
    url: "https://webref.johnaio281.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-johnaio281-webref-webref": {
      "Transport": "http",
      "Url": "https://webref.johnaio281.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-johnaio281-webref-webref -t streamable-http -u 'https://webref.johnaio281.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-johnaio281-webref-webref": {
      "type": "http",
      "url": "https://webref.johnaio281.workers.dev/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-11-05 (score 67, +1)

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

### 2026-11-03 (score 66, +1)

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

### 2026-11-01 (score 65, +1)

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

### 2026-10-30 (score 64, +1)

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

### 2026-10-28 (score 63, +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.

### 2026-10-26 (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-10-23 (score 61, +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-10-22 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (14)

### `http_status` (~90 tokens)

Look up an HTTP status code: what it means, what the client must do, whether it is retryable, whether it is safe to replay, the defining RFC and the common causes. ($0.003 per call)

Input parameters:

- `code` (number|string, required): status code, e.g. 429
- `detail` (string): summary = name and class only; decision = what the client should do

### `status_for_situation` (~67 tokens)

Find the HTTP status code that matches a described situation, when the code is not known in advance — for example 'the caller is being rate limited' or 'upstream returned garbage'. ($0.005 per call)

Input parameters:

- `situation` (string, required): free text describing what went wrong

### `retry_advice` (~77 tokens)

Decide how a client should react to a status code: retry with backoff, check the outcome before retrying, or do not retry. Includes a suggested backoff schedule. ($0.005 per call)

Input parameters:

- `code` (number|string, required)
- `idempotent` (boolean): whether the request being handled is idempotent

### `mime_type` (~73 tokens)

Look up a MIME type by full type or by file extension: the top-level type, what it is for, and the usual file extension. ($0.003 per call)

Input parameters:

- `extension` (string): extension, with or without the dot
- `type` (string): full type, e.g. application/json

### `list_mime_types` (~82 tokens)

List or search MIME types by top-level type or by keyword, for example image types or anything to do with calendars. ($0.003 per call)

Input parameters:

- `limit` (number)
- `query` (string)
- `topLevel` (string): application, text, image, audio, video, font, model, multipart, message, example

### `content_type_advice` (~66 tokens)

Check whether a Content-Type header matches what an endpoint kind expects, and say what to send instead when it does not. ($0.003 per call)

Input parameters:

- `contentType` (string, required): the Content-Type header value
- `endpointKind` (string, required): what the endpoint expects

### `http_method` (~59 tokens)

Describe an HTTP method: whether it is safe, whether it is idempotent, whether it carries a body, and what it is for. ($0.003 per call)

Input parameters:

- `method` (string, required): e.g. GET, POST, PATCH

### `time_until` (~109 tokens)

How much time is between two instants: the direction, the total in every unit, and a day/hour/minute/second breakdown. Use it to compute a retry delay, a rate-limit reset, or whether a deadline has passed. ($0.003 per call)

Input parameters:

- `from` (string, required): start instant, ISO-8601, e.g. 2026-01-01T00:00:00Z
- `to` (string, required): end instant, ISO-8601

### `describe_instant` (~104 tokens)

Describe an instant: its date, weekday and time in UTC and in Tehran local time (UTC+03:30), plus the Unix timestamp. Use it when a response carries a timestamp and the local date matters. ($0.003 per call)

Input parameters:

- `at` (string, required): the instant, ISO-8601, e.g. 2026-01-01T21:30:00Z
- `timezone` (string): which timezone the caller cares about

### `weekday_of` (~79 tokens)

Which day of the week a date falls on, and whether it is a business day. Use it before scheduling work or setting a deadline that lands on a weekend. ($0.003 per call)

Input parameters:

- `date` (string, required): the date, YYYY-MM-DD
- `weekStartsOn` (string): which day the week is considered to start on

### `business_days_between` (~80 tokens)

Count the business days between two dates, excluding weekends. Use it to turn a calendar deadline into a working-day deadline. Public holidays are not excluded, so the count is an upper bound. ($0.005 per call)

Input parameters:

- `from` (string, required): start date, YYYY-MM-DD
- `to` (string, required): end date, YYYY-MM-DD

### `add_duration` (~89 tokens)

Add a duration to an instant and get the result, in UTC and in Tehran local time. Use it for a TTL, a lock expiry, or a token lifetime. ($0.003 per call)

Input parameters:

- `amount` (number, required): how many units, may be negative
- `at` (string, required): the start instant, ISO-8601
- `unit` (string): the unit of amount

### `convert_duration` (~86 tokens)

Convert a duration between units and get it in plain language. Use it to express a timeout in the unit the caller asked for, or to check whether a limit is seconds, minutes or milliseconds. ($0.003 per call)

Input parameters:

- `from` (string): the unit of value
- `to` (string): the unit to convert into
- `value` (number, required): the magnitude

### `unix_time` (~74 tokens)

Convert between a date and a Unix timestamp, in either direction. Use it when a payload carries one and the other is needed. ($0.003 per call)

Input parameters:

- `date` (string): a date (YYYY-MM-DD) or instant, ISO-8601
- `timestamp` (number): a Unix timestamp in seconds

## Diagnostics

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

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 64
- 2026-10-30: 64
- 2026-10-29: 63
- 2026-10-28: 63
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 61
- 2026-10-24: 61
- 2026-10-23: 61
- 2026-10-22: 60
- 2026-10-21: 60

## Common questions

### What is the WebRef (paid) MCP server?

WebRef (paid) is an MCP server listed in the public MCP registry as dev.workers.johnaio281.webref/webref. Web standards and time reference for agents: HTTP codes, retries, deadlines. Paid via x402. This page covers its hosted endpoint (https://webref.johnaio281.workers.dev/mcp).

### Is the WebRef (paid) MCP server safe to use?

WebRef (paid) scores 67 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 WebRef (paid) MCP server expose?

WebRef (paid) exposes 14 tools: http_status, status_for_situation, retry_advice, mime_type, list_mime_types, and 9 more. Their descriptions and schemas cost roughly 1,135 tokens of context every time the server is loaded.

### Does the WebRef (paid) MCP server require authentication?

No. We connected to WebRef (paid) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the WebRef (paid) MCP server still maintained?

WebRef (paid) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://webref.johnaio281.workers.dev/mcp
- Repository: https://github.com/johnaio281/webref
- Website: https://webref.johnaio281.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-johnaio281-webref-webref/webref.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-johnaio281-webref-webref/webref.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-johnaio281-webref-webref/webref