frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

Ask HN: Why don't browsers load websites directly in WASM?

1•FerkiHN•2m ago•1 comments

Dotfiles Management (2022)

https://mitxela.com/projects/dotfiles_management
1•signa11•2m ago•0 comments

Show HN: We built a tool to translate sustainability jargon into business speak

https://www.leafr.com/sustainababble-translator
1•gusbartholomew•7m ago•0 comments

Cold hydrogen clouds discovered in heated Fermi bubbles at Milky Way's center

https://phys.org/news/2025-07-cold-hydrogen-clouds-superheated-fermi.html
1•olvy0•8m ago•0 comments

RAG chunking isn't one problem, it's three

https://sgnt.ai/p/rag-trinity/
1•petesergeant•12m ago•0 comments

Show HN: Vity: Think Cursor, but for Shell Commands

https://github.com/Kaleab-Ayenew/vity
1•kalishayish•17m ago•0 comments

Show HN: EmailAI.dev – Generate production-ready email templates with AI

https://www.emailai.dev
1•aadarshguru•20m ago•0 comments

We should ask AI do coding tasks more efficiently, just for saving tokens

https://github.com/lidangzzz/AI-Coding-Style-Guides
2•lidangzzz•26m ago•0 comments

I vibe coded a game with my daughter

https://davepeck.org/2025/07/07/cat-restaurant-game-vibe-coded-with-vscode-and-github-copilot/
1•furkansahin•26m ago•0 comments

Keeping tabs on curl's memory use

https://daniel.haxx.se/blog/2025/07/08/keeping-tabs-on-curls-memory-use/
1•TangerineDream•27m ago•0 comments

The Dutch Eel Ships of London

https://bsky.app/profile/greenleejw.bsky.social/post/3lsvugci7mc2u
2•vintagedave•28m ago•0 comments

Cough Syrup Ambroxol shows promise for Parkinson's dementia treatment

https://newatlas.com/brain/alzheimers-dementia/cough-syrup-dementia/
1•thunderbong•33m ago•0 comments

Retrowave 2

https://store.steampowered.com/app/3331000/Retrowave_2/
1•doener•33m ago•0 comments

Show HN: OffChess – 100k+ Offline, Ad-Free Chess Puzzles App

https://offchess.com
1•avadhesh18•36m ago•0 comments

Show HN: StopAddict – Track your addictions and quit with a simple system

1•skyzouw•36m ago•0 comments

Ready Lists

https://11011110.github.io/blog/2025/07/07/ready-lists.html
1•082349872349872•38m ago•0 comments

Introducing OpenCLI

https://patriksvensson.se/posts/2025/07/introducing-open-cli
4•pimterry•39m ago•0 comments

Cocoa Basics Part Zero: Introduction

https://blog.xoria.org/cocoa-basics-0/
2•todsacerdoti•42m ago•1 comments

UK police dangle £75M to digitize its VHS tape archives

https://www.theregister.com/2025/07/08/uk_police_dangle_75_million/
1•jjgreen•42m ago•0 comments

Taichi: High-performance parallel programming in Python

https://www.taichi-lang.org/
2•fanf2•51m ago•0 comments

Heredocs in Dockerfiles (2021)

https://www.docker.com/blog/introduction-to-heredocs-in-dockerfiles/
3•tosh•51m ago•0 comments

Am I Online?

https://antonz.org/is-online/
3•begoon•52m ago•0 comments

C4 Bomb: Blowing Up Chrome's AppBound Cookie Encryption

https://www.cyberark.com/resources/threat-research-blog/c4-bomb-blowing-up-chromes-appbound-cookie-encryption
2•Metalnem•53m ago•0 comments

Kronotop v0.12.0 – Scalable, transactional doc DB with query predicates

https://github.com/kronotop/kronotop/releases/tag/v0.12.0
1•mastabadtomm•57m ago•0 comments

WebAssembly: Yes, but for What?

https://queue.acm.org/detail.cfm?id=3746171
3•todsacerdoti•58m ago•3 comments

Thunderbird 140 ESR is out now with new features

https://www.neowin.net/news/thunderbird-140-esr-is-out-now-with-new-features-bug-fixes-and-critical-security-patches/
7•Bluestein•1h ago•0 comments

Zoopharmacognosy

https://en.wikipedia.org/wiki/Zoopharmacognosy
2•elsewhen•1h ago•0 comments

TIL you can make "GIFs" with SVGs for GitHub README.md files

https://koaning.io/posts/svg-gifs/
3•cantdutchthis•1h ago•0 comments

Lessons I Learned from My Failed SaaS Products

https://andresmax.substack.com/p/lessons-i-learned-from-my-failed
1•sjdonado•1h ago•0 comments

How to become passionate about delivering shareholder value

https://www.seangoedecke.com/shareholder-value/
3•rtukpe•1h ago•1 comments
Open in hackernews

A Critical Look at "A Critical Look at MCP."

https://docs.mcp.run/blog/2025/05/16/mcp-implenda-est/
33•palmfacehn•1mo ago

Comments

nip•1mo ago
> Further, one of the issues with remote servers is tenancy

Excellent write-up and understanding of the current state of MCP

I’ve been waiting for someone to point it out. This is in my opinion the biggest limitation of the current spec.

What is needed is a tool invocation context that is provided at tool invocation time.

Such tool invocation context allows passing information that would allow authorizing, authentication but also tracing the original “requester”: think of it as “tool invoked on behalf of user identity”

This of course implies an upstream authnz that feeds these details and more.

If you’re interested in this topic, my email is in my bio: I’m of the architect of our multi-tenant tool calling implementation that we’ve been running in production for the past year with enterprise customers where authnz and auditability are key requirements.

jensneuse•1mo ago
The way we've solved this in our MCP gateway (OSS) is that the user first needs to authenticate against our gateway, e.g. by creating a valid JWT with their identity provider, which will be validated using JWKS. Now when they use a tool, they must send their JWT, so the LLM always acts in their behalf. This supports multiple tenants out of the box. (https://wundergraph.com/mcp-gateway)
Yoric•1mo ago
Is this really hard to code?

I mean, converting a tool-less LLM into a tool-using LLM is a few hundred lines of code, and then you can plug all your tools, with whichever context you want.

nip•1mo ago
Indeed very easy to code!

My point is about the need for a spec of this mechanism: without a spec, every company / org will roll out their own and result in 500 flavors of the same concept.

That’s where MCP shines: tool calling and tool discovery is already 1.5 years old (an eternity in ai land).

The MCP spec ensures that we can all focus on solving problems with tool calling rather than wasting time in cobbling together services that re not interoperable (because developed without a common spec / standard)

__loam•1mo ago
This is an advertisement
tomrod•1mo ago
I wish this were critical, but it is an ad for MCP.run.
nip•1mo ago
It’s both in my opinion and discussions can stem from the linked article

Many come to HN also for the comments

palmfacehn•1mo ago
Personally, I'm not a fan. I thought the proponent's view might stimulate a discussion.
FunnyLookinHat•1mo ago
> Server authors working on large systems likely already have an OAuth 2.0 API.

I think this biases towards sufficiently large engineering organizations where OAuth 2.0 was identified as necessary for some part of their requirements. In most organizations, they're still using `x-<orgname>-token` headers and the like to do auth.

I'm not sure that there's a better / easier way to do Auth with this use case, but it does present a signficant hurdle to adoption for those who have an API (even one ready for JSON-RPC!) that is practically ready to be exposed via MCP.

motorest•1mo ago
> I think this biases towards sufficiently large engineering organizations where OAuth 2.0 was identified as necessary for some part of their requirements. In most organizations, they're still using `x-<orgname>-token` headers and the like to do auth.

I don't think that's it. Auth is a critical system in any organization, and larger organizations actually present more resistance to change, particularly in business critical areas. If anything, smaller orgs gave an easier time migrating critical systems such as authentication.

hirsin•1mo ago
Touching on tenancy and the "real" gaps in the spec does help push the discussion in a useful direction.

https://vulnerablemcp.info/ is a good collection of the immediately obvious issues with the MCP protocol that need to be addressed. A couple low blows in there, that feel a bit motivated to make MCP look worse, but generally a good starting point overall.

owebmaster•1mo ago
This post has too many "shameless plugs" to be taken seriously.
smitty1e•1mo ago
Serious question:

If doing an extended, service-level session (like a GPT interaction) with a server known beforehand, would it make sense to set up a keypair and manage the interaction over SSH?

Restated: are we throwing away a lot of bandwidth establishing TLS trust for the more general HTTP?