The more I look into MCPs as they are being build right now the more it reminds me of the time people thought giving everyone a user on a production database for queries was a good idea.
This is IMHO not a flaw of MCP, but current implementations.
It also doesn’t help that there’s an insistence on OAuth 2.1 for HTTP accessed MCPs in the spec which devs aren’t necessarily familiar with (hey SSO tax) and adds additional complexity. #llm #ai
Timo Zimmermann /
npub1de…7nj0z
2025-05-17 05:08:40
Author Public Key
npub1dev6e64lanmeaj8gzg5t2gldnvvda0cju80lug6fnlrcre3fq5rse7nj0zSeen on
wss://relay.mostr.pubPublished at
2025-05-17 05:08:40Event JSON
{
"id": "baa947ae9a7360f2ed12c91e5ec0c430ce3710fc86cea29da5e85537600312cb",
"pubkey": "6e59aceabfecf79ec8e81228b523ed9b18debf12e1dffe23499fc781e6290507",
"created_at": 1747458520,
"kind": 1,
"tags": [
[
"t",
"llm"
],
[
"t",
"ai"
],
[
"proxy",
"https://social.screamingatmyscreen.com/users/fallenhitokiri/statuses/114521441617419630",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.mostr.pub"
]
],
"content": "The more I look into MCPs as they are being build right now the more it reminds me of the time people thought giving everyone a user on a production database for queries was a good idea.\n\nThis is IMHO not a flaw of MCP, but current implementations.\n\nIt also doesn’t help that there’s an insistence on OAuth 2.1 for HTTP accessed MCPs in the spec which devs aren’t necessarily familiar with (hey SSO tax) and adds additional complexity. #llm #ai",
"sig": "3c7cd38e55b0f69c9462ca3a9189c63b0e70dd604d0cf863287245c5149b0c4dab795dc6c8f08e01caec73025e07941e3e185083461e1828f6996eb4d883d53f"
}