Go Assembly Mutation Testing

Show HN: HyprMCP – Analytics, logs and auth for MCP servers

Show HN: HyprMCP – Analytics, logs and auth for MCP servers Hi HN, my name is Philip, I’m the co-founder of Glasskube and one of the creators of HyprMCP.This project started when we did what everyone was doing — building a remote MCP server and launching it. Building the first local MCP server for testing was quite simple, and we had our first tools ready within a day. The next step was turning that into a production-ready remote MCP server.As we exposed the MCP server to our users, we wanted to authenticate them with our existing authentication methods. We dove deep into authentication. Our approach was to build an auth proxy and plug it in front of our MCP. It took a while to figure out Dynamic Client Registration (DCR) and the OAuth spec, and especially the gaps between existing OIDC IDPs and what LLM clients needed.We thought authentication would be the hard part — but it wasn’t. When we shared the MCP server with a few friendly startups, we realized that different MCP clients behave differently. Especially if something didn't work, it was hard to figure out the root cause. We ended up storing all the raw gRPC method calls to see if the initialization and subsequent requests worked. This is especially useful if you are on a serverless environment with limited debugging functionality, like Cloudflare Workers.Once we solved auth and compatibility, we launched to a small customer base — done, right? Unfortunately, not quite. Technically everything was working, but when we started talking to users, they told us the MCP server didn’t always respond with the right tools for their prompts. We had a working enterprise-grade MCP server — but it wasn’t very smart. After talking to some startup friends, we realized we needed an evaluation layer. That’s when we added prompt analytics — letting us see which prompts triggered which tools and how well they performed. That alone dramatically improved our MCP’s behavior and overall user experience.After building all of this into our proxy, we realized that everyone building a remote MCP was facing the same challenges. So we decided to package it all up and release it to the community.We’re thrilled to launch and open-source HyprMCP. It acts as a proxy that you can plug in front of your MCP server(s) with zero code changes. You get authentication, logging and debugging, prompt analytics, and an MCP connection instructions generator.Under the hood, HyprMCP leverages dynamic Kubernetes Operators (Metacontroller) to automate infrastructure provisioning.On the roadmap: MCP aggregation — combining multiple MCP servers under one single remote URL for large organizations running servers with different lifecycles. All of it without storing end user credentials on the server and connecting the MCP to the organizations existing authentication methods.You can check the project out on GitHub: <a href="https://github.com/hyprmcp/jetski" rel="nofollow">https://github.com/hyprmcp/jetski</a>For testing, we also have a hosted version here: <a href="https://app.hyprmcp.com" rel="nofollow">https://app.hyprmcp.com</a>We even created a demo video on YouTube: <a href="https://www.youtube.com/watch?v=m2-YyfjXap4" rel="nofollow">https://www.youtube.com/watch?v=m2-YyfjXap4</a>We’d love to get your feedback, hear what features are missing, and learn how you’re building and running your own MCP servers.

QA-use-MCP: MCP for E2E testing

Property-Based Testing of OCaml 5's Runtime System [pdf]

Show HN: Dagger.js – A buildless, runtime-only JavaScript micro-framework

Show HN: Dagger.js – A buildless, runtime-only JavaScript micro-framework TL;DR: dagger.js is a buildless, runtime-only micro-framework that plays nicely with native Web Components. It uses HTML-first directives (e.g. +click, +load) so you can ship a page by dropping a single <script> from a CDN—no bundlers, no compile step.Why I built it Modern stacks are powerful but often heavy: bundlers, compile steps, framework DSLs, local CLIs. For internal tools, small apps, and edge/serverless deployments, I wanted something you can view-source, paste into a page, and ship.What it is:Runtime-only: no build or VDOM compile; hydrate behaviors directly on HTML. HTML directives: e.g. +click, lifecycle +load / +loaded / +unload / +unloaded. Zero APIs: dagger.js works in pure declarative mode, modules and directives provide everything you need to build your application. Web-Components-first: works alongside Custom Elements; keep concerns local. Distributed modules: load small, focused script modules via CDN. Progressive enhancement: the page renders without a build step.Use cases:Admin panels & dashboards that don’t warrant a full toolchain Embed widgets, docs-sites with interactive bits Edge/serverless apps where cold start and simplicity matterLinksGitHub: <a href="https://github.com/dagger8224/dagger.js" rel="nofollow">https://github.com/dagger8224/dagger.js</a> Docs/Guide: <a href="https://daggerjs.org" rel="nofollow">https://daggerjs.org</a> Examples: <a href="https://codepen.io/dagger8224/pens" rel="nofollow">https://codepen.io/dagger8224/pens</a>I’d love feedback on edge-cases, and where it breaks. Happy to answer tough questions here.

DeepCodeBench: Real-World Codebase Understanding by Q&A Benchmarking

Taking Buildkite from a side project to a global company

Building your own CLI coding agent with Pydantic-AI

Show HN: Synchrotron, a real-time DSP engine in pure Python

Show HN: Synchrotron, a real-time DSP engine in pure Python Yes, Python.I can already hear the screams from the rafters telling me how terrible of a choice Python is - but in my case, I valued modularity, extensibility, hackability over raw performance. (It was also a challenge to myself to see how far I can get without referencing existing implementations)Synchrotron processes nodes: simple Python classes with typed I/O and a render() method for processing. It can be as concise as 5 lines:<pre><code> class IncrementNode(Node): input: StreamInput output: StreamOutput def render(self, ctx): self.out.write(self.a.read(ctx) + 1) </code></pre> Nodes can then be spawned and linked programmatically or in the graphical editor. Synchrotron handles the rest at runtime. Besides the web UI, you can also interact with the engine via Python, REST, DSL, or standalone TUI.Currently you can build synths, FX chains, MIDI instruments, arpeggiators, controllers, or just mess about with sound :>Editor: <a href="https://synchrotron.thatother.dev/" rel="nofollow">https://synchrotron.thatother.dev/</a> Source: <a href="https://github.com/ThatOtherAndrew/Synchrotron" rel="nofollow">https://github.com/ThatOtherAndrew/Synchrotron</a>It's still experimental (and my first ever shipped project), but I'd love feedback from people who tinker with audio/DSP/live coding. Docs are terrible currently, but that's my next big goal!

Show HN: I've been building an ERP for manufacturing for the last 3 years

Bitmapist: We built an open-source cohorts analytics tool that saved millions

Show HN: A GitHub Action that quizzes you on a pull request

Show HN: A GitHub Action that quizzes you on a pull request A little idea I got from playing with AI SWE Agents. Can AI help make sure we understand the code that our AIs write?PR Quiz uses AI to generate a quiz from a pull request and blocks you from merging until the quiz is passed. You can configure various options like the LLM model to use, max number of attempts to pass the quiz or min diff size to generate a quiz for. I found that the reasoning models, while more expensive, generated better questions from my limited testing.Privacy: This GitHub Action runs a local webserver and uses ngrok to serve the quiz through a temporary url. Your code is only sent to the model provider (OpenAI).

Show HN: Linux CLI tool to provide mutex locks for long running bash ops

Show HN: Linux CLI tool to provide mutex locks for long running bash ops Been exploring claude and spec-based coding, I think it turned out fairly successful. It's just a simple unix-style tool that gives you a single command to use in bash scripts to simplify mutex or semaphore locking of execution.

Description

More from Hacker