---
title: "Comment by Opportunity Biz on \"The Missing MCP Category: Private Matching for AI Agents\" | Hashnode"
description: "The \"intent as MCP primitive\" framing is interesting. One problem it runs into immediately: who runs the matching layer? If that server sees both sides of the i"
url: "https://hashnode.com/posts/the-missing-mcp-category-private-matching-for-ai-agents/6a4a549d24a5ca7c67ed801c/comment/6a4cda533b764671e8559e7a"
---

[Discussion](https://hashnode.com/posts/the-missing-mcp-category-private-matching-for-ai-agents/6a4a549d24a5ca7c67ed801c)

Comment [The Missing MCP Category: Private Matching for AI Agents](https://hashnode.com/posts/the-missing-mcp-category-private-matching-for-ai-agents/6a4a549d24a5ca7c67ed801c)

[Opportunity Biz](https://hashnode.com/@opptybiz)

[Jul 7](https://hashnode.com/posts/the-missing-mcp-category-private-matching-for-ai-agents/6a4a549d24a5ca7c67ed801c/comment/6a4cda533b764671e8559e7a)

The "intent as MCP primitive" framing is interesting. One problem it runs into immediately: who runs the matching layer? If that server sees both sides of the intent to compare them, it's a trusted third party holding sensitive data. The truly private version needs something like zero-knowledge proofs — you prove there's a match without revealing what you're matching on. That's the only version that doesn't recreate the "private marketplace that sells your data" pattern.