Farley on Nostr: Here’s the key thing that isn’t said in the description: Who runs the MCP ...

Here’s the key thing that isn’t said in the description:

Who runs the MCP servers?
Who controls the tool registry?
Who issues OAuth credentials?
Who defines “secure interactions”?

Because the moment you hear:
OAuth2
centralized tool discovery
unified interfaces
stateful workflows
you should immediately recognize:

This is being designed primarily for centralized environments.

Cloud.
SaaS.
Enterprise.
Platform ecosystems.

Not sovereign edge computing.

MCP assumes:

persistent identity
trusted authorities
permissioned access
session continuity
managed endpoints

That maps perfectly onto:
centralized AI providers
enterprise integrations
platform-controlled agents

It maps poorly onto:
sovereign users
local nodes
decentralized systems
adversarial environments

Sound familiar? 😏