Val Town Shuts Jan 10. Profile Search Finds Vail, Not Its MCP Builders

If you hire engineers who build agents, MCP servers and cron automations, one of the few places their work was public, running and signed with the author's name is closing. On Nov 10, 2026, Steve Krouse announced that Val Town is winding down. It goes read-only on Dec 10 and dark on Jan 10, 2027, and none of it appears in professional profile search.

What is happening to Val Town, and when?

Val Town is shutting down in four stages, and the one that matters to sourcers is Dec 10, when the platform goes read-only. After that, profiles stay visible but nobody can edit them. On Jan 10 the remaining services stop.

Krouse's stated reason was blunt: "we couldn't compete in the cloud computing space." Cofounder Tom MacWright was plainer still, calling winding down "industry lingo for shutting down." Krouse also thanked investor Dan Levine by name. The company published migration guides for Cloudflare, Vercel, Netlify and Render.

Data is the wrinkle. Krouse's post carves SQLite and blob storage out of the Dec 10 read-only mode, but at least one migration write-up tells users to inventory their data and plan the export before the read-only cutoff. Either way, builders with real data in their vals face a harder move than those with stateless code, and how they handle it is the first test of who treats their projects as production systems.

Why are public vals a sourcing signal?

Public vals are a sourcing signal because Val Town made code public by default, so the free-tier community's actual working code sat in the open, attached to a username. A val can run as a website, API, MCP server, cron job, agent, Slack bot or email automation.

According to Val Town's docs, only Pro and Business accounts could mark vals private or unlisted. Everyone else shipped in public. That gives you an unfiltered view of the community instead of a curated highlight reel.

The scale was not trivial. In a January 2025 newsletter, the team wrote that "23k of you made 135k vals that've run 214m times." That works out to about 5.9 vals per user on average.

214m

The company also leaned hard into agents before the end. The blog archive shows "Introducing Val Town MCP" (Nov 14, 2025), "Townie v5, powered by Val Town MCP and Claude 4.5" (Jan 22, 2026) and "New focus: Claude Code + Val Town MCP" (May 5, 2026). The platform's last year pointed squarely at the tooling hiring managers now ask for.

Three recent product changes make the signal easier to read:

• Pinned vals. Users can pin vals to feature their best work, much like pinned GitHub repos.
• Universal download. Anyone can download any public val, not just their own.
• GitHub sync. The docs added syncing vals with GitHub, so some builders already have a mirror.

Why can't profile search find Val Town builders?

Profile search can't find Val Town builders because they don't write "Val Town" in their headlines, so the evidence of their work exists only on val.town itself. When I searched Refolk's index of professional profiles for "Val Town," I got 140 matches, and almost none of them were developers.

The top employer among those 140 was Town of Vail, with 18 profiles. Second was the University of Cape Town, with 2. No sampled title belonged to a Val Town builder. The keyword collides with a Colorado ski town and a South African university, and the real users never show up.

The mechanism is simple. Val Town was a tool, like a text editor. Nobody lists their text editor on a profile. What they list is a title ("Software Engineer," "Founder"), and that title says nothing about whether they have shipped a working MCP server this year.

So the Jan 10 shutdown does more than end a hosting product. It removes the only index that connects these people to their work.

Does "MCP server" in a headline mean someone builds them?

Usually not. In Refolk's index, 864 US profiles mention "MCP server" in their headline, but in a 25-profile sample the titles skew heavily toward founders and executives, not hands-on engineers.

864

Look at who those 864 are. The sampled US titles include CTO & Founder, Head of Engineering, COO, VP Digital and a Director of AI Automation. Exactly one was a plain "Software Engineer." Top employers were small companies like Beye.ai, Apra Labs and Birches Health, plus Intel. Treat the sample as a direction, not a percentage, but the direction is clear: the headline keyword is mostly claimed by people who sell, lead or consult on MCP work.

This is why MCP server developers are so slow to hire. You run the obvious search, get a few hundred founders and executives who won't take an IC role, and burn weeks screening people who list the protocol rather than people who ship it. Then the hiring manager asks for someone who has actually deployed an agent with real tool calls, and the pipeline starts over from scratch.

Val Town's public vals flip that problem. Each one shows an author, the code, and version history. If a val is an MCP server that has been edited across months, you are looking at proof of work rather than a claim.

The US-to-UK gap matters too. With 9.6 times as many US headlines claiming MCP work, a UK headline search runs dry fast, which makes proof-of-work sources like public vals worth even more there.

What should you capture before Dec 10?

Capture usernames, val URLs and pinned vals for the builders you care about before Dec 10, while profiles are complete and still editable by their owners. After the freeze, nothing new gets added, and after Jan 10 nothing I found says the pages stay online.

Here is the capture list, in order of value:

1. The top-100 leaderboard. The January 2025 newsletter mentions a val listing the top 100 Val Town users by number of public vals. That is a ready-made ranking of the most prolific builders. Save it.
2. Pinned vals per user. Pinned vals are each builder's own pick of their best work, so they are the fastest way to judge someone.
3. Val type. Tag each builder by what they ship: MCP server, agent, cron, Slack bot, email automation, API. For agent and MCP hiring, those two tags are the shortlist.
4. Edit history. A val updated through 2026 tells you more than one written once in 2024.
5. Linked GitHub accounts. Anyone using GitHub sync already has a mirror, which is your bridge after shutdown.
6. Downloads of standout vals. Since anyone can download any public val, keep a copy of the specific code you plan to reference in outreach.

Start with the names the community already credited. The January 2025 newsletter highlighted Prasham's README generator and calendar app, Vlad's Bluesky Threads to RSS converter, and Inferable's agent integration. Those show the range: developer tooling, consumer utilities, and agent infrastructure.

Remember the blind spot. Paid users could hide their work, so the most commercially serious builders may be the least visible. Your capture list over-represents free-tier users and under-represents paying ones, so check names against other sources before you rank anyone.

The hard part comes next: turning a val.town username into a real person with an email, a GitHub account and a current employer. That is the gap Refolk closes. You describe the builder in plain English and get back matched profiles, not a keyword list that returns ski-town staff.

How do you source them after Jan 10?

After Jan 10, source Val Town builders through the trail their migration leaves on GitHub: new repos with recent first commits whose READMEs mention Val Town or val.run. Treat this as an inference about likely behavior, not a measured pattern, but it is a reasonable one.

Val Town bundled the editor, version control and hosting into one tool. Moving off it means rebuilding all three. The official migration guides point to Cloudflare, Vercel, Netlify and Render, and other hosts are already competing for these users. On Hacker News, Easel.sh's founder posted that he has written guides for moving workloads from Val Town onto Easel.

That is where the signal gets better, not worse. A builder who ports a stateful val to Cloudflare, moves its SQLite data off before the cutoff and wires up deploys has shown they can handle infrastructure, not just prototypes. The shutdown is sorting the community for you.

To source engineers from GitHub activity after the shutdown, look for:

• Repos created between Nov 10, 2026 and Jan 2027 with server code.
• READMEs or commit messages that mention "Val Town," "val.town" or "val.run."
• Deploy configs for Cloudflare, Vercel, Netlify, Render or Easel added in the same window.
• MCP or agent keywords in repo names, topics or package manifests.
• A cluster of small repos from one author, which matches the multi-val habit (about 5.9 per user).

The shutdown is a free technical screen. Whoever migrated a stateful val before Dec 10 already passed it.

Doing this by hand means stitching together GitHub search, commit dates and profile lookups for every candidate. Refolk handles that in a single query: ask for "developers who migrated Val Town projects to Cloudflare in the last two months and build AI agents," and I return the people, not the repos.

Why won't the Feb 1 open-source release save these portfolios?

It won't, because open-sourcing Val Town's platform code is a separate thing from keeping users' public vals and profiles online. Feb 1, 2027 releases the software that ran the service. Nothing I found says the user content will stay accessible after Jan 10.

It is easy to read "open-sourced" and assume the archive survives. Don't. The usernames, the pinned vals and the edit histories that make up the sourcing signal live in the hosted service, and nothing announced says that data ships with the code.

So the real window is Nov 10 to Dec 10 for complete, live profiles, and Dec 10 to Jan 10 for a read-only copy. After that, you are relying on whatever builders chose to move to GitHub themselves.

How should outreach to Val Town builders read?

Outreach should name the specific val you looked at and acknowledge the shutdown, because these builders are in the middle of a forced migration and a generic AI-engineer pitch will feel tone-deaf. One sentence about their actual code beats three about your company.

A few rules for this group:

• Reference the artifact. "Your Bluesky-to-RSS val" lands. "Your impressive background" does not.
• Respect the timing. Many will spend December porting code before the Jan 10 shutdown. Offer a call in January, not this week.
• Ask about the migration. Where they moved and why is a good technical conversation, and a natural screen.
• Don't assume they're job hunting. Val Town shutting down ends a tool, not their employment.

If you want to find developers who build AI agents rather than people who talk about them, the weeks before Dec 10 are a rare chance to see the work and the name side by side.

FAQ

When exactly does Val Town shut down?

New signups and upgrades ended Nov 10, 2026. The platform goes read-only on Dec 10, 2026, though Krouse's post excludes SQLite and blob storage from that read-only mode, so check data plans separately. All remaining services end Jan 10, 2027, and Val Town's own code is open-sourced on Feb 1, 2027. For sourcing, treat Dec 10 as the practical deadline, since that is when profiles freeze.

Can I find Val Town developers by searching professional profiles for "Val Town"?

Not reliably. In Refolk's index, a "Val Town" headline search returned 140 profiles, led by 18 Town of Vail employees and 2 from the University of Cape Town, with no sampled title belonging to an actual Val Town builder. Builders don't list the tool on their profiles, so you need their val.town usernames or their migrated GitHub repos.

Where are Val Town users migrating their code?

Val Town published migration guides for Cloudflare, Vercel, Netlify and Render, and Easel.sh's founder has posted his own guides for moving Val Town workloads onto Easel. Some users also synced vals to GitHub before the shutdown, so their GitHub accounts are the most durable place to find them once val.town goes dark.

Are Val Town builders a good pool for MCP server hiring?

They are one of the better ones, because their public vals show working MCP servers and agents with authorship and version history. By contrast, most of the 864 US profiles in Refolk's index with "MCP server" in the headline belong to founders and executives. Just remember that paid users could hide their vals, so some of the strongest builders may not appear at all.