# Today's Best Build: VetCV MCP **Report Date**: 2026-04-28 **Coverage**: 2026-04-28T00:00:00+08:00 – 2026-04-28T23:59:59+08:00（UTC） **Status**: ok ## Today's Best Build: VetCV MCP **One-liner**: An open-source MCP server that lints CVs against real ATS parsers and surfaces actionable fixes instead of fake scores. **Why Now**: Most ATS scanners invent a 0–100 score with no basis in reality. Recruiters at three companies confirmed no universal score exists. As AI agents handle more job applications, a transparent, parser-level linting tool is the only reliable way to optimize a CV. **Evidence**: - Existing ATS scanners fabricate scores, confirmed by recruiters at three companies on different ATS platforms. _(signal #6473)_ - GitHub Copilot's shift to usage-based billing shows AI tool costs are becoming granular and unpredictable, making free open-source tools more attractive. _(signal #6348)_ - Most users treat AI like Google search, leading to poor results; structured tools like CV linting provide deterministic, auditable value. _(signal #6493)_ **Fastest Validation**: Deploy the MCP server on a public endpoint and have 5 real job seekers test it against their own CVs, measuring the number of actionable lint items produced per vendor. **Counter-view**: Unlike Jobscan which uses generic keyword matching, VetCV lints against the actual parsers of Workday, Greenhouse, Lever, Taleo, and iCIMS — a difference confirmed by recruiters who say keyword matching misses the real parsing issues. ## Top Signals ### I built an open-source MCP server that lints a CV against 5 real ATS parsers **Source**: devto | **Metric**: Comments: 1 Directly addresses the #1 problem in job applications: fake ATS scores. Built on the emerging MCP protocol, making it immediately usable by any AI agent. ### GitHub Copilot is moving to usage-based billing **Source**: hackernews | **Metric**: Score: 668 / Comments: 488 A paradigm shift in AI tool pricing. Developers now face unpredictable costs, driving interest in self-hosted or transparent alternatives. ### Show HN: Waiting for LLMs Suck – Give your user a game **Source**: hackernews | **Metric**: Score: 7 / Comments: 4 Indicates user patience is becoming a product differentiator. Any AI tool (including VetCV) can benefit from filling latency with engaging micro-interactions. ### I Forgot to Code **Source**: hackernews | **Metric**: Score: 8 Highlights the over-reliance on AI code generation and the erosion of fundamental skills. Tools that provide deterministic, transparent feedback are increasingly valued. ## Discovery ### Q1. What solo-founder products launched today? **Signal**: Show HN: Waiting for LLMs Suck – Give your user a game (HN score 8.5) **Analysis**: Solo founder launched a game to entertain users during LLM latency, receiving strong positive feedback. **Takeaway**: Ship a similar game to reduce perceived wait time and improve user experience. **Counter-view**: Devin for Terminal (id=6311) launched same day but targets developers directly, not end users. ### Q2. Which search terms or discussion threads are suddenly rising? **Signal**: GitHub Copilot usage-based billing discussions (HN score 7.8, devto score 8.0) **Analysis**: Multiple threads on HN and devto discuss the shift from flat-fee to metered billing for Copilot. **Takeaway**: Watch for potential migration to alternatives like Cursor or Supermaven. **Counter-view**: Copilot still has strong brand loyalty; many developers may stay despite complaints. ### Q3. Which open-source projects are growing fast but lack a commercial offering? **Signal**: Localsend: open-source cross-platform AirDrop alternative (HN score 6.7) **Analysis**: Growing fast as a privacy-focused file sharing tool with no commercial tier. **Takeaway**: Build a commercial offering on top, e.g., enterprise sync or managed deployment. **Counter-view**: AirDrop is deeply integrated in Apple ecosystem; hard to replace for most users. ### Q4. What are developers complaining about today? **Signal**: GitHub Copilot moves to usage-based billing (HN score 7.4, 7.8) **Analysis**: Developers complain about cost increase and complexity of new billing model. **Takeaway**: Pass on building Copilot-dependent products; monitor alternatives and pricing strategies. **Counter-view**: Some power users may benefit from usage-based model if they code less. ## Tech Radar ### Q5. What is the fastest-growing developer tool this week? **Signal**: Pgrx: Build Postgres Extensions with Rust (HN score 7.9) **Analysis**: Fast-growing developer tool for building Postgres extensions in Rust, highly upvoted on HN. **Takeaway**: Build a product leveraging Pgrx, e.g., custom indexing extensions or analytical functions. **Counter-view**: Rust learning curve may limit adoption compared to C-based extensions. ### Q6. Which AI models, frameworks, or infrastructure deserve attention? **Signal**: XiaomiMiMo/MiMo-V2.5-Pro (HuggingFace score 6.5) and IgnitionRAG (ProductHunt score 7.2) **Analysis**: New model from Xiaomi and a RAG framework IgnitionRAG launched; both show strong initial interest. **Takeaway**: Deploy MiMo for edge devices or integrate IgnitionRAG for document Q&A in production. **Counter-view**: MiMo may be quickly outdated; IgnitionRAG faces strong competition from LangChain and LlamaIndex. ### Q7. Which platforms, products, or technologies are declining? **Signal**: The Utter Failure of the JS Error (devto score 5.2) **Analysis**: JavaScript error handling patterns are being criticized as outdated and unreliable. **Takeaway**: Defer relying on JS errors; consider Rust or safer languages for critical systems. **Counter-view**: JavaScript is still dominant; error handling improvements are on the horizon. ### Q8. What tech stacks are successful Show HN / GitHub projects using? **Signal**: Pgrx uses Rust; Localsend likely uses Flutter/Dart (based on cross-platform nature) **Analysis**: Successful projects are using modern languages: Rust for performance and Flutter for cross-platform reach. **Takeaway**: Consider Rust for performance-critical backends or Flutter for rapid, cross-platform frontends. **Counter-view**: Python still dominates for AI projects on Show HN. ## Competitive Intel ### Q9. What pricing and revenue models are indie developers discussing? **Signal**: What is Cursor AI’s business model? (devto score 5.3) and Copilot billing discussion (HN 7.4) **Analysis**: Indie developers are evaluating AI tool pricing, especially the shift from flat-fee to usage-based. **Takeaway**: Build a usage-based tier or flat-fee hybrid for your AI product; offer free tier for adoption. **Counter-view**: Free tiers may be unsustainable; many startups fail on pricing. ### Q10. What migration, replacement, or "X is dead" trends are emerging? **Signal**: Localsend as open-source AirDrop alternative (HN score 6.7) **Analysis**: Indicates a trend toward open-source replacements for proprietary services like AirDrop. **Takeaway**: Replace other proprietary services with open-source alternatives; focus on privacy. **Counter-view**: Open-source often lacks the polish and seamless integration of Apple's ecosystem. ### Q11. Which old projects or legacy needs are suddenly coming back? **Signal**: L123: Lotus 1-2-3 style spreadsheet (HN 5.9) and resurgence of RF engineering (HN 5.8) **Analysis**: Vintage spreadsheet UX and RF engineering are making comebacks, driven by terminal nostalgia and IoT. **Takeaway**: Build a modern terminal-based spreadsheet or low-cost RF tools for hobbyists. **Counter-view**: Spreadsheet market is saturated; RF requires deep hardware knowledge. ## Trends ### Q12. What are the highest-frequency keywords this week? **Signal**: Frequency analysis of 126 signals shows 'Copilot' (4 mentions), 'AI' (10+), 'open-source' (6), 'usage-based' (3) **Analysis**: Copilot billing and AI tooling discussions dominate, with open-source projects also prominent. **Takeaway**: Watch AI tool pricing trends and open-source to commercial transitions. **Counter-view**: Frequency analysis may be skewed; deeper NLP analysis needed for precision. ### Q13. Which concepts are cooling down? **Signal**: MEMORY.md Every Turn? That’s Noise, Not Memory. (devto score 7.0) **Analysis**: The concept of persistent memory in AI chat is being criticized as noise, indicating cooling hype. **Takeaway**: Pass on building around unwieldy memory; focus on explicit context mechanisms. **Counter-view**: Some users value long-term memory; Apple Intelligence may push it mainstream. ### Q14. Which new terms or categories are emerging from zero? **Signal**: MCP server (id=6473) and A2A stack (id=6480) mentioned in devto posts **Analysis**: Model Context Protocol (MCP) and Agent-to-Agent (A2A) are new categories gaining traction. **Takeaway**: Build interoperability tools leveraging MCP and A2A standards. **Counter-view**: Standards may shift; early adoption risks lock-in to evolving protocols. ## Action ### Q15. What is most worth spending 2 hours on today? **Signal**: Show HN: Waiting for LLMs Suck (HN score 8.5) **Analysis**: A game that entertains users during LLM latency was well-received, showing market need. **Takeaway**: Build a simple web game that runs while waiting for API calls; reuse as a library. **Counter-view**: Users might prefer to switch tabs; game might not retain attention. ### Q16. Why not the other two candidate directions? **Signal**: MCP server (id=6473 score 8.8) and Localsend (id=6526 score 6.7) **Analysis**: MCP server is niche and technical; file sharing is competitive. Game has immediate emotional payoff and viral potential. **Takeaway**: Pass on MCP server and file sharing for now due to complexity and competition. **Counter-view**: MCP could become infrastructure; file sharing benefits from network effects. ### Q17. What is the fastest validation step? **Signal**: Common validation pattern: send a landing page to HN/Product Hunt **Analysis**: Create a simple page describing the waiting game and collect emails to gauge interest. **Takeaway**: Launch a landing page within 2 hours with a signup form; share on HN and devto. **Counter-view**: No-code tools might be faster but less flexible for customization. ### Q18. What product should this become over the weekend? **Signal**: Show HN post describes a game that users play while LLMs load **Analysis**: The concept can become a browser extension that injects a game during API calls. **Takeaway**: Ship a minimal Chrome extension by Sunday that works with OpenAI and Anthropic APIs. **Counter-view**: Browser extension distribution is hard; alternative: web app with a loading screen overlay. ### Q19. How should initial pricing and packaging look? **Signal**: Common indie pricing discussions (devto score 5.3) and Copilot's billing model **Analysis**: Freemium with free basic games and paid customization aligns with indie SaaS patterns. **Takeaway**: Set free tier with 5 games, pro at $5/month for unlimited games and themes. **Counter-view**: Enterprise may want self-hosted; offer $100/year per seat for that. ### Q20. What is the strongest counter-view? **Signal**: LLM latency decreasing over time **Analysis**: As models get faster, the need for waiting-room entertainment diminishes. **Takeaway**: Consider pivoting to productivity tools during waits, like Quick Note or Jumpbrain. **Counter-view**: Latency will always exist; inference optimization is still a growing field. ## Action Plan **2-Hour Build**: Fork the existing cv-mirror-mcp repo, set up an Express.js wrapper around the three MCP tools, and host it on a free Railway tier with a simple /health endpoint. **Why This Wins**: It scratches a real itch: every job seeker needs their CV parsed correctly. It's also a perfect MCP showcase that any agent can adopt, giving it viral potential in the developer community. **Why Not Alternatives**: - Building another 'AI wrapper' for resume writing is crowded and low-signal. - A game to fill LLM wait times is entertaining but not a recurring need like job applications. - A security tool like GTFOBins is mature; entering that space requires deep expertise. **Fastest Validation**: Post a Show HN with the hosted MCP endpoint and ask users to paste their issue logs. Measure conversion by how many users run the linter twice. **Weekend Expansion**: Add a web-based file upload with live lint results, integrate with LinkedIn profile import, and add a 'send to recruiter' share link.