WebRef (paid)
REMOTE · WEBREF.JOHNAIO281.WORKERS.DEV
Web standards and time reference for agents: HTTP codes, retries, deadlines. Paid via x402.
Available components
Last scanned (2 minutes ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 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. See how to fix → View diagnostics → Unverified
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1180 tokens (~84/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 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.
- 26 Oct 26 +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.
- 23 Oct 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.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ 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 5 Nov 2026 · Probed https://webref.johnaio281.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=johnaio281.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 63a205b5eddc3fa8d66a145340e3bf8795d |
| SANs: *.johnaio281.workers.dev, johnaio281.workers.dev | ||||||
| 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 webref.johnaio281.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://webref.johnaio281.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://webref.johnaio281.workers.dev/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. 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 →
add_duration ~89
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)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | how many units, may be negative |
| at | string | yes | the start instant, ISO-8601 |
| unit | string | – | the unit of amount |
No output schema declared.
No examples provided.
business_days_between ~80
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)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | start date, YYYY-MM-DD |
| to | string | yes | end date, YYYY-MM-DD |
No output schema declared.
No examples provided.
content_type_advice ~66
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)
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | yes | the Content-Type header value |
| endpointKind | string | yes | what the endpoint expects |
No output schema declared.
No examples provided.
convert_duration ~86
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)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | the unit of value |
| to | string | – | the unit to convert into |
| value | number | yes | the magnitude |
No output schema declared.
No examples provided.
describe_instant ~104
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)
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | yes | the instant, ISO-8601, e.g. 2026-01-01T21:30:00Z |
| timezone | string | – | which timezone the caller cares about |
No output schema declared.
No examples provided.
http_method ~59
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)
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | e.g. GET, POST, PATCH |
No output schema declared.
No examples provided.
http_status ~90
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)
| Name | Type | Req | Description |
|---|---|---|---|
| code | number|string | yes | status code, e.g. 429 |
| detail | string | – | summary = name and class only; decision = what the client should do |
No output schema declared.
No examples provided.
list_mime_types ~82
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)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | – | – |
| topLevel | string | – | application, text, image, audio, video, font, model, multipart, message, example |
No output schema declared.
No examples provided.
mime_type ~73
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)
| Name | Type | Req | Description |
|---|---|---|---|
| extension | string | – | extension, with or without the dot |
| type | string | – | full type, e.g. application/json |
No output schema declared.
No examples provided.
retry_advice ~77
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)
| Name | Type | Req | Description |
|---|---|---|---|
| code | number|string | yes | – |
| idempotent | boolean | – | whether the request being handled is idempotent |
No output schema declared.
No examples provided.
status_for_situation ~67
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)
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | free text describing what went wrong |
No output schema declared.
No examples provided.
time_until ~109
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)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | start instant, ISO-8601, e.g. 2026-01-01T00:00:00Z |
| to | string | yes | end instant, ISO-8601 |
No output schema declared.
No examples provided.
unix_time ~74
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)
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | a date (YYYY-MM-DD) or instant, ISO-8601 |
| timestamp | number | – | a Unix timestamp in seconds |
No output schema declared.
No examples provided.
weekday_of ~79
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)
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | the date, YYYY-MM-DD |
| weekStartsOn | string | – | which day the week is considered to start on |
No output schema declared.
No examples provided.
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.
remote · webref.johnaio281.workers.dev
claude mcp add --transport http dev-workers-johnaio281-webref-webref 'https://webref.johnaio281.workers.dev/mcp'
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.