Live data from Hacker News

Show HN: Ismcpdead.com – Live dashboard tracking MCP adoption and sentiment

ismcpdead.com

21–29 of 29 posts

Re: Show HN: Ismcpdead.com – Live dashboard tracking MCP adoption and sentiment

#21

Earlier quoted context omitted.

This is solved by the agent having its own identity and credentials. Why would you share your login and identity with your AI agent? Access control and permissions should be handled on the backend by enforcing IAM on well-defined principals, not with MCP middleware. Claude can already bypass MCP and call APIs or use CLIs if it runs into blockers using MCP, so it’s not an effective point to implement the control.

You can have agents that serve multiple different users with varying levels if permission

Anti-pattern imho. Agents should operate within granular identity and permission scopes, with audit and log trails for all data operations (read, write, etc).

Copilot: https://learn.microsoft.com/en-us/entra/agent-id/identity-pl... | https://learn.microsoft.com/en-us/purview/audit-copilot (for example)

TLDR Maintain an identity boundary whenever possible.

Re: Show HN: Ismcpdead.com – Live dashboard tracking MCP adoption and sentiment

#22

One thing that MCP solves well, that neither CLI apps (like the `gh` CLI for example) nor letting your LLM call arbitrary APIs via CURL does, is setting granular permissions per tool. Most agent frontends I've used like Claude Code only give you one level deep of CLI commands to authorize, which works fine for allowing commands like `docker build:*`. But for complex CLIs like GitHub, Azure, etc. it just doesn't scale…

This is solved by the agent having its own identity and credentials. Why would you share your login and identity with your AI agent? Access control and permissions should be handled on the backend by enforcing IAM on well-defined principals, not with MCP middleware. Claude can already bypass MCP and call APIs or use CLIs if it runs into blockers using MCP, so it’s not an effective point to implement the control.

[dead]

Re: Show HN: Ismcpdead.com – Live dashboard tracking MCP adoption and sentiment

#24
I'm not sure if it's irony or what, but I personally realized how absolutely goofy MCP is when I vibecoded with gemini in like 2 seconds a quite reasonable bash agent (for use with my local llama stuff.)

There's really not much of a point in "MCP" and/or formality here when working with LLMs, nothing bash etc can't do. If you want to use them, fine, but understand that at the other end you're always dealing with a nonzero amount of unpredictable vibes.

Re: Show HN: Ismcpdead.com – Live dashboard tracking MCP adoption and sentiment

#25
The content analysis can be off. The following text has been flagged "negative":

> STOP asking Claude Code to design your apps. It’s great for logic, not design. Google Stitch 2.0 + Claude Code via MCP is the workflow that finally fixes the AI slop problem.

Re: Show HN: Ismcpdead.com – Live dashboard tracking MCP adoption and sentiment

#26
The token overhead is something I’ve been feeling lately. It’s annoying to see the context window shrink just from tool definitions that never even get triggered. For me, as a dev, I’d much rather just throw together a quick bash wrapper. But I can see the appeal for the non-technical side of our team who just want to 'plug and play' with AI connections without asking for a PR. It feels like MCP is aiming for that specific market gap.

Re: Show HN: Ismcpdead.com – Live dashboard tracking MCP adoption and sentiment

#29

The token overhead is something I’ve been feeling lately. It’s annoying to see the context window shrink just from tool definitions that never even get triggered. For me, as a dev, I’d much rather just throw together a quick bash wrapper. But I can see the appeal for the non-technical side of our team who just want to 'plug and play' with AI connections without asking for a PR. It feels like MCP is aiming for that sp…

[dead]
Post reply on HN