EOL Desk

What it does

EOL Desk is a calendar of upcoming end-of-life and support-cutoff dates for popular open-source libraries and frameworks. Those facts are already structured (name, version line, date, successor, source). A human needs a scannable board; an agent needs typed actions — not a screenshot of a table and not a private MCP server the human cannot see.

Why WebMCP

The page is the product and the tool host. On load we register list_upcoming_eols, get_eol_detail, and suggest_upgrade_path via document.modelContext.registerTool. ChatGPT's in-app browser or Chrome with WebMCP enabled discovers the same dataset the UI renders. No login wall, no second API for agents.

Better user experience

Without WebMCP, a maintainer either hunts vendor blogs and changelogs by hand, or lets an agent scrape HTML and hope the date is still in the DOM. Both drift. EOL Desk is one board for humans and agents: scan upcoming cutoffs, open a row, or call typed tools for JSON. One source of truth.

People and agents together

Before, asking what dies in 90 days meant the model guessed from training data or scraped pages. Now a person keeps the board honest while ChatGPT or Chrome WebMCP calls list_upcoming_eols, get_eol_detail, and suggest_upgrade_path on the same page. Shared structured facts, no scrape.

How we built it

Greenfield public page on Cloudflare Pages/Workers. On load we feature-detect document.modelContext (fallback navigator.modelContext) and register three tools with the Imperative API against the same dataset as the table: list_upcoming_eols, get_eol_detail, suggest_upgrade_path. Tested with the ChatGPT in-app browser and Chrome 149+ chrome://flags/#enable-webmcp-testing.

Judge access: none needed, public page.

Challenges I ran into

A 48-hour build window. Getting a public GitHub repo up under an existing RonnyKane account. Sorting out the difference between a Devpost portfolio project and actually attaching it to the hackathon. And the fact that WebMCP only works for judges in the ChatGPT in-app browser or Chrome 149+ with the testing flag enabled.

Accomplishments that I'm proud of

Shipped a public live URL, an MIT-licensed repo, and a sub-3-minute demo with all three tools registered on the page.

What I learned

The product is the page as the tool host. Humans and agents need one source of truth, not a scrape.

What's next for EOL Desk

Keep the calendar current and the tools stable through judging (Sep 4-21).

Built With

• cloudflare
• cloudflare-pages
• javascript
• webmcp
• workers