WebRef (paid) is answering right now. Last checked 9 min ago. It exposes 14 tools.
Web standards and time reference for agents: HTTP codes, retries, deadlines. Paid via x402.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
4 days of history
4 days agonow
100.0%
Uptime 24h
91 of 91 checks
14
Tools
read from the server
665 ms
Response time
average over 24h
open, no key
Access
streamable-http
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.
run in your terminal
claude mcp add webref --transport http https://webref.johnaio281.workers.dev/mcpSettings → Connectors → Add custom connector, then paste this address
https://webref.johnaio281.workers.dev/mcp~/.codex/config.toml
[mcp_servers.webref]
url = "https://webref.johnaio281.workers.dev/mcp".cursor/mcp.json
{
"mcpServers": {
"webref": {
"url": "https://webref.johnaio281.workers.dev/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"webref": {
"type": "http",
"url": "https://webref.johnaio281.workers.dev/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
http
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)
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 causes. ($0.003 per call)
mime
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)
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)
business
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, so the count is an upper bound. ($0.005 per call)
content
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)
convert
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 seconds, minutes or milliseconds. ($0.003 per call)
describe
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 and the local date matters. ($0.003 per call)
duration
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)
retry
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. ($0.005 per call)
status
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 'upstream returned garbage'. ($0.005 per call)
time
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-limit reset, or whether a deadline has passed. ($0.003 per call)
unix
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)
weekday
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 per call)
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://webref.johnaio281.workers.dev/mcp | streamable-http | answering | 644 ms | 9 min ago |
Alternatives to WebRef (paid)
same job, measured the same wayagent-site-audit - website audits for agents
by audito
Paid website audits for agents: flat JSON, HTML report, deep audit. USDC via x402.
Verdoc
by verdochello
Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.
Reference Data MCP Server
by cyanheads
Countries, timezones, elements, constants, HTTP status codes, unit conversion, and MIME type lookup.
Httpstatus
by pipeworx-io
HTTP status code reference MCP.
O
Orcpin
by npraught
Paid x402 facts for AI agents: signed statements, door reports, endpoint checks, chain reads
systemprompt.io reports
by systemprompt
Paid EU AI Act compliance reports for agents. $1.50 per call via x402 (USDC on Base) or Stripe.
Sentrik
by maxgerhardson
Governance runtime for AI-generated code. Enforce compliance and security standards.
Fhirfly
by fhirfly
Healthcare reference data for AI agents: providers, drugs, diagnoses, labs, codes, claims.
WebRef (paid) — questions
Answers built from our own checks of this server.
What can WebRef (paid) do?
It exposes 14 tools, read directly from the server on our last check. Among them: add_duration, business_days_between, content_type_advice, convert_duration, describe_instant, http_method and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is WebRef (paid) mostly used for?
Its tools cluster around http and mime. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is WebRef (paid) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 665 ms. The bar chart above shows every period we have measured.
Is WebRef (paid) still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect WebRef (paid)?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does WebRef (paid) need an API key?
No. WebRef (paid) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is WebRef (paid)?
It answers our handshake in 665 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.