MCP 检查 / Code and repository research
DeepWiki MCP
查看哪些检查已通过、哪些信息缺失,以及下一步该测试什么。
匿名端点检查
·测试程序 1.1.04/4
已通过的元数据检查
检查概览
元数据检查已通过
已连接到端点,其提供的工具定义通过了已记录的检查。
检查明细
选择一个类别,查看具体检查结果。
工具元数据记录情况
已观察的 3 个工具中的字段存在情况。字段存在不代表质量;输出架构和行为提示是可选项。
3 项中有 3 项已记录
逐项工具详情
仅记录字符数,未评估描述内容。
- ask_wiki_question108 个字符
- read_wiki_contents45 个字符
- read_wiki_structure59 个字符
3 项中有 3 项已记录
逐项工具详情
仅检查根结构,未评估完整模式的有效性。
- ask_wiki_questiontrue
- read_wiki_contentstrue
- read_wiki_structuretrue
3 项中有 3 项已记录
逐项工具详情
这是可选的输出约定;需通过执行测试确认响应是否符合约定。
- ask_wiki_questiontrue
- read_wiki_contentstrue
- read_wiki_structuretrue
3 项中有 0 项已记录 · 3 项未知
逐项工具详情
声明为 true 或 false 都计为已记录。实际行为未经验证。
- ask_wiki_question未记录
- read_wiki_contents未记录
- read_wiki_structure未记录
3 项中有 0 项已记录 · 3 项未知
逐项工具详情
声明为 true 或 false 都计为已记录。实际行为未经验证。
- ask_wiki_question未记录
- read_wiki_contents未记录
- read_wiki_structure未记录
请求耗时
这些是本次运行中的单次观测值,不是性能基准测试。
测试范围
- OAuth
- 未测试
- ChatGPT
- 未测试
- Claude
- 未测试
- 总体质量评级
- 未评级
元数据检查通过,并不能证明登录、客户端兼容性或任务可靠性。
执行检查
通过Read the documentation structure for the public MCP TypeScript SDK repository.
使用固定输入的直接 MCP 场景。未使用 AI 模型或 ChatGPT / Claude 会话。
查看请求记录下一步
检查行为提示
检查源定义,准确声明只读或破坏性行为。这些可选提示不代表已验证的行为。
涉及的工具: ask_wiki_question, read_wiki_contents, read_wiki_structure
测试实际客户端工作流
选定任务和预期结果,然后在用户依赖的客户端中验证。
运行详情与原始检查记录
请求、输入、响应、工具列表、来源和测试限制
运行详情与原始检查记录
请求、输入、响应、工具列表、来源和测试限制
以下原始证据与技术观察保留英文。
只读冒烟测试 / 通过
Read the documentation structure for the public MCP TypeScript SDK repository.
这是一项使用固定输入的直接工具测试,不涉及 AI 模型或 ChatGPT、Claude 会话。调用尝试数可能包含报错或超时的调用。
The response passed the registered content assertions.
- 冒烟测试工具调用尝试数
- 1
- 工具
- read_wiki_structure
- 场景与版本
- deepwiki-sdk-structure / 1
- 观察时间
- 2026-10-15T07:14:27.385Z
- 测试程序
- 1.0.0
- 协议
- 2025-11-25
- 耗时
- 227 ms
- 运行 ID
- a5a04e58-5e73-4fc6-a76c-d0d026b14d56
- 结果 SHA-256
- e72d38e266509e4d6af6d167e83f3ec2de644b05d5455dfbfeba9e649bddadb3
准确的公开输入
{
"repoName": "modelcontextprotocol/typescript-sdk"
}固定场景断言
- modelcontextprotocol/typescript-sdk: 通过
记录的响应摘录
Available pages for modelcontextprotocol/typescript-sdk:
- 1 Overview
- 1.1 Installation and Setup
- 1.2 Monorepo Structure and Packages
- 1.3 Core Protocol Concepts
- 2 Architecture
- 2.1 Protocol Foundation
- 2.2 Type System and Message Schemas
- 2.3 Communication Lifecycle
- 2.4 Wire Codecs and Era-Aware Schemas
- 3 Server Implementation
- 3.1 McpServer High-Level API
- 3.2 Tool Registration and Execution
- 3.3 Resource and Prompt Management
- 3.4 Low-Level Server Protocol Class
- 3.5 Serving over HTTP
- 3.6 Middleware Integration
- 3.7 Serving over Stdio
- 3.8 Server Examples and Patterns
- 4 Client Implementation
- 4.1 Client Class and High-Level API
- 4.2 Streamable HTTP Client Transport
- 4.3 SSE Client Transport
- 4.4 Stdio and In-Memory Transports
- 4.5 Response Caching
- 4.6 Client Examples and Patterns
- 5 OAuth Authentication
- 5.1 OAuth Client Flow and Providers
- 5.2 Machine-to-Machine Authentication
- 5.3 OAuth Server Integration
- 6 Transport System
- 6.1 Transport Interface and Contract
- 6.2 Transport Comparison and Selection
- 7 Advanced Features
- 7.1 Session Management and Resumability
- 7.2 Elicitation a- 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.
已记录的检查
这些检查针对元数据。若上方存在工具调用结果,该结果与这些检查分别记录。
protocol-negotiation
Negotiated protocol 2025-11-25; this does not establish host compatibility.
initialized-notification
The initialization notification received HTTP 202 with an empty body.
tool-metadata-shape
SDK metadata shape checked for 3 observed tools. This is not complete JSON Schema validation or behavior verification.
oauth-login
OAuth discovery, login, token refresh and authenticated access are outside this anonymous inspection.
元数据请求证据
request-1 / initialize
2026-10-15T07:11:36.823Z
HTTP 200 · 1129 ms · 3829 B
response-received
request-2 / notifications/initialized
2026-10-15T07:11:37.952Z
HTTP 202 · 140 ms · 0 B
notification-accepted
request-3 / tools/list
2026-10-15T07:11:38.092Z
HTTP 200 · 183 ms · 1608 B
response-received
观察到的工具目录
工具名称来自 tools/list 的声明。工具执行情况单独记录在冒烟测试部分。
完整目录:3 个工具
- ask_wiki_question
- read_wiki_contents
- read_wiki_structure
端点与来源
- 端点
- https://mcp.deepwiki.com/mcp
- 官方来源
- https://docs.devin.ai/work-with-devin/deepwiki-mcp
- 配置
- Anonymous endpoint profile
- 请求的协议
- 2025-11-25
- 返回的协议
- 2025-11-25
- 协议
- 2025-11-25
- 观察时间
- 2026-10-15T07:11:38.285Z
- 运行 ID
- b7e99b3f-5a4c-4edb-b0c6-5e92c74b8b72
- 目录 SHA-256
- 1cf852f73fb778b1c76a684ee85d786790a9e0705dfd2345f264602697432bd3
- 指纹范围
- 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.
检查限制
- requestTimeoutMs
- 5,000
- runTimeoutMs
- 30,000
- responseBytes
- 1,048,576
- requests
- 7
- pages
- 5
- tools
- 200
这份报告无法证明什么
这些观察不能证明一般任务成功率、安全性、OAuth 行为或 ChatGPT 与 Claude 兼容性。请查看每项测试的具体限制。
- 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.
Compare actual extraction results
Our web-to-Markdown benchmark tests shared pages and shows the content checks behind every result.
View the benchmark