WebRef (paid)

Name: WebRef (paid)
Author: dev.workers.johnaio281.webref

MCP serverMCP

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

by dev.workers.johnaio281.webrefrepository ↗homepage ↗v1.5.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"webref-paid","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability9/9 checks ok

30 days ago

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	73 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools
11 h ago	mcp initialize	ok	200	39 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools
18 h ago	mcp initialize	ok	200	37 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools
25 h ago	mcp initialize	ok	200	94 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools
32 h ago	mcp initialize	ok	200	69 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	57 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	149 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	73 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	85 ms	server webref 1.0.0 · protocol 2025-06-18 · 14 tools

Tools observed via MCP handshake

http_status — 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 caus
status_for_situation — 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 'upstrea
retry_advice — 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
mime_type — 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)
list_mime_types — 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)
content_type_advice — 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)
http_method — 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)
time_until — 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-l
describe_instant — 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
weekday_of — 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 pe
business_days_between — 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,
add_duration — 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)
convert_duration — 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 seco
unix_time — 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)

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrydev.workers.johnaio281.webref/webref

first seen 2 d ago · fetched 2 d agoopen ↗

Field history (7 recent events)

2 d ago · declared · summary → "Web standards and time reference for agents: HTTP codes, retries, deadlines. Paid via x402."
2 d ago · declared · description → "Web standards and time reference for agents: HTTP codes, retries, deadlines. Paid via x402."
2 d ago · declared · publisherName → "dev.workers.johnaio281.webref"
2 d ago · declared · homepageUrl → "https://webref.johnaio281.workers.dev/"
2 d ago · declared · repoUrl → "https://github.com/johnaio281/webref"
2 d ago · declared · version → "1.5.0"
2 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from