{
  "version": "1.3.0",
  "query": "MCP",
  "total": 14,
  "results": [
    {
      "id": "agents/mcp-publication-and-compatibility",
      "title": "Recipe: publish and verify an MCP integration",
      "description": "Separate registry publication, host availability, version compatibility, tool selection, and successful execution.",
      "audience": "agents",
      "category": "Audit recipes",
      "kind": "Recipe",
      "level": "Technical",
      "outcome": "Produce a compatibility record for a named host and one complete customer workflow.",
      "published": "2026-09-13",
      "updated": "2026-09-13",
      "url": "https://byagents.dev/agents/mcp-publication-and-compatibility",
      "markdown_url": "https://byagents.dev/content/agents/mcp-publication-and-compatibility.md",
      "excerpt": "Input: a server implementation, a declared protocol revision, and a named intended host. Output: publication and compatibility evidence for that combination. This is an implementation checklist, not a universal MCP certification or a claim that ByAgents hosts an MCP service."
    },
    {
      "id": "humans/agent-protocols-explained",
      "title": "MCP, WebMCP, A2A, ACP, UCP, and ARD: what to build",
      "description": "A plain-English map of agent protocols, the job each one does, and the adoption question to ask before investing.",
      "audience": "humans",
      "category": "Foundations",
      "kind": "Guide",
      "level": "Mixed",
      "outcome": "Select an interface for a real customer workflow without implementing every acronym.",
      "published": "2026-09-13",
      "updated": "2026-09-13",
      "url": "https://byagents.dev/humans/agent-protocols-explained",
      "markdown_url": "https://byagents.dev/content/humans/agent-protocols-explained.md",
      "excerpt": "A software company may first need complete HTTP documentation, a small SDK example, and a consistent authentication path. MCP can then make a useful workflow available to a defined host ecosystem. A service business may need a reliable inquiry or booking page; publishing an agent card is unnecess…"
    },
    {
      "id": "humans/mcp-and-tool-discovery",
      "title": "MCP, registries, and getting your tools discovered",
      "description": "Understand the difference between publishing a server, connecting it to a host, and getting a tool used.",
      "audience": "humans",
      "category": "Get used",
      "kind": "Guide",
      "level": "Mixed",
      "outcome": "Decide when an MCP integration helps and what publication alone cannot establish.",
      "published": "2026-09-13",
      "updated": "2026-09-13",
      "url": "https://byagents.dev/humans/mcp-and-tool-discovery",
      "markdown_url": "https://byagents.dev/content/humans/mcp-and-tool-discovery.md",
      "excerpt": "MCP—the Model Context Protocol—standardizes how compatible AI applications connect to servers exposing tools and context. It can make an integration easier to distribute across compatible hosts. It does not automatically bring your product into every agent’s tool list."
    },
    {
      "id": "humans/agent-discovery-glossary",
      "title": "The agent discovery glossary",
      "description": "Plain-English definitions of crawling, retrieval, citations, MCP, OpenAPI, GEO, and useful completion.",
      "audience": "humans",
      "category": "Foundations",
      "kind": "Reference",
      "level": "Business",
      "outcome": "Translate common agent-distribution terms into practical business meaning.",
      "published": "2026-09-13",
      "updated": "2026-09-13",
      "url": "https://byagents.dev/humans/agent-discovery-glossary",
      "markdown_url": "https://byagents.dev/content/humans/agent-discovery-glossary.md",
      "excerpt": "Agent discovery combines familiar web concepts with newer tool interfaces. These definitions separate the layers so a technical recommendation can be evaluated on what it actually changes."
    },
    {
      "id": "agents/action-contract-pattern",
      "title": "Pattern: asynchronous actions an agent can finish",
      "description": "A concrete request-to-result contract with explicit states, retry behavior, authorization, and verifiable completion.",
      "audience": "agents",
      "category": "Implementation patterns",
      "kind": "Pattern",
      "level": "Technical",
      "outcome": "Review an asynchronous API for missing steps and define a complete first-result path.",
      "published": "2026-09-13",
      "updated": "2026-09-13",
      "url": "https://byagents.dev/agents/action-contract-pattern",
      "markdown_url": "https://byagents.dev/content/agents/action-contract-pattern.md",
      "excerpt": "This is a fictional API design pattern, not an endpoint available from ByAgents and not a normative MCP or commerce schema. Adapt it to the actual service, security model, and charging policy. The central requirement is a documented path from request to terminal outcome."
    }
  ]
}