frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Libghostty is coming

https://mitchellh.com/writing/libghostty-is-coming
115•kingori•4h ago•24 comments

Android users can now use conversational editing in Google Photos

https://blog.google/products/photos/android-conversational-editing-google-photos/
36•meetpateltech•53m ago•23 comments

Getting AI to work in complex codebases

https://github.com/humanlayer/advanced-context-engineering-for-coding-agents/blob/main/ace-fca.md
32•dhorthy•3h ago•15 comments

Launch HN: Strata (YC X25) – One MCP server for AI to handle thousands of tools

72•wirehack•3h ago•42 comments

Go has added Valgrind support

https://go-review.googlesource.com/c/go/+/674077
365•cirelli94•8h ago•92 comments

From MCP to shell: MCP auth flaws enable RCE in Claude Code, Gemini CLI and more

https://verialabs.com/blog/from-mcp-to-shell/
48•stuxf•2h ago•15 comments

x402 — An open protocol for internet-native payments

https://www.x402.org/
132•thm•3h ago•53 comments

Imagining a language without booleans

https://justinpombrio.net/2025/09/22/imagining-a-language-without-booleans.html
25•todsacerdoti•19h ago•18 comments

Nine things I learned in ninety years

http://edwardpackard.com/wp-content/uploads/2025/09/Nine-Things-I-Learned-in-Ninety-Years.pdf
756•coderintherye•14h ago•293 comments

Getting More Strategic

https://cate.blog/2025/09/23/getting-more-strategic/
105•gpi•5h ago•12 comments

Restrictions on house sharing by unrelated roommates

https://marginalrevolution.com/marginalrevolution/2025/08/the-war-on-roommates-why-is-sharing-a-h...
212•surprisetalk•4h ago•245 comments

Structured Outputs in LLMs

https://parthsareen.com/blog.html#sampling.md
158•SamLeBarbare•7h ago•74 comments

Mesh: I tried Htmx, then ditched it

https://ajmoon.com/posts/mesh-i-tried-htmx-then-ditched-it
69•alex-moon•5h ago•66 comments

Shopify, pulling strings at Ruby Central, forces Bundler and RubyGems takeover

https://joel.drapper.me/p/rubygems-takeover/
188•bradgessler•2h ago•111 comments

OpenDataLoader-PDF: An open source tool for structured PDF parsing

https://github.com/opendataloader-project/opendataloader-pdf
46•phobos44•3h ago•12 comments

Always Invite Anna

https://sharif.io/anna-alexei
15•walterbell•2h ago•0 comments

Thundering herd problem: Preventing the stampede

https://distributed-computing-musings.com/2025/08/thundering-herd-problem-preventing-the-stampede/
10•pbardea•18h ago•0 comments

Zinc (YC W14) Is Hiring a Senior Back End Engineer (NYC)

https://app.dover.com/apply/Zinc/4d32fdb9-c3e6-4f84-a4a2-12c80018fe8f/?rs=76643084
1•FriedPickles•5h ago

Zig feels more practical than Rust for real-world CLI tools

https://dayvster.com/blog/why-zig-feels-more-practical-than-rust-for-real-world-cli-tools/
132•dayvster•5h ago•193 comments

Are elites meritocratic and efficiency-seeking? Evidence from MBA students

https://arxiv.org/abs/2503.15443
83•bikenaga•2h ago•43 comments

Markov Chains Are the Original Language Models

https://elijahpotter.dev/articles/markov_chains_are_the_original_language_models
6•chilipepperhott•3d ago•0 comments

Agents turn simple keyword search into compelling search experiences

https://softwaredoug.com/blog/2025/09/22/reasoning-agents-need-bad-search
39•softwaredoug•3h ago•15 comments

Smooth weighted round-robin balancing

https://github.com/nginx/nginx/commit/52327e0627f49dbda1e8db695e63a4b0af4448b1
12•grep_it•4d ago•1 comments

Zoxide: A Better CD Command

https://github.com/ajeetdsouza/zoxide
264•gasull•13h ago•168 comments

YAML document from hell (2023)

https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
146•agvxov•8h ago•100 comments

Show HN: Run Qwen3-Next-80B on 8GB GPU at 1tok/2s throughput

https://github.com/Mega4alik/ollm
73•anuarsh•3d ago•7 comments

Show HN: Kekkai – a simple, fast file integrity monitoring tool in Go

https://github.com/catatsuy/kekkai
31•catatsuy•3h ago•4 comments

Processing Strings 109x Faster Than Nvidia on H100

https://ashvardanian.com/posts/stringwars-on-gpus/
138•ashvardanian•3d ago•23 comments

Cache of devices capable of crashing cell network is found in NYC

https://www.nytimes.com/2025/09/23/us/politics/secret-service-sim-cards-servers-un.html
201•adriand•6h ago•128 comments

Permeable materials in homes act as sponges for harmful chemicals: study

https://news.uci.edu/2025/09/22/indoor-surfaces-act-as-massive-sponges-for-harmful-chemicals-uc-i...
81•XzetaU8•8h ago•68 comments
Open in hackernews

Launch HN: Strata (YC X25) – One MCP server for AI to handle thousands of tools

72•wirehack•3h ago
Hey HN! We are Klavis AI (https://www.klavis.ai/) and we're launching Strata, one open-source MCP server that helps AI agents use thousands of API tools without getting overwhelmed. Instead of showing all available tools at once, Strata reveals them step-by-step based on what the AI actually needs.

As a former Senior SWE on Google Gemini 's tool use team, I saw firsthand how AI would struggle with tools. If you've built AI agents, you've likely hit the same walls: (1) AI agents struggle to pick the right API from hundreds of options. (2) Tool descriptions and info consume massive token budgets. (3) Most servers cap at 40~50 tools to avoid these problems, limiting what you can build.

Instead of flooding the AI with everything upfront, Strata works like a human would. It guides the AI agents to discover relevant categories, then lists available actions in those categories. It relies on LLMs’ reasoning to drill down progressively to find the exact tool needed. Here are some examples:

Github query: "Find my stale pull requests in our main repo"

Strata: AI model identifies GitHub → Shows categories (Repos, Issues, PRs, Actions) → AI selects PRs → Shows PR-specific actions -> AI selects list_pull_requests → Shows list_pull_requests details -> Executes list_pull_requests with the right parameters.

Jira query: "Create a bug ticket in the 'MOBILE' project about the app crashing on startup."

Strata: AI identifies Jira → Shows categories (Projects, Issues, Sprints) → AI selects Issues → Shows actions (create_issue, get_issue) → AI selects create_issue → Shows create_issue details → Executes with correct parameters.

Slack query: "Post a message in the #announcements channel that bonus will be paid out next Friday."

Strata: AI identifies Slack → Shows categories (Channels, Messages, Users) → AI selects Messages → Shows actions (send_message, schedule_message) → AI selects send_message → Shows send_message details → Executes with correct parameters.

This progressive approach unlocks a huge advantage: depth. While most integrations offer a handful of high-level tools, Strata can expose hundreds of granular features for a single app like GitHub, Jira, etc. Your AI agent can finally access the deep, specific features that real workflows require, without getting lost in a sea of options.

Under the hood, Strata manages authentication tokens and includes a built-in search tool for the agent to dig into documentation if it gets stuck.

On the MCPMark https://mcpmark.ai/leaderboard/mcp, Strata achieves +15.2% higher pass@1 rate vs the official GitHub server and +13.4% higher pass@1 rate vs the official Notion server. In human eval tests, it hits 83%+ accuracy on complex, real-world multi-app workflows.

Here is a quick demo to watch Strata navigate a complex workflow with multiple apps, automatically selecting the right tools at each step: https://www.youtube.com/watch?v=N00cY9Ov_fM.

You can connect to any external MCP Server into Strata, and we have an open source version for it: https://github.com/Klavis-AI/klavis.

For team or production use with more features, visit our website: https://www.klavis.ai. Add Strata to Cursor, VS Code or any MCP-compatible application with one click. You can also use our API to easily plug in Strata to your AI application.

We look forward to your comments. Thanks for reading!

Comments

bigolnik•2h ago
How does this differ from something like nexusrouter?
wirehack•2h ago
As you can see from our examples, the main approach is not tool search. Instead, Strata guides your AI agent step by step, going from server to categories to actions to action details so that the model does not get overloaded. We actually have 1000+ tools for some of the integrations (e.g. GitHub) and this approach works better than traditional methods.

Think of it as a search engine vs. a file explorer. But we do provide documentation search as well. So you get the best out of the two worlds.

justchad•2h ago
This looks very relevant and useful to what I'm working on at the moment. The LLM gets lost in all of the tools we provide for certain actions.
wirehack•2h ago
Glad it could be helpful to you! Curious what AI agents you are building and exactly what tools caused the failure.

In any case, feel free to give us a try!

CuriouslyC•2h ago
This is something I actually started to work on and put down because it wasn't exciting enough, but it's a legit product that fills a niche and congrats on the launch.

The biggest issue I found was getting agents to intelligently navigate the choose your own adventure of searching for the right tool. It amazes me that they're so good at coding when they're so bad at tool use in general. I'm sure your MCP responses were a fun bit of prompt engineering.

wirehack•2h ago
Haha yeah we did optimize it a lot before the launch!

Actually for us, our first prototype was pretty good! We are also surprised about that because it took us a day or so to build the the prototype (only for one integrations though). Then it took us another week to build another prototype for multiple integrations.

ssgodderidge•1h ago
Is the goal to make a “universal MCP” that makes it easy to let MCP clients execute thousands of tools on a session by session basis? Or is it more focused on initial tool discovery and registration? If it’s the former, does the process add more latency between user taking action and tool getting executed?
wirehack•1h ago
Yes it is the former. The value comes from its progressive guidance during a task, not just in the initial setup.

As for latency, we optimized for that. For examples, Strata automatically uses a direct, flat approach for simple cases. And we use less tokens compared to official MCP servers as well, as shown in the benchmark.

typpilol•1h ago
Isn't Microsoft going to eat your lunch with their "virtual tools" offering for high tool counts?
wirehack•58m ago
We tested our approaches with several thousand tools and it is working pretty well. Also we provide API access as well, so any developer can use this, not just on Microsoft or VS Code.
tleyden5iwx•1h ago
Looks really useful! Do you happen to have a gallery of apps using it? In particular, I'd like to see how desktop or mobile apps handle the oauth flows.
wirehack•1h ago
Yes we do! Just signup to our website https://www.klavis.ai/home/mcp-servers and you will see all the apps and the auth options.
Banditoz•1h ago
I think having the gallery viewable without an account would be valuable.
wirehack•1h ago
Oh yes for sure. Checkout https://www.klavis.ai/mcp-servers. You do not need to sign up. But you cannot see the auth flow for obvious reasons.
p_ing•58m ago
The lack of enterprise Microsoft services is really discouraging.
wirehack•53m ago
We are aware of this and working on it now. We are actually code complete on Microsoft Teams and Outlook. We will definitely launch it within the next week or so.
nycdatasci•1h ago
The attack surface for agents with MCP access grows exponentially with the number of tools. On the scale of thousands of tools, I think it's nearly impossible to understand potential interactions and risk. Do you have any innovative controls in place that would help a CISO get comfortable with a product like this in an enterprise context?
wirehack•1h ago
That's the critical question. The key is that Strata never exposes all tools to the agent at once. Our progressive guidance acts as a dynamic allowlist, so that the agent only "sees" the specific tools relevant to its immediate task. This fundamentally reduces the blast radius at each step. We do provide a comprehensive audit trails for every action, giving a CISO a centralized control plane to manage and monitor agent capabilities, rather than an exponential risk. If you are interested, come talk to us!
daveidol•53m ago
How is a “dynamic allowlist” useful if it can still access anything based on what the user prompts? Is there a way to impose a static allowlist too?
wirehack•52m ago
Yes there is a way to impose a static allowlist. As a very simple example, you can disable certain servers completely via the UI or the API.
smrtinsert•1h ago
this. This will be the number one obstacle to adoption.
typpilol•1h ago
Comparing to the official GitHub server isn't a good benchmark because it's a bloated mess of tools still.
wirehack•1h ago
The eval benchmark also compared Notion and we are 13% higher than them as well!
darkbatman•1h ago
We kinda use https://github.com/googleapis/genai-toolbox but for databases looking forward if klavis provide more or general solution.

Ideally when we are writing agents we need mcp to support auth, custom headers because by design when deploying for saas we need to pass around client params to be able to isolate client connections.

We do token optimisation and other smart stuff to save token money. Looking forward to try this as well if this solves similar problems as well

wirehack•57m ago
Thank you! Yes we do provide auth and support other remote MCP servers via our API : https://docs.klavis.ai/api-reference/strata/create. It indeed support custom headers. Feel free to give us a try or come talk to us!
koliber•54m ago
How do you handle compliance questionnaires from companies that adhere to SOC2 guidelines? If I used Klavis how would I tell my clients which information I send to which external partners?
wirehack•51m ago
We are SOC2 compliant. So this will not be a problem. Come talk to us if you are interested in using this for your clients and we can work out the details.
deepdarkforest•50m ago
1. Interesting approach, but the pricing seems 1-2 orders of magnitude too expensive. For your example for slack, It contains 4 calls for an action. Pricing shows 100 dollars per 10k cals, so 1 cent per call. This means, for an agent that lets say does 4 actions, so and your examples show at least 3-4 api calls per action , it's already 12 cents? Similar tools like composio.dev have 200k calls for 29 dollars, so around 70x cheaper (both for the cheapest tier). Even with needing only 1 call for subsequent calls, 1 cent per single api call sounds wrong, at least for our use case it does not economic sense to pay 5-10 cents on top of llm costs on every user query. Apologies if I'm missing something!

2. Could this not be replicated by others by just handmaking a fuzzy search tool on the tools? I think this is the approach that will win, even with rag for lets say 10k plus tools maybe in the future, but not sure how much differentiation this is in the long term, i've made this search tool myself a couple of times already

wirehack•47m ago
1. Hi! We noticed this for Strata as well so we are ONLY counting the execute_action in Strata. This means the fee is the same as using the traditional, flat approaches. In other words, the 3 previous calls does not cost you anything!

2. I think the main drawback of search method is like giving a human lots of tools/APIs but you can ONLY access them via a search interface. This feels weird and should be improved. For our approaches, the step by step methods allow you to see what categories/actions are available. We also provide a documentation search so that you get the best out of both worlds.

deepdarkforest•41m ago
1. Oh okay great, maybe clarify it in the pricing page? That mcp server call means just execute. But its' still 10x more expensive right?

2. From what i understand it's just nested search right? It is not anything different, if you do flat or embedding search or fuzzy/agentic nested is a choice for sure, but Im just saying not sure how defensible this is, if all other mcp competitors or even users themselves put in a nested search tool

wirehack•36m ago
1. Sure, we will clarify that in the pricing page, thank you! As you can see from our evaluation, we are much better than official MCP servers. I think people care more about getting things done correctly. Otherwise, you waste all the model tokens for nothing. We do have enterprise deals where we can work out a customized pricing plan for your specific use case. Come talk to us if you are interested.

2. One VERY important distinction is that the model is doing the "search" here, not some RAG algorithm or vector database. Therefore, as the model becomes smarter, this approach will be more accurate as well.

deepdarkforest•7m ago
1. I was not talking about official MCP servers, those are often even free. Im talking about pricing of other devtools for aggregating tools/mcp's. I think this is an obvious space to build i agree, i just worry about differentiation. Its a search space not as big as web search, or complex (order doesnt matter).

2. Yes, i see, this is what i meant by agentic search. Essentially is a tiny subagent, taking list of tools in and out the relevant ones. Still implementable in 5 mins. But i guess if the experience is very smooth enterprise might pay?

wirehack•1m ago
1. Yes I agree. To be honest we are a young company (as you can tell we are from YC X25), so we are still figuring out the pricing. But thank you for the feedback and sharing your thoughts.

2. Yes the idea is not complex once you understand it. But there are some nuances we found along the way and supporting more integrations are always important but requires engineering efforts. Thank you!

progbits•42m ago
The fact people are giving credentials to all these MCP tools keeps amazing me.

Ten years ago if you built a service that asked you for permissions to everything imaginable most people would keep well clear. I guess the closest was Beeper which wanted your social passwords but that was heavily criticized and never very popular.

Now you slap an AI label on it and you can't keep people away.

wirehack•40m ago
We also provide an open-source version for Strata so that you can have full control. You can self-host it on your own infrastructure, so your credentials never have to touch our servers.
progbits•35m ago
That's nice, kudos. But trusting you is only half of the problem. I don't trust the LLM either.
wirehack•32m ago
Yeah I see what you mean. Many MCP clients has the ability to ask human for confirmation before a tool call is executed. In this way, you can check the tool call before it executes.
smt88•9m ago
Is there any way for the LLM to bypass the request for human confirmation, or is it hard-coded into the deterministic MCP client code?
wirehack•4m ago
We do not build the MCP clients, but for many of the clients I believe it is hard-coded into the deterministic client code.
jfdi•33m ago
Nice work this definitely feels like a market gap, for those who’ve been deep enough to experience it.
wirehack•31m ago
Thank you!
wanderingbit•6m ago
Heads up, your docs for “Getting Started > Multi-app integration > open source” point to a broken link for the open source code:

https://docs.klavis.ai/documentation/quickstart#open-source

Add a call to the mintlify cli ‘mint broken-links’ into your CI and you should be set!