All public server reports

Endpoint report / Metadata + smoke test

Microsoft Learn MCP

A dated endpoint inspection. Metadata and any separately recorded tool call have their own evidence, scope and limitations.

Developer documentationRunner 1.1.0

What this establishes

The anonymous endpoint advertised 3 tools and passed four bounded metadata checks. A separate, fixed read-only smoke scenario is recorded below. Actual ChatGPT and Claude workflows were not tested.

The smoke result applies only to the displayed call and literal content assertions. It does not establish overall answer correctness or reliability.

Connection and metadata
Metadata checks passed
Observed tool catalog
Complete: 3 tools
Read-only smoke test
Passed · 1 call attempted
ChatGPT / Claude
Not tested / Not tested
Overall score
Not assigned

Read-only smoke test / Passed

Fetch the public Azure Functions overview.

This is one direct, fixed-input tool test. It does not exercise an AI model or a ChatGPT or Claude session. Calls attempted may include a call that returned an error or timed out.

The response passed the registered content assertions.

Smoke tool calls attempted
1
Tool
microsoft_docs_fetch
Scenario / version
learn-fetch-functions / 1
Observed at
2026-10-15T07:14:24.660Z
Runner
1.0.0
Protocol
2025-06-18
Elapsed time
171 ms
Run ID
904f5c02-9b46-4b29-8cc7-afe25eef5189
Result SHA-256
4f5a84cc1d1c1d8a6542946c227f7d09388a188ea2f75554badbc1c3fb39afd7

Exact public inputs

{
  "url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-overview"
}

Fixture assertions

  • Azure Functions: Passed
  • serverless: Passed
Recorded response excerpt
# What is Azure Functions?

Azure Functions is a serverless solution that allows you to build robust apps while using less code, and with less infrastructure and lower costs. Instead of worrying about deploying and maintaining servers, you can use the cloud infrastructure to provide all the up-to-date resources needed to keep your applications running.

You focus on the code that matters most to you, in the most productive language for you, and Azure Functions handles the rest. For a list of supported languages, see [Supported languages in Azure Functions](supported-languages).

## Scenarios

Functions provides a comprehensive set of event-driven [triggers and bindings](functions-triggers-bindings) that connect your functions to other services without having to write extra code.

The following list includes common integrated scenarios that use Functions.

| If you want to... | then... |
| --- | --- |
| [Process file uploads](functions-scenarios#process-file-uploads) | Run code when a file is uploaded or changed in blob storage. |
| [Process data in real time](functions-scenarios#real-time-stream-and-event-processing) | Capture and transform data from event and IoT so
  • One fixed public read-only request from a direct MCP client. No model selection, ChatGPT/Claude host, OAuth, private account or write behavior was tested.
  • Content assertions check the listed literal terms and absence of a tool error; they do not establish complete factual correctness, relevance or production reliability.
  • Observed call duration is one sample and includes network conditions. It is not a latency benchmark or a comparison between services.
  • Only the first tools/list page is inspected for this selected tool. No notification stream, redirect, credentials or caller-supplied scenario is allowed.
  • Response SHA-256 covers the UTF-8 JSON serialization of the SDK-parsed tool result. Only a bounded public text excerpt is retained; it is untrusted server content.

Recorded checks

These checks cover the metadata inspection. They are separate from the tool-call result above, when present.

protocol-negotiation

Negotiated protocol 2025-06-18; this does not establish host compatibility.

Passed

initialized-notification

The initialization notification received HTTP 202 with an empty body.

Passed

tool-catalog

Observed the complete advertised catalog: 3 tools across 1 pages.

Passed

tool-metadata-shape

SDK metadata shape checked for 3 observed tools. This is not complete JSON Schema validation or behavior verification.

Passed

oauth-login

OAuth discovery, login, token refresh and authenticated access are outside this anonymous inspection.

Not tested

Metadata request evidence

request-1 / initialize

2026-10-15T07:11:36.540Z

HTTP 200 · 573 ms · 1950 B

response-received

request-2 / notifications/initialized

2026-10-15T07:11:37.113Z

HTTP 202 · 170 ms · 0 B

notification-accepted

request-3 / tools/list

2026-10-15T07:11:37.283Z

HTTP 200 · 222 ms · 4950 B

response-received

Observed tool catalog

Names were advertised through tools/list. Any tool execution is recorded separately in the smoke test section.

Complete: 3 tools
  • microsoft_code_sample_search
  • microsoft_docs_fetch
  • microsoft_docs_search

Endpoint and provenance

Endpoint
https://learn.microsoft.com/api/mcp
Official source
https://learn.microsoft.com/en-us/training/support/mcp-developer-reference
Profile
Anonymous endpoint profile
Requested protocol
2025-11-25
Reported protocol
2025-06-18
Protocol
2025-06-18
Observed at
2026-10-15T07:11:37.511Z
Run ID
25dbf005-a320-4ff0-8940-82d00bd453f4
Catalog SHA-256
69a9d1086efe71ee7950a8aa47c0d02c7214485b76d14cc27c7d03bbaa296b60
Fingerprint scope
complete-catalog

SHA-256 of all observed tool objects, recursively sorted object keys and sorted canonical tool strings; schema array order is preserved. Raw descriptions, schemas and headers are not persisted.

Inspection bounds
requestTimeoutMs
5,000
runTimeoutMs
30,000
responseBytes
1,048,576
requests
7
pages
5
tools
200
Read the full methodology (English Markdown)

What this report does not establish

These observations do not establish general task success, security, OAuth behavior or ChatGPT and Claude compatibility. Read the limits of each recorded test.

  • Metadata-only anonymous inspection. No tools/call, OAuth flow, API model calls, host UI or publication review was executed. No global quality or safety score is produced.
  • Annotations are server declarations, not verified behavior. Metadata success does not establish task success, security, usefulness or ChatGPT/Claude compatibility.
  • Only active exact HTTPS endpoints in the reviewed source registry are accepted. Redirects, supplied credentials, arbitrary endpoints and OAuth URL fetching are disabled. DNS/TLS use the local runtime: this is not a hardened multi-tenant SSRF sandbox and must not be exposed as a public scanner.
  • Session identifiers are used only in memory. Request/response headers, raw error messages, raw descriptions and schemas are excluded from artifacts. Tool names and aggregate metadata remain untrusted server input.
  • Only the recorded protocol versions and bounded catalog prefix are supported. Reaching a bound or lacking access means unknown, not a failed server or a passing full audit.

What should your MCP do better?

Share a public endpoint or repository, the tasks that matter, and the clients your users use. We will discuss a pilot scope, access and price.

Discuss a benchmark

Opens your email app. Send public links only; arrange sandbox access separately.

Was this helpful?

Anonymous feedback helps us improve pages and translations.