frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: Drisp – put app screenshots on true-size 3D device models

https://drint.io/drisp
1•Dan96•1m ago•0 comments

The Hidden Geography of AI [video]

https://www.youtube.com/watch?v=K-qll_Yhfms
1•jonbaer•6m ago•0 comments

Do not buy RAM, compress

https://curiousbits.nl/blog/do-not-buy-ram-compress/
2•Ecno92•6m ago•1 comments

Telegram Dictator

https://macos-beta.telegram.org/dictator/
2•SweetSoftPillow•7m ago•0 comments

ICE offers contractor operating deportation flights windfall and secrecy

https://www.theguardian.com/us-news/2026/nov/18/ice-deportation-flights-csi-deal
1•rob74•7m ago•0 comments

AI found more critical bugs in another widely used tech running 225M websites

https://www.theregister.com/security/2026/11/18/ai-found-more-critical-bugs-in-another-widely-use...
2•nephihaha•8m ago•0 comments

0.87.0 – Boot without the card, and a KVM switch – ESP-KVM

https://espkvm.io/blog/0-87-0-boot-without-the-card/
1•dexif•10m ago•0 comments

EU commission hit by cyber attack

https://en.philenews.com/international/european-commission-cyberattack-personal-data-staff-system...
3•lode•13m ago•0 comments

Bloom Exchange – Double-blind negotiation sandbox and Ed25519 receipts for MCP

https://github.com/astyboyy-ship-it/bloom-exchange
1•BloomExchangeAi•13m ago•0 comments

The Codex Sandbox

https://openai.com/index/inside-the-codex-sandbox/
1•giuliomagnifico•14m ago•0 comments

Characterizing LLM Agent Behaviors in Module Shadowing Environments

https://arxiv.org/abs/2610.40716
1•TanZeng•14m ago•0 comments

Inworld TTS looks not bad at all

https://inworld.ai/tts
1•olup•15m ago•0 comments

Redict Deprecated in Favor of Valkey

https://redict.io/posts/2026-11-17-redict-deprecated/
1•DeepLogin•15m ago•0 comments

Anthropic to debut IPO with a valuation of $1.5T

https://apnews.com/article/anthropic-ipo-nasdaq-ai-b6a74b8949021207dc162fcc876c4649
1•armcat•15m ago•0 comments

Show HN: I made PocketTag, forward PocketAI notes with tag to email

https://www.pockettag.link
1•eekay•16m ago•0 comments

Palo Alto Networks to Buy AI-Startup Applied Compute for $4.5B

https://www.wsj.com/tech/ai/palo-alto-networks-to-buy-ai-startup-applied-compute-for-4-5-billion-...
1•ronfriedhaber•18m ago•0 comments

Can you unlock the bootloader on the Motorola G Stylus 2025 from Straight Talk?

1•timtim51251•21m ago•0 comments

Show HN: SJF4J – Treat Java Objects as JSON

https://github.com/sjf4j-projects/sjf4j
1•hannyu•21m ago•0 comments

Deploying OpenEverest on a 3-Node K3s Cluster

https://www.percona.com/blog/deploying-openeverest-on-a-3-node-k3s-cluster/
2•omegaSigma95•21m ago•0 comments

Many Differences Between Liberals and Conservatives May Boil Down to One Belief

https://www.scientificamerican.com/article/many-differences-between-liberals-and-conservatives-ma...
2•jcfrei•21m ago•0 comments

We made disk writes over 100 times faster. Here's the trade-off

https://natbox.io/blog/faster-disk-writes
1•alsarafm•22m ago•0 comments

When AI Starts Solving Problems Scientists Couldn't

https://open.spotify.com/episode/6AcIzPDTkFQoD2t0esNuA9
1•thecontentboy•22m ago•0 comments

Crew unaware of risks before Mike Lynch's yacht Bayesian sank, say investigators

https://www.bbc.co.uk/news/articles/c6e9kn15z9d7o
2•zeristor•23m ago•0 comments

Distributed, high-performance blob storage on SQLite

https://zerodha.tech/blog/high-performance-distributed-blob-storage/
2•ghostfoxgod•23m ago•0 comments

Google's AI Strategy Is a Distribution War

https://siliconcent.com/posts/googles-ai-strategy-is-a-distribution-war/
1•josharsh•24m ago•0 comments

US Department of Justice charges Russian for targeting Palantir as foreign agent

https://www.reuters.com/legal/litigation/us-department-of-justice-charges-russian-targeting-palan...
2•vrganj•26m ago•0 comments

Show HN: Supabase RLS simulator – who can read/insert/update/delete each table

https://psychevus.com/tools/supabase-rls
1•mzaferanloo•28m ago•0 comments

SSH2Shell

https://ssh2shell.com/
2•schaum•28m ago•2 comments

Engineering is broken (we're doing it the wrong way)

https://link.springer.com/book/10.1007/978-3-032-18169-5
2•conway_man•28m ago•1 comments

Show HN: Kibi – requirements framework for AI coding agents

https://looted.github.io/kibi/
1•Looted•32m 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?