frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Tesla Roadster Won't Refill Its Air Tanks (Bet) [video]

https://www.youtube.com/watch?v=yKgox6ZKRJk
1•num42•1m ago•1 comments

Large Angle Period of the Pendulum

https://jslandy.com/pendulum/
1•efavdb•3m ago•0 comments

Category Theory Illustrated – Sets

https://abuseofnotation.github.io/category-theory-illustrated/01_set/
1•boris_m•3m ago•0 comments

The Obsidian (open source/local) of personal agents

https://tophat.md
2•exr0n•5m ago•1 comments

Rewriting my toy blockchain in Rust (2022)

https://www.ezzeriesa.com/index/Writing/Rewriting%20my%20toy%20blockchain%20in%20Rust%209a130f225...
2•kurinikku•10m ago•0 comments

HuggingFace Attack Postmortem: Civilizations, Reactions and Next Actions

https://thezvi.wordpress.com/2026/09/01/huggingface-attack-postmortem-civilizations-reactions-and...
1•gmays•18m ago•0 comments

Show HN: Deckard – Diablo 4 Companion

https://www.patreon.com/deckard_companion/posts/deckard-is-soon-173632635
1•ozanbora•22m ago•0 comments

How to Make Almost Anything

https://pub.cba.mit.edu/863.26/site/
6•o4c•24m ago•0 comments

How to Make Something That Makes Almost Anything(2024)

https://fab.cba.mit.edu/classes/865.24/
3•o4c•26m ago•1 comments

Fractional Reserve Banking 101

https://www.lynalden.com/fractional-reserve-banking/
2•rzk•26m ago•0 comments

Automatar – An Intelligent AI Guitar

https://www.creativeapplications.net/member/automatar-an-intelligent-ai-guitar/
1•bryanrasmussen•30m ago•0 comments

Sortition

https://en.wikipedia.org/wiki/Sortition
1•xnx•30m ago•0 comments

We need a data vault to grant on-demand access to our data

https://memo.mx/posts/datavault/
1•__warlord__•31m ago•0 comments

Qwen4 Max: Intelligence, Performance and Price Analysis

https://artificialanalysis.ai/models/qwen4-max
2•theanonymousone•37m ago•2 comments

The Tools of Dan Gelbart

https://scottlocklin.wordpress.com/2026/08/05/the-tools-of-dan-gelbart/
2•o4c•42m ago•0 comments

Questions asked on self-help cassettes

https://tapes.emilysaltz.space/
1•gregsadetsky•44m ago•0 comments

Can robotics models control a 4200lb excavator?

https://www.dreamscalelabs.com/blog/excavate/
1•PenTest-duck•53m ago•0 comments

Show HN: RediWM – A complete Wayland Desktop Environment built in Zig 0.17

https://github.com/oxydizer/rediwm
1•oxydizer•57m ago•0 comments

I made an addicting game that will generate a million in revenue one day

https://www.pufful.com/
1•mattmerrick•59m ago•1 comments

Reviewing footage and audio isn't editing. I built an app that does it for you

https://editmatic.app/en
1•EithanK•1h ago•0 comments

Import PST file to Office 365

https://www.mailsdaddy.com/pst-to-office-365-migration-tool/
1•somit0•1h ago•0 comments

Show HN: Agent-Otel-Kit – OTel Dashboards for Claude Code, Codex and Gemini CLI

https://github.com/s3onghyun/agent-otel-kit
1•s3onghyun•1h ago•0 comments

Show HN: Vindle – Wordle for Cars

https://vindle.app/
1•cachebag•1h ago•0 comments

Show HN: OpenButterfly – Tracking the environmental impact of the AI ecosystem

https://openbutterfly.com
2•ravipatib•1h ago•0 comments

Did the Apollo Guidance Computer use 60% of the ICs in 1963?

https://retrocomputing.stackexchange.com/questions/12158/did-the-apollo-guidance-computer-really-...
3•Skyfall106•1h ago•0 comments

Show HN: New Book

https://github.com/metereindustries/qeg
1•metereindustrie•1h ago•0 comments

HS 9th Grade ELA Assignment Turned into philosophical rambling

https://liamis.dev/blogs/CaptionRambling/
1•ForgottenMail•1h ago•0 comments

Google AI Ultra Subscription Not Worth It

https://www.reddit.com/r/google_antigravity/comments/1xx9nl3/google_ai_ultra_subscription_not_wor...
5•behnamoh•1h ago•0 comments

Jensen Huang's downfall will accelerate US-China 'great decoupling'

https://www.channelnewsasia.com/commentary/nvidia-jensen-huang-affair-us-china-ai-tech-decoupling...
1•Markoff•1h ago•0 comments

RISC-V Matrix Extensions

https://fprox.substack.com/p/risc-v-matrix-extensions
1•hasheddan•1h ago•0 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•1y ago

Comments

nip•1y 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•1y 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•1y 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•1y 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•1y ago
This is an advertisement
tomrod•1y ago
I wish this were critical, but it is an ad for MCP.run.
nip•1y ago
It’s both in my opinion and discussions can stem from the linked article

Many come to HN also for the comments

palmfacehn•1y ago
Personally, I'm not a fan. I thought the proponent's view might stimulate a discussion.
FunnyLookinHat•1y 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•1y 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•1y 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•1y ago
This post has too many "shameless plugs" to be taken seriously.
smitty1e•1y 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?