Take Friday Off
REMOTE · TAKEFRIDAYOFF.COM
Wellness product development in Australia: TGA pathways, guides, case studies, a readiness check.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 8557 tokens (~80/item across 106 items; 17 tools + 89 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
- Structured output schemas are declared (82% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Resource “faq” now points somewhere else: tfo://faq → tfo://page/faq security
- Resource “glossary” now points somewhere else: tfo://glossary → tfo://page/glossary security
- 20 Nov 26 +1
- Resource “faq” now points somewhere else: tfo://faq → tfo://page/faq security
- Resource “glossary” now points somewhere else: tfo://glossary → tfo://page/glossary security
- 19 Nov 26 0
- Resource “faq” now points somewhere else: tfo://faq → tfo://page/faq security
- Resource “glossary” now points somewhere else: tfo://glossary → tfo://page/glossary security
- 18 Nov 26 +1
- Resource “faq” now points somewhere else: tfo://faq → tfo://page/faq security
- Resource “glossary” now points somewhere else: tfo://glossary → tfo://page/glossary security
- 17 Nov 26 0
- Resource “faq” now points somewhere else: tfo://faq → tfo://page/faq security
- Resource “glossary” now points somewhere else: tfo://glossary → tfo://page/glossary security
- 16 Nov 26 +1
- Resource “faq” now points somewhere else: tfo://faq → tfo://page/faq security
- Resource “glossary” now points somewhere else: tfo://glossary → tfo://page/glossary security
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 72
First indexed and scored.
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 21 Nov 2026 · Probed https://takefridayoff.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=takefridayoff.com | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 147854a5171e4dba1380f4a82f8d9308 |
| SANs: takefridayoff.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of takefridayoff.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| takefridayoff.com. | No DS | 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://takefridayoff.com/mcp | Verified | 200 | |
| http (plaintext) | http://takefridayoff.com/mcp | HTTPS enforced | 301 | https://takefridayoff.com/mcp |
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 →
tfo_case_studies Find case studies ~172
Case studies from five years of Take Friday Off project records, strongest first: what was built and the result, with the client named where they have reviewed Take Friday Off publicly or already appear on the site. Filter by words (a format, ingredient, pathway or client, e.g. "capsule", "affron", "cosmetic", "Arxi") and by kind. Each result links to its full story, which tfo_get_page reads.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | established (established brands), first (first launches), own (the founder’s own brands), soon (in production, shipping soon) |
| limit | integer | – | – |
| query | string | – | Words that must all appear in the story: client, title, brand, what was built, manufacturing or results |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| kind | string | yes | – |
| query | string|null | – | – |
| results | array | yes | – |
No examples provided.
tfo_claims_check Check ad and claims copy ~337
Check the words a brand wants to use for a supplement in Australia (an ad, a product page, a social post, an influencer caption, the words on the pack) against the TGA's advertising rules as takefridayoff.com/guides/tga-advertising sets them out. Flags "TGA approved", safe or free of side effects, guaranteed or miraculous, serious diseases (restricted and prohibited representations), testimonials and the endorsements the Code excludes, research claims, exaggeration, comparisons, free samples, and the statement an ad must carry. Each flag gives the words found, why, the guide's own words and the link. Foods and cosmetics are read against their own rules. It reads words, not meaning: no flags is not clearance, and it is not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Where it runs: ad_or_website (the default), online_store (a page that sells it), social_post (the brand's own post), influencer_post (someone else posting for the brand), label_or_pack (the words on… |
| copy | string | yes | The words to check: the ad, the product page text, the caption, or the claims on the pack |
| paid | boolean | – | Whoever is posting is paid or given anything of value for it (cash, free product, discounts, gifts) |
| pathway | string | – | What the product is: listed_medicine (AUST L), assessed_listed_medicine (AUST L(A)), food, cosmetic, or unknown (treated as a medicine; tfo_pathway_check can settle it) |
| Name | Type | Req | Description |
|---|---|---|---|
| assumed | array | – | – |
| basis | object | – | – |
| channel | string | – | – |
| checkedOn | string|null | – | – |
| counts | object | yes | – |
| disclaimer | string | yes | – |
| draft | boolean | – | – |
| findings | array | yes | – |
| limits | string | yes | – |
| missing | array | yes | – |
| nextStep | string | – | – |
| pages | array | yes | – |
| pathway | string | – | – |
| summary | string | yes | – |
No examples provided.
tfo_define Define a regulatory term ~146
Define a term from the takefridayoff.com glossary of Australian supplement, food and cosmetic regulation (ARTG, AUST L, sponsor, permitted indications, TGO 116, GMP, FSANZ, AICIS and more): its other names, the definition, its link, the guide section that covers it in depth and the related terms. Finds a term by its name, an abbreviation or its long form; without a term, lists them all.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | – | The term, abbreviation or long form: "AUST L", "Australian Register of Therapeutic Goods", "MOQ", "TGO 116". Leave out to list every term. |
| Name | Type | Req | Description |
|---|---|---|---|
| checkedOn | string|null | – | – |
| count | number | yes | – |
| disclaimer | string | yes | – |
| draft | boolean | – | – |
| found | boolean | yes | – |
| glossary | string | yes | – |
| matches | array | yes | – |
| query | string|null | – | – |
| term | object|null | – | – |
| terms | array | – | – |
No examples provided.
tfo_faq Search the FAQ ~94
Answer common questions about how TFO works, who it is for, formats, pricing model and location, plus the questions on its service, pathway and guide pages (TGA listing, manufacturing, formulation). Each answer carries the page it comes from. Optional free-text query filters the list.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional words the question or answer must contain, e.g. "pricing" or "TGA" |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string|null | yes | – |
| results | array | yes | – |
No examples provided.
tfo_get_founders Get founder ~34
Gabriel Perera, Founder and Managing Partner: role, summary, career and full bio, plus the team line.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tfo_get_page Read a page ~190
Read a Take Friday Off page in full, as Markdown with absolute links: a service, pathway, format or guide page (with its questions, case studies and sources), a case study (/work/<slug>), a note (/notes/<slug>), or a core page (/, /system, /work, /about, /partner, /contact). Give a URL, a path or a slug, and optionally one section by its heading words. With no page, returns the list of pages.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | – | URL, path or slug: "/guides/tga-approval", "tga-approval", "https://takefridayoff.com/skincare", "/work/everleanbody-saffron-capsule" |
| section | string | – | Optional: one section by its heading words or anchor, e.g. "fees" or "sunscreens" |
| Name | Type | Req | Description |
|---|---|---|---|
| draft | boolean | – | – |
| markdown | string | – | – |
| pages | array | – | – |
| title | string | – | – |
| type | string | yes | – |
| updated | string|null | – | – |
| url | string | – | – |
No examples provided.
tfo_get_positioning Get positioning ~51
Return Take Friday Off’s positioning as it publishes it: what it is, its brand line, mission, vision and USP, and its key figures, each with the context it must be quoted with.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tfo_label_check Check a draft label ~223
Check the text of a draft label for a listed medicine in Australia against TGO 116, as takefridayoff.com/guides/supplement-labelling sets it out: each active ingredient with its quantity, the dosage form, the pack quantity, the AUST L number, the batch and expiry with their identifiers, storage, the sponsor and its contact, warnings under their heading, directions and the indications, with declared substances, the sugar-alcohol statement and the PO box rule. Then flags the words a label can't use ("TGA approved", safe, guaranteed). Each item quotes the guide with its link. It reads words, not the artwork, so layout, text size and placement are not checked. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | The label's text, every panel: the name, actives and quantities, directions, warnings, storage, batch and expiry, the sponsor |
| pathway | string | – | listed_medicine (AUST L, the default) or assessed_listed_medicine (AUST L(A)) |
| Name | Type | Req | Description |
|---|---|---|---|
| assumed | array | – | – |
| basis | object | – | – |
| checkedOn | string|null | – | – |
| claims | array | yes | – |
| counts | object | yes | – |
| disclaimer | string | yes | – |
| draft | boolean | – | – |
| items | array | yes | – |
| limits | string | yes | – |
| nextStep | string | – | – |
| pages | array | yes | – |
| pathway | string | – | – |
| summary | string | yes | – |
No examples provided.
tfo_launch_plan Plan a product launch ~643
One plan for launching a wellness product in Australia: the regulatory pathway it is likely on (medicine, food or cosmetic), the five steps from brief to shelf (Discover, Design, De-risk, Deliver, Drive) with what each step delivers and what the brand decides, how long comparable launches took and what could slow this one, the TGA's fees for a first listing when it is a medicine, the closest case studies, and the call. Runs the pathway check, the timeline and the fees tool together, so every figure and rule is quoted from takefridayoff.com with its link. Pass what is known; the answer says what it assumed. Not legal or regulatory advice, and not a quote.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Where it will sell: direct_to_consumer, pharmacy_and_health_food, or both (for the margin that cost of goods leaves) |
| claims | array | – | What the brand wants to say it does: treat_or_prevent_condition (prevents, cures or relieves a disease, condition or symptom), health_benefit (supports a body function or health: immunity, energy, sl… |
| form | string | – | – |
| formula_proven | boolean | – | The formula has already been proven in samples and trials |
| ingredients | array | – | Notable ingredients: poisons_standard_substance (in Schedule 2, 3, 4 or 8), sports_declared_substance (an added substance on the 2023 World Anti-Doping Prohibited List, dendrobium, methylliberine or… |
| lip_or_tinted_foundation | boolean | – | A lip product or a tinted foundation (these have their own sunscreen exclusion) |
| made_overseas | boolean | – | The product will be made outside Australia |
| meets_sports_food_standard | boolean | – | Made and labelled as a formulated supplementary sports food under Standard 2.9.4 |
| new_ingredient | boolean | – | An ingredient not yet on the TGA's Permissible Ingredients Determination, so it needs its own evaluation first |
| primary_sunscreen | boolean | – | Presented mainly to protect the skin from UV |
| product | string | – | The product in a sentence: "collagen powder for glowing skin", "magnesium gummies for sleep", "SPF 30 tinted moisturiser" |
| retail_price | number | – | The planned retail price in Australian dollars, for the target cost of goods and a first-run budget |
| spf | number | – | The SPF, for a product applied to the skin |
| traditional_food | boolean | – | Has a tradition of use as a food in Australia or New Zealand, in the form presented |
| use | string | – | Swallowed, or applied to the skin or hair |
| Name | Type | Req | Description |
|---|---|---|---|
| assumed | array | – | – |
| basis | object | – | – |
| book_a_time | string | – | – |
| caseStudies | array | yes | – |
| costs | object|null | – | – |
| disclaimer | string | yes | – |
| draft | boolean | – | – |
| fees | object|null | – | – |
| nextStep | string | yes | – |
| pages | array | yes | – |
| pathway | object | yes | – |
| product | string|null | – | – |
| steps | array | yes | – |
| summary | string | yes | – |
| timeline | object|null | – | – |
No examples provided.
tfo_list_services List services ~61
The five steps of Friday Launch Engine™ (Discover, Design, De-risk, Deliver, Drive: what we do, what the client gets, what the client decides), the product formats developed, and the five pillars.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | – |
No output schema declared.
No examples provided.
tfo_pathway_check Medicine, food or cosmetic? ~514
Indicative check of which Australian regulatory pathway a wellness product is likely on: a medicine regulated by the TGA (a therapeutic good), a food under the Food Standards Code, or a cosmetic. Applies the rules on takefridayoff.com/pathways in their order (declared goods, excluded goods, presentation, the food standards, form, and on the skin the claim), with the sunscreen and sports-supplement rules. Pass what is known; the answer states what it assumed and what is still missing. Returns the likely pathway and a confidence, the deciding rule first, each quoted from the page with its link, what that pathway means, and what to confirm. Not legal or regulatory advice.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | – | What the brand wants to say it does: treat_or_prevent_condition (prevents, cures or relieves a disease, condition or symptom), health_benefit (supports a body function or health: immunity, energy, sl… |
| form | string | – | – |
| ingredients | array | – | Notable ingredients: poisons_standard_substance (in Schedule 2, 3, 4 or 8), sports_declared_substance (an added substance on the 2023 World Anti-Doping Prohibited List, dendrobium, methylliberine or… |
| lip_or_tinted_foundation | boolean | – | A lip product or a tinted foundation (these have their own sunscreen exclusion) |
| meets_sports_food_standard | boolean | – | Made and labelled as a formulated supplementary sports food under Standard 2.9.4 |
| primary_sunscreen | boolean | – | Presented mainly to protect the skin from UV |
| product | string | – | The product in a sentence: "collagen powder for glowing skin", "magnesium gummies for sleep", "SPF 30 tinted moisturiser" |
| spf | number | – | The SPF, for a product applied to the skin |
| traditional_food | boolean | – | Has a tradition of use as a food in Australia or New Zealand, in the form presented |
| use | string | – | Swallowed, or applied to the skin or hair |
| Name | Type | Req | Description |
|---|---|---|---|
| assumed | array | – | – |
| basis | object | – | – |
| checkedOn | string|null | – | – |
| confidence | string | yes | – |
| confidenceMeans | string | – | – |
| considered | array | – | – |
| disclaimer | string | yes | – |
| draft | boolean | – | – |
| label | string | yes | – |
| likely | string | yes | – |
| nextStep | string | – | – |
| pages | array | yes | – |
| product | string|null | – | – |
| reasons | array | yes | – |
| sources | string | – | – |
| summary | string | yes | – |
| toConfirm | array | yes | – |
| warnings | array | – | – |
| whatItMeans | array | – | – |
No examples provided.
tfo_readiness_check Readiness check ~199
Score whether a wellness brand is a fit for Take Friday Off (the four questions of takefridayoff.com/partner). Returns a score out of 9, a verdict (strong_fit / not_yet, or incomplete with the questions still to ask), each answer with its points and the next step (for a strong fit, book_a_time: a link to book a call with Gabriel Perera). Call it with no arguments to let the user answer in the interactive card, where the assistant shows one.
| Name | Type | Req | Description |
|---|---|---|---|
| drag | string | – | What is slowing the pipeline |
| role | string | – | Who is asking |
| stage | string | – | Where the brand is: established and growing (scale), ambitious and built and backed to scale (backed), growing without backing or a plan to scale (growing), an idea only (idea) |
| timeline | string | – | When the product needs to be on shelf (months) |
| Name | Type | Req | Description |
|---|---|---|---|
| book_a_time | string | – | – |
| detail | array | yes | – |
| max | integer | yes | – |
| missing | array | – | – |
| next | string | yes | – |
| partner | string | yes | – |
| recommendation | string | yes | – |
| score | integer | yes | – |
| summary | string | yes | – |
| verdict | string | yes | incomplete: not every question is answered yet; ask the ones in missing |
No examples provided.
tfo_request_call Request a call ~186
Send the Take Friday Off team a no-obligation call request for the person: their name, email, brand and what they want to talk about. Use it only when the person asks for a call or agrees to one, since it shares their name and email with the team. Returns a reference and a link (book_a_time) where they can pick a time themselves, with their name and email filled in.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Their brand or organisation, if they have one |
| string | yes | Their email address, for the reply | |
| message | string | yes | What they want to talk about: the product, where it is up to, the timing |
| name | string | yes | The person’s full name |
| revenue | string | – | Where the brand is today, in their words, e.g. "established, growing fast" |
| Name | Type | Req | Description |
|---|---|---|---|
| book_a_time | string | – | – |
| errors | array | – | – |
| mailto | string | – | Only when the request could not be delivered: an email draft the person can send instead |
| next | string | – | – |
| ok | boolean | yes | – |
| reference | string | – | Quote it if the person follows up by email |
| test | boolean | – | True when the email is at a domain reserved for examples (example.com, .test): the request was checked but nothing was sent |
No examples provided.
tfo_search Search Take Friday Off ~181
Search everything Take Friday Off publishes about developing wellness products in Australia: its service, pathway, format and guide pages (TGA listing and its fees, listed medicines, medicine vs food vs cosmetic, managed manufacturing, formulation, skincare and sunscreens, capsules and tablets, powders), their questions and answers, the case studies and the notes. Returns the best passages, each with a link to the exact section to cite and the date the page was last reviewed. Read a whole page with tfo_get_page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | What to look for, in plain words: "TGA listing fees", "is a protein powder a food", "SPF moisturiser cosmetic", "capsule case study" |
| type | string | – | Limit to pages, questions and answers (faq), case_studies or notes |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
tfo_send_brief Send a product brief ~494
Turn the founder's answers into the product brief Take Friday Off works from, with the launch plan attached (the likely pathway, the timeline, the TGA fees and the costs), and send it to the team as an enquiry. Interview the person first: the product, who it is for, the format, what it should do, the ingredients, the price and channel, the volume, the timing and where it is today. Call without confirm to get the brief and show it to them; only when they have read it and said to send it, call again with the same answers and confirm: true. Sending shares their name and email with Take Friday Off, who reply within one business day.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Their brand or organisation, if they have one |
| budget | string | – | The budget, if they want to share it |
| channel | string | – | Where it will sell |
| claims | array | – | The same claims as categories, for the plan's pathway |
| claims_wanted | string | – | What it should do, or what they want to say about it, in their words |
| confirm | boolean | – | true only after the person has read the brief and said to send it |
| customer | string | – | Who it is for |
| string | yes | Their email address, for the reply | |
| form | string | – | The format (for the plan) |
| format_detail | string | – | The format in their words: "60 capsules in a glass jar", "200 g pouch" |
| ingredients | string | – | The ingredients they want, or have in mind |
| launch | string | – | When they want to launch |
| name | string | yes | The person’s full name |
| notes | string | – | Anything else the team should know |
| product | string | yes | The product in a sentence: "a magnesium and chamomile capsule for sleep" |
| retail_price | number | – | The planned retail price in Australian dollars |
| revenue | string | – | Where the brand is today, in their words |
| stage | string | – | Where the product is today: an idea, a formula, a product on the market to improve |
| use | string | – | Swallowed, or applied to the skin or hair (for the plan's pathway) |
| volume | string | – | The first order and the yearly volume they expect |
| Name | Type | Req | Description |
|---|---|---|---|
| book_a_time | string | – | – |
| brief | string | – | The brief as the team receives it |
| errors | array | – | – |
| mailto | string | – | Only when the brief could not be delivered: an email draft the person can send instead |
| next | string | – | – |
| ok | boolean | yes | – |
| plan | array | – | The plan lines attached to the brief |
| reference | string | – | Quote it if the person follows up by email |
| sent | boolean | – | – |
| test | boolean | – | True when the email is at a domain reserved for examples: checked, not sent |
No examples provided.
tfo_tga_fees What will the TGA charge? ~458
The TGA's fees for a listed medicine in Australia (2026–27), added up for a plan: the listing application, the annual charge for each year on the market, variations, requests for new indications, new ingredients by application level (IN1 to IN4, or a range when the level isn't known), assessed listings (AUST L(A)) by category and GMP clearances for overseas factories. Every amount is read from the fee table on takefridayoff.com/guides/tga-approval (and /guides/assessed-listed-medicines) and quoted with its link, with the rules on the annual charge's exemption. TGA fees only: development, evidence and manufacturing are not included.
| Name | Type | Req | Description |
|---|---|---|---|
| assessed | array | – | One entry per assessed listed medicine (AUST L(A)), by application category: L(A)1 for a medicine identical to one already listed as assessed, L(A)2 for an equivalent medicine or one evaluated from a… |
| medicines | integer | – | How many listed medicines (AUST L) to list; each pays the listing application and its own annual charge. Default 1, or 0 when only assessed is given. |
| new_indications | integer | – | Requests to add a new indication to the TGA's permitted list. Default 0. |
| new_ingredients | array | – | One entry per ingredient not yet permitted for listed medicines, by application level: IN1, IN2, IN3 or IN4, or "unknown" for a range. Default none. |
| overseas_sites | integer | – | Overseas manufacturing sites that need a TGA GMP clearance (per manufacturer, site and sponsor). Default 0. |
| variations | integer | – | Variations to an existing listing (a change to the product after it is listed). Default 0. |
| years | integer | – | Financial years of the annual charge to include for each medicine, counting each year it is on the ARTG once it has had turnover. Default 1, the first year it sells. |
| Name | Type | Req | Description |
|---|---|---|---|
| annualNote | string|null | – | – |
| annualPerYear | number|null | – | – |
| assumed | array | – | – |
| basis | object | – | – |
| checkedOn | string|null | – | – |
| disclaimer | string | yes | – |
| draft | boolean | – | – |
| financialYear | string|null | – | – |
| gmpNote | string|null | – | – |
| lines | array | yes | – |
| nextStep | string | – | – |
| notIncluded | string|null | – | – |
| pages | array | yes | – |
| paymentNote | string|null | – | – |
| range | object|null | – | – |
| schedule | array | yes | – |
| summary | string | yes | – |
| total | number|null | – | – |
| totalText | string | yes | – |
No examples provided.
tfo_timeline How long will it take? ~334
Indicative timeline for developing a wellness product in Australia, from the records and the stages on takefridayoff.com/guides/supplement-development-timeline: what comparable products took (design to production order, or signed brief to dispatch), the six stages a listed medicine is built in, and which of the known hold-ups apply to this product (a new ingredient and the TGA's evaluation windows, a pathway not yet settled, a formula not yet proven, an overseas factory). Every figure is quoted from the page with its link. Not a quote or a promise for a particular product.
| Name | Type | Req | Description |
|---|---|---|---|
| clock | string | – | Which measure to give: design_to_production_order (the formula to the first production order) or brief_to_dispatch (the signed brief to the first batch leaving for the 3PL, manufacturing included; th… |
| formula_proven | boolean | – | The formula has already been proven in samples and trials (it runs on the line, tastes right, is stable) |
| made_overseas | boolean | – | The product will be made outside Australia (the site then needs a TGA GMP clearance) |
| new_ingredient | boolean | – | An ingredient that is not yet on the TGA's Permissible Ingredients Determination, so it needs its own evaluation first |
| pathway | string | – | listed_medicine (a TGA-listed medicine), food, cosmetic, or unknown (not settled yet; tfo_pathway_check can help) |
| product | string | – | The product in a sentence: "magnesium capsule for sleep", "probiotic powder in sachets" |
| Name | Type | Req | Description |
|---|---|---|---|
| assumed | array | – | – |
| basis | object | – | – |
| checkedOn | string|null | – | – |
| clock | string | yes | – |
| clockMeans | string | – | – |
| disclaimer | string | yes | – |
| draft | boolean | – | – |
| faq | object|null | – | – |
| holdups | array | yes | – |
| listingNote | string|null | – | – |
| newIngredientWindows | array | – | – |
| nextStep | string | – | – |
| pages | array | yes | – |
| pathwayNote | string|null | – | – |
| positioning | string|null | – | – |
| product | string|null | – | – |
| range | string|null | – | – |
| rangeDays | object|null | – | – |
| records | array | yes | – |
| stages | array | yes | – |
| summary | string | yes | – |
No examples provided.
How do I install the Take Friday Off MCP server?
Take Friday Off is a hosted endpoint at https://takefridayoff.com/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 · takefridayoff.com
claude mcp add --transport http com-takefridayoff-mcp 'https://takefridayoff.com/mcp'
What is the Take Friday Off MCP server?
Take Friday Off is an MCP server listed in the public MCP registry as com.takefridayoff/mcp. Wellness product development in Australia: TGA pathways, guides, case studies, a readiness check. This page covers its hosted endpoint (https://takefridayoff.com/mcp).
Is the Take Friday Off MCP server safe to use?
Take Friday Off scores 75 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 Take Friday Off MCP server expose?
Take Friday Off exposes 17 tools: tfo_search, tfo_get_page, tfo_pathway_check, tfo_launch_plan, tfo_claims_check, and 12 more. Their descriptions and schemas cost roughly 4,317 tokens of context every time the server is loaded.
Does the Take Friday Off MCP server require authentication?
No. We connected to Take Friday Off without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Take Friday Off MCP server still maintained?
Take Friday Off is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Take Friday Off MCP server?
VerifyMCP ran 14 checks on Take Friday Off, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.