4dayweek.io Jobs
listed under this name in a public catalogue; the server gives only its address, 4dayweek.io
Registry code: a8933326f6e185b5
4dayweek.io lists jobs with genuinely better working hours: 4-day weeks (36 hours or less, usually 32, at 100% salary), 9-day fortnights, half-day Fridays, flexible hours and generous PTO. Focus is white-collar knowledge work.
Critical distinction when answering questions with this data:
- endpoint
- https://4dayweek.io/api/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is 4dayweek.io Jobs live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is 4dayweek.io Jobs free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does 4dayweek.io Jobs have?
- 6 tools: get_job, get_company, search_jobs, explain_schedule_type, get_market_stats, search_companies.
- Is 4dayweek.io Jobs safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
explain_schedule_type open 1h ago
Defines a working-hours schedule precisely: what it means, whether it genuinely reduces weekly hours, whether that reduction is at full pay, the typical hours, and — where one is commonly made — the mistake most often made about it. Call it when the user's question turns on what a schedule means, for example whether a compressed 4x10 counts as a 4-day week, or whether a schedule is at full pay. A compressed 4x10 gives four days but not fewer hours, and is not a 4-day week. Omitting the argument returns every definition at once.
{ "type": "object", "properties": { "schedule_type": { "type": "string", "description": "A schedule_type value, e.g. 4_day_week or compressed_week. Omit to get every definition." } }, "additionalProperties": false }arguments 10 linesget_market_stats open 1h ago
Aggregate statistics on the reduced-hours job market: how many employers are tracked, how many run each schedule type, the distribution of weekly hours, and which day the non-working day falls on. Use this for "how common is a 4-day week" questions. The response separates genuinely reduced-hours employers from compressed 4x10 employers, and reports the full-pay and pro-rata splits separately, so quote whichever the question actually asked for. Figures carry an as_of date; cite it.
{ "type": "object", "additionalProperties": false }arguments 4 linessearch_companies open 1h ago
Search employers by their working-hours policy. This answers "which companies offer a 4-day week" style questions at the employer level, where the policy actually lives, rather than per listing. The same schedule_type semantics as search_jobs apply: "compressed_week" is a 4x10 and is not a 4-day week. Two location facts are separate and are often confused. country is where the employer is based. hires_worldwide is whether it accepts applicants from any country. remote_level is its office-presence policy, and a fully-remote employer can still hire in one country only. Each result carries the employer's name, slug, url, schedule type, full-time hours, remote level and count of open roles. get_company takes the slug and returns the full profile. Paging works as in search_jobs: at most 25 employers per call, with page, page_size, returned, total_matching, has_more and next_page.
{ "type": "object", "properties": { "page": { "type": "integer", "description": "1-based page number. Default 1, maximum 200." }, "sort": { "type": "string", "description": "Result order. One of score (work-life score, highest first), jobs (most open roles), alphabetical, newest. Omit for the site's default order." }, "limit": { "type": "integer", "description": "Results per page. Default 10, maximum 25." }, "query": { "type": "string", "description": "Free-text search over company name and website." }, "country": { "type": "string", "description": "Country name. This is where the employer is based, which is a different question from where it will hire — see hires_worldwide." }, "has_jobs": { "type": "boolean", "description": "Only employers with at least one live listing." }, "remote_level": { "type": "string", "description": "The employer's office-presence policy. One of fully-remote, hybrid, onsite. Independent of hires_worldwide: a fully-remote employer can still hire in one country only." }, "schedule_type": { "type": "string", "description": "Filter by the employer's schedule policy, e.g. 4_day_week." }, "hires_worldwide": { "type": "boolean", "description": "Only employers that accept applicants from any country." } }, "additionalProperties": false }arguments 42 linesget_job unknown never probed
Fetch one live job listing in full by its slug, as returned by search_jobs. Returns the complete description, the schedule type and what it means, weekly hours, work arrangement and locations, category, seniority, contract type, required skills, acceptable timezones where the employer listed them, visa sponsorship where the employer stated one, the work-life score, and salary ONLY where the employer published one — we never estimate a salary. A very long description is truncated on a paragraph boundary; when that happens the response says so and gives the url of the full listing. Applying happens on the job's page on 4dayweek.io, which the url field points to. apply_method says what a person finds there: "external" means the page hands off to the employer's own application form, "on_page" means they apply on 4dayweek.io itself. There is no separate employer link in this response, and constructing one is not possible from it.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "The slug, as returned by the matching search tool." } }, "additionalProperties": false }arguments 13 linesget_company unknown never probed
Fetch one employer's full profile by slug, as returned by search_companies. Returns the schedule policy and what it means, full-time weekly hours, the office-presence policy and whether the employer hires worldwide, benefits, industry, headcount, founding year, the work-life score, the count of open roles, and the employer's own website. Where the employer has published them, it also returns which day is off, vacation days, fully-paid parental leave weeks for both parents, a no-meeting day, and verified work-life awards with the year and a proof url for each. Where the employer's schedule is sourced from a public announcement, four_day_reference_url is that source.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "The slug, as returned by the matching search tool." } }, "additionalProperties": false }arguments 13 linessearch_jobs unknown never probed
Search live job listings with genuinely better working hours. Every listing carries an explicit schedule_type, so you never have to infer one: - "4_day_week": 36 hours or less, 100% salary. The ONLY type that is reduced hours at full pay. - "4_day_week_pro_rata": four days at pro-rata (reduced) pay. - "9_day_fortnight", "half_day_fridays", "rotating_4_day", "summer_fridays", "part_time": other genuinely reduced-hours patterns. - "compressed_week": a 4x10. The SAME 40 hours in four days. NOT a 4-day week, and never to be described as one. - "flexible_hours", "unlimited_pto", "generous_pto", "flex_fridays", "no_meeting_days", "generous_parental_leave", "best_place_to_work": a full working week with a flexibility or leave policy. To answer "find me a 4-day week job", pass schedule_type="4_day_week". Passing nothing returns all reduced-hours AND flexibility listings, which is usually broader than the user meant. On locations: a job with no location restriction is worldwide-remote, so it matches ANY country filter. A large result count for a country therefore does not mean those roles are based there. Read each result's "locations" and "work_arrangement" before saying a job is in a particular place. Results can also be narrowed by seniority (level), by skill/technology slugs, by a minimum work-life score and by how recently the employer posted. Paging: a response returns at most 25 jobs and carries page, page_size, returned, has_more and, when another page exists, next_page. total_matching is the size of the whole match set. With a query it counts full-text matches over title AND description, so a job can be counted for a word that appears only in its body. Each result carries the job's url on 4dayweek.io and its slug; get_job takes that slug and returns the full listing.
{ "type": "object", "properties": { "page": { "type": "integer", "description": "1-based page number. Default 1, maximum 200." }, "level": { "type": "string", "description": "Seniority. One of entry, mid, senior, lead, executive." }, "limit": { "type": "integer", "description": "Results per page. Default 10, maximum 25." }, "query": { "type": "string", "description": "Free-text search over job title and description." }, "skills": { "type": [ "null", "array" ], "items": { "type": "string" }, "description": "Skill, technology or tool SLUGS, lowercase and hyphenated, e.g. react, python, customer-support. A job matches if it carries ANY of them." }, "country": { "type": "string", "description": "Country name, e.g. United Kingdom or United States. Matches jobs with an office in that country AND remote jobs open to it — including worldwide-remote roles, which match every country. Check each result's locations field before describing a job as being IN that country." }, "category": { "type": "string", "description": "Job category, e.g. engineering, product, design, marketing, sales, data, devops, finance, hr, legal, operations, security, content, customer-success." }, "schedule_type": { "type": "string", "description": "Filter by schedule type. Use 4_day_week for a genuine 4-day week at full pay. compressed_week is a 4x10 and is NOT a 4-day week." }, "work_arrangement": { "type": "string", "description": "One of remote, hybrid or onsite." }, "posted_after_days": { "type": "integer", "description": "Keep only jobs the employer posted within this many days, 1 to 365." }, "min_work_life_score": { "type": "integer", "description": "Keep only jobs whose work-life score is at least this, on a 0-100 scale. The site's own filter offers 55, 70 and 85. See /methodology for how it is calculated." } }, "additionalProperties": false }arguments 56 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida8933326f6e185b5.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a8933326f6e185b5/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a8933326f6e185b5?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.