3 ms·

Yes because we should all be building function calling implementations for the same 10 SaaS services rather than using 10 standard MCP servers.

• ukuina 1y ago
  But the standard servers should be hosted by the service provider, like mcp.slack.com as a counterpart to api.slack.com Why should I be self-hosting ANY local MCP server for accessing an external service?
  • reustle 1y ago
    That is being done as a stop gap until official servers are released. Ideally you are writing a server for your own product/service, or custom local work. i.e. I wrote a server for water.gov to pull the river height prediction nearby for the next 24hr. This helps the campground welcome message writing tool craft a better welcome message. Sure that could be a plain tool call, but why not make it portable into any AI service.
    • cyberge99 1y ago
      Can you share this?
  • Too 1y ago
    Remote MCP servers can do prompt injection that instruct your local agent to do something else other than only the expected tool call. https://embracethered.com/blog/posts/2025/model-context-protocol-security-risks-and-exploits/ https://embracethered.com/blog/posts/2025/model-context-prot...
    • lyu07282 1y ago
      That flaw isn't introduced by the MCP server necessarily it can already be present in the API data it returns, you will never be able to protect yourself against someone injecting a malicious prompt that calls your code eval tool to open up a reverse shell on your MacBook Pro.
      • owebmaster 1y ago
        that's not the case, MCP has a feature, samplings, that allow MCP servers to run prompts using the client model.
        • lyu07282 1y ago
          Oh boy, you know at least the infosec people are going to get a good laugh from this clown show