Google Search Console MCP

io.github.sonnivasquez由 GitHub 账号 sonnivasquez 发布v1.1.0更新于 Nov 5, 2026

Local, read-only Google Search Console MCP server. Quick Connect needs no Cloud project.

概览

AI 生成的概览

本地运行的 Google Search Console MCP 服务器,让助手查询你自己的 GSC 表现、索引与站点地图数据并做 SEO 分析。

可以做什么
  • 查询搜索表现:总量、时间线、周期对比、细分维度、页面与查询明细
  • 发现 SEO 候选:低点击率、接近首页、内容衰退、页面互相竞争、内容选题
  • 检查索引与站点地图:网址检查、站点地图状态、索引抽样、页面与图片审计
  • 审计链接与迁移:有界站内链接图、新旧网址映射核对
  • 分析变化:流量下滑拆解、变更影响历史、与 Google 更新的时间重合
  • 生成报告与导出:确定性 Markdown 报告、本地数据集导出、结论核验
适用场景
适合为自己拥有的站点做 SEO 时使用:让助手直接读取 Search Console 数据,比较周期、找出表现偏弱的页面或查询、查看索引状态,或不必手工导出 CSV 就能整理表现报告。
运行要求
以 stdio 本地运行,需要 Node.js 22 或更高版本(npm 或 Bun)。需要一个能访问 Search Console 资源的 Google 账号,并通过 GSC_SITE_URLS 指定允许访问的资源。认证方式为 Quick Connect 浏览器登录(GSC_AUTH_MODE=oauth)、自建 OAuth 客户端(GSC_OAUTH_CLIENT_ID 与 GSC_OAUTH_CLIENT_SECRET 或 GSC_OAUTH_SECRETS_FILE),或服务账号密钥文件(GSC_KEY_FILE)。
安装前请注意
默认只读;GSC_ACCESS_MODE=full 会开启向 Google 提交网址和站点地图,Quick Connect 不支持完整权限。本地导出与变更历史需分别设置 GSC_EXPORTS=1 或 GSC_HISTORY=1 才启用。OAuth 令牌保存在 GSC_DATA_DIR(默认 ~/.gsc-mcp)。工具返回结果会交给 MCP 客户端,可能被发送给其 AI 服务商,因此 GSC 数据不一定留在本机。审计会抓取你的页面及引用的图片,包括外部主机上的图片。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Google Search Console MCP,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Google Search Console MCP server

[npm version] [License: Apache-2.0] [GitHub stars]

[Glama score]

[Google Search Console MCP server]

A local Google Search Console MCP server to compare search performance, find SEO opportunities, and check URL indexing status from your AI assistant using your own Google Search Console data.

GSC MCP is an open-source MCP server by Sonni Vasquez. It runs locally over stdio with Node.js or Bun and provides 34 tools. Google API requests run from your machine, with read-only Google access by default and access limited to the properties you select.

Website · npm package · Quickstart · Guía en español · Tool catalog

This is an independent project, not an official Google product.

Install with npx

The buttons and snippets below start the local stdio server with npx -y @sonnivasquez/gsc-mcp. They set GSC_AUTH_MODE=oauth and GSC_ACCESS_MODE=readonly. They do not sign you in to Google and they do not choose a property. Node.js 22 or newer is required. After the client starts the server, set GSC_SITE_URLS to your Search Console property and run gsc auth login or gsc setup. Quick Connect uses the shared read-only OAuth client shipped in this package, so you do not create a Google Cloud project for that path.

[Install in Cursor] [Install in VS Code]

Claude Code

Replace sc-domain:example.com with your Search Console property id:

bash
claude mcp add gsc-mcp -e GSC_AUTH_MODE=oauth -e GSC_ACCESS_MODE=readonly -e GSC_SITE_URLS=sc-domain:example.com -- npx -y @sonnivasquez/gsc-mcp

JSON config

Same command, for a client that reads mcpServers. Replace the example property:

json
{  "mcpServers": {    "gsc-mcp": {      "command": "npx",      "args": ["-y", "@sonnivasquez/gsc-mcp"],      "env": {        "GSC_AUTH_MODE": "oauth",        "GSC_ACCESS_MODE": "readonly",        "GSC_SITE_URLS": "sc-domain:example.com"      }    }  }}

Why this one

Quick Connect is the path that skips creating a Google Cloud OAuth client. Custom OAuth and service accounts in this same server still use credentials you create. Both paths run locally.

Quick Connect in this serverYour own Google credentials
Google Cloud projectNot required. This package ships a shared read-only OAuth client.Custom OAuth needs your client (GSC_OAUTH_SECRETS_FILE, or GSC_OAUTH_CLIENT_ID plus GSC_OAUTH_CLIENT_SECRET). A service account needs GSC_KEY_FILE.
Where it runsLocal stdio process. Google API requests run from your machine.Same local process.
Default accessRead-only. Setup refuses full access for Quick Connect.Read-only unless GSC_ACCESS_MODE=full. That mode enables gsc_submit_url, gsc_submit_batch, and gsc_submit_sitemap.
Tools34 gsc_* tools registered by the server.The same 34 tools.
Also registered heregsc_genai_conversation_queries, gsc_check_update_impact, and gsc_image_page_audit.The same tools.

gsc_genai_conversation_queries reads AI-conversation exhaust in query data. gsc_check_update_impact compares a drop window with confirmed ranking updates and reports temporal coincidence only. gsc_image_page_audit fetches your own pages and their image bytes.

What you can do

SEO taskWhat GSC MCP returnsExample tools
Understand a traffic changeClicks, impressions, CTR, average position and period comparisons by page or querygsc_performance_overview, gsc_compare_periods, gsc_analyze_traffic_drop
Prioritize pages and queriesCandidates with low CTR, weak positions or declining traffic, using explicit thresholdsgsc_find_opportunities, gsc_content_decay
Review competing pagesQueries served by multiple pages on your site, with evidence for editorial reviewgsc_detect_cannibalization, gsc_query_pages
Inspect indexing and sitemapsGoogle's indexed view of selected URLs and registered sitemap statesgsc_inspect_urls, gsc_list_sitemaps
Compare segmentsBrand terms, site folders, countries, devices, or web versus image searchgsc_analyze_segments, gsc_compare_web_image
Audit on-page imagesFindings from downloading your own pages and their referenced imagesgsc_image_page_audit
Audit a page or an index sampleCurrent HTTP HTML and exact-page queries, or indexed-view inspection from sitemap discoverygsc_page_audit, gsc_indexing_audit
Review internal linksBounded HTML link graph and literal suggestionsgsc_internal_link_audit
Evaluate changes or a migrationObserved before/after metrics and declared URL mappingsgsc_change_impact, gsc_migration_audit
Prepare reportsMarkdown reports and optional local dataset exportsgsc_generate_report, gsc_export_dataset

These are analysis tools. Opportunity and cannibalization results are candidates to review, not proof that a particular SEO change will improve rankings.

Get started

You need Node.js 22 or newer, npm or Bun, and a Google account with access to a Search Console property. Bun can install the package and run the MCP server; the global gsc CLI still requires Node.js.

bash
npm install -g @sonnivasquez/gsc-mcpgsc setup

Setup guides you through:

  1. Sign in to Google. Choose read-only Quick Connect, or use your own OAuth client or a service account.
  2. Choose properties. Select the Search Console properties this server may access.
  3. Connect your client. Review and approve the configuration preview. Setup preserves other MCP servers.

Quick Connect uses a shared Desktop OAuth application and needs no Google Cloud project setup. Complete Google sign-in in your browser. Never paste passwords, OAuth credentials or tokens into an AI chat.

Check your local installation and saved authentication state:

bash
gsc doctorgsc auth status

To check access with a minimal request to Google, run gsc auth status --online. Restart your MCP client if the tools do not appear.

Other installation options

With Bun as the package manager:

bash
bun install -g @sonnivasquez/gsc-mcpgsc setup

The shell installer installs the latest package globally and opens setup. It uses npm by default and does not use sudo:

bash
curl -fsSL https://gscmcp.dev/install.sh | sh

To use Bun with the installer:

bash
curl -fsSL https://gscmcp.dev/install.sh | sh -s -- --manager bun

Read the installer or follow the quickstart for details.

Supported clients

Guided setup supports Claude Desktop, Claude Code, Cursor, Codex, OpenCode and Pi. It can also print JSON for another compatible MCP client. GSC MCP uses local stdio, so the client must support launching a local server.

See client setup instructions. Use gsc setup --dry-run to preview changes or gsc setup --verbose for configuration details. OpenCode and Pi configuration is global.

Install with your AI agent

Copy this prompt into an agent that can run terminal commands. You complete Google sign-in yourself:

text
Install @sonnivasquez/gsc-mcp globally with npm, or Bun if I prefer, then run gsc setup.Use read-only Quick Connect. Help me sign in to Google, choose my Search Consoleproperties and connect my MCP client while preserving other MCP servers.Never ask me to paste credentials or tokens into chat. Verify with gsc doctorand tell me whether I need to restart my client. Do not query Search Consoleuntil I ask.

Try it with your site

After setup, ask your assistant to list the properties it can access. Use an exact property identifier such as sc-domain:example.com or https://example.com/ in subsequent requests.

The prompts below are examples, not measured results:

text
For sc-domain:example.com, compare the last 28 days with the previous period.Show the pages with the largest observed click losses, including impressions,CTR and average position. State the dates and coverage of the returned data.
text
Find queries for sc-domain:example.com with at least 500 impressions and CTRbelow 2% in the last 28 days. Show their ranking pages and prioritize candidatesfor a title and snippet review. Do not edit the site.
text
Inspect these three URLs on my selected property and show Google's indexedstatus for each. Then list its registered sitemaps. Do not submit anything.

You can also ask for pages with sustained traffic declines, query overlap across your own pages, brand versus non-brand segments, or a Markdown performance report. Saving reports and exporting datasets require GSC_EXPORTS=1 in your MCP client's server environment. Restart the client after changing that environment.

On-demand website audits and change history

Version 1.1.0 adds gsc_page_audit, gsc_indexing_audit, gsc_internal_link_audit, gsc_change_impact, and gsc_migration_audit. They combine bounded HTTP HTML or sitemap reads with your own GSC data. They do not render JavaScript or run in the background; client-rendered content and links remain unknown. Continue batches explicitly using nextCursor; sessions expire after 15 idle minutes.

GSC_HISTORY=1 enables explicit local change records and saved measurements, independently of GSC_EXPORTS. Transient before/after analysis needs no history. Results may be partial even when the scheduled work completes: check status, coverage and warnings. Full evidence may require gsc_get_dataset. No alerts service, scheduler or automatic captures are installed. See audit inputs, limits, evidence pagination and examples. These audits require version 1.1.0 or later. Check gsc_capabilities in the running server after updating and restarting your MCP client.

Authentication and access

ConnectionRequirementsAccess
Quick ConnectBrowser sign-in with a Google account that can access the propertyRead-only, using the shared OAuth application
Custom OAuthYour own Google Cloud OAuth client and browser sign-inRead-only, or full access after explicit configuration
Service accountYour own credentials file and permissions for the propertyRead-only, or full access after explicit configuration

Read-only access blocks Google write operations. Full access uses GSC_ACCESS_MODE=full and enables sitemap submission and eligible Indexing API URL notifications. Setup asks for separate confirmation before enabling writes. Quick Connect does not support full access.

URL Inspection reads Google's indexed view; it does not request indexing. Indexing API submissions have eligibility and permission requirements and do not guarantee indexing. See the credentials guide and tool catalog before enabling writes.

Choosing all properties also includes future properties and requires an explicit confirmation. Setup's --yes option does not enable writes, a sample query, or the optional agent skill.

Privacy and data limits

GSC MCP has no hosted MCP backend or product telemetry. OAuth tokens stay in your local data directory, ~/.gsc-mcp/ by default, or GSC_DATA_DIR. Quick Connect shares an OAuth application and its Google API quotas; it does not share your tokens or property access with the maintainer.

Website audits fetch selected pages, robots.txt and sitemaps directly from authorized properties. The image audit also fetches referenced images, including images served by external public hosts.

Tool responses go to your MCP client and may be sent to its AI provider. Local execution does not mean your Search Console data stays entirely on your machine. Review your client's retention and training settings and the privacy policy.

When interpreting results:

  • Date presets such as last_28_days end three days before today in Pacific Time. This is a conservative product default, not a guarantee of Google's data availability.
  • Search Console returns limited rows and coverage. Missing rows are not necessarily zero traffic.
  • Average position is an impression-weighted average, not a live rank tracker.
  • Traffic drops and overlap with Google updates do not establish causation.
  • URL Inspection does not trigger a live crawl or guarantee indexing.
  • Alerts run on demand; GSC MCP does not continuously monitor your site.

Update or uninstall

Check for a newer release without installing it:

bash
gsc update --check

Run gsc update for an assisted reinstall and verification, or reinstall with your package manager. Check gsc --version and restart your MCP client after updating.

Uninstall with npm uninstall -g @sonnivasquez/gsc-mcp or bun remove -g @sonnivasquez/gsc-mcp. Removing the package does not revoke Google access or delete saved tokens. Follow the uninstall guide to remove local data or revoke access.

Documentation

Development

bash
npm cinpm run typecheck:nodenpm run test:node

For Bun, build with bun run build and run bun --test test. The package includes an optional Google Search Console MCP agent skill, available from setup with --install-skill.

License and attribution

Apache-2.0. Copyright Sonni Vasquez.

If this server helps, star the repo: https://github.com/sonnivasquez/gsc-mcp

来源:README.md,提交 545ab5f

工具

34

gsc_page_audit

Audit 1-5 own URLs: HTTP HTML, metadata, directives and exact-page GSC queries. Literal matches only; no JavaScript rendering or automatic edits. On demand; use nextCursor to continue explicitly.

输入参数urlscursorpresetendDatesiteUrl必填startDateresultLimit

gsc_indexing_audit

Discover own sitemap URLs and inspect Google's indexed view, up to 10 per explicit call. Indexed state is not a live test; samples do not describe whole-site indexation. Never submits URLs.

输入参数urlscursorpresetendDatesiteUrl必填selectionstartDateresultLimitsitemapUrlsinspectLimit

gsc_change_impact

Record/list/delete changes or analyze before/after metrics on request. GSC_HISTORY=1 enables local history independently of exports; analyze can be transient. saveSnapshot requires a saved changeId. No scheduler, notifications or causal attribution.

输入参数afteraction必填beforechangecursorpresetendDatesiteUrl必填changeIdbatchSizestartDatecontrolUrls另有 3 个

gsc_migration_audit

Audit declared old/new URL mappings across authorized properties: redirects, destination HTML, indexed status and before/after metrics. Explicit batches; no edits or indexing submissions; no ranking guarantees.

输入参数afterbeforecursorpresetendDatemappingsbatchSizestartDateresultLimitmigrationDatesourceSiteUrl必填targetSiteUrl必填

gsc_submit_url

Send an Indexing API notification for an updated or deleted URL. Google supports this API for JobPosting and livestream BroadcastEvent pages; a notification does not guarantee crawling or indexing. Requires write access and appropriate credentials. IMPORTANT: Base your analysis ONLY on the data returned. Report exact numbers from the results. Do not speculate about causes (e.g. algorithm updates, competitor actions) unless the data explicitly supports it. If the data does not contain enough information to answer a question, say so clearly rather than guessing.

输入参数url必填action

gsc_submit_batch

Send up to 200 Indexing API notifications. Google supports this API for JobPosting and livestream BroadcastEvent pages; notifications do not guarantee crawling or indexing. Requires write access and appropriate credentials; quota applies. IMPORTANT: Base your analysis ONLY on the data returned. Report exact numbers from the results. Do not speculate about causes (e.g. algorithm updates, competitor actions) unless the data explicitly supports it. If the data does not contain enough information to answer a question, say so clearly rather than guessing.

输入参数urls必填action

gsc_submit_sitemap

Submit a sitemap to Google Search Console. Submission does not guarantee crawling or indexing. Requires write access and appropriate credentials. IMPORTANT: Base your analysis ONLY on the data returned. Report exact numbers from the results. Do not speculate about causes (e.g. algorithm updates, competitor actions) unless the data explicitly supports it. If the data does not contain enough information to answer a question, say so clearly rather than guessing.

输入参数site_url必填sitemap_url

gsc_genai_conversation_queries

Surface AI-conversation exhaust hiding in your regular query data: bare replies to Google's AI ('yes', 'go on'), 'what about X' pivot follow-ups, conversational questions, AI-visibility tracker probes, and full agent prompts logged as queries. Google counts every AI Mode follow-up as a new query and folds AI Mode/AI Overviews into the web search type, so these fragments carry real impressions, positions and clicks. The dedicated Generative AI report has no query dimension; this is the only query-level AI evidence available anywhere. Classifies every match into seven buckets with landing pages, plus a monthly timeline showing when reply-artefacts first appeared on your site. Treat probe and harness buckets as machine traffic, not demand. Pulls abort over 50k rows per request. IMPORTANT: Base your analysis ONLY on the data returned. Report exact numbers from the results. Do not speculate about causes (e.g. algorithm updates, competitor actions) unless the data explicitly supports it. If the data does not contain enough information to answer a question, say so clearly rather than guessing. PRESENTATION: Always present these results as a rich, interactive visualization using artifacts. Use summary cards for key metrics, colour-coded indicators for severity or change direction (green for positive, red for negative), bar charts or sparklines for comparisons, and tabbed sections to organise different categories of results. Make the output visually scannable and dashboard-like rather than plain text or raw tables. POSITION: position is an impression-weighted average over real impressions, blended across queries, devices and countries. It is not a rank-tracker rank. Deep positions are only recorded when a user actually reaches that part of the results, so values beyond page one rest on sparse data. Treat absolute positions as directional and prefer position deltas between periods when judging change.

输入参数dayssite_url必填min_impressionsinclude_timelinemax_rows_per_bucket

gsc_image_page_audit

Fetches pages from YOUR OWN site and audits every image on them for the on-page factors that drive image-search performance: missing/empty/generic/duplicate alt text, non-descriptive filenames, missing width/height attributes, lazy loading on the LCP candidate, srcset coverage, file format and weight, intrinsic dimensions vs Google's ~250x200 indexing minimum, ImageObject and licensable schema, max-image-preview, inline background images, and optionally metadata inside image files (camera EXIF and GPS that should be stripped, IPTC Creator/Copyright/Caption that should survive, XMP DigitalSourceType on AI-generated images). Find candidate page URLs with gsc_search_analytics using searchType=image and dimensions=[page], then audit selected pages. Page URLs must belong to the instance allowlist and every fetch stays on public hosts with redirects revalidated; images may be fetched from public CDN hosts. Returns a per-image findings table, page-level checks, and an ordered top_fixes list. IMPORTANT: Base your analysis ONLY on the data returned. Report exact numbers from the results. Do not speculate about causes (e.g. algorithm updates, competitor actions) unless the data explicitly supports it. If the data does not contain enough information to answer a question, say so clearly rather than guessing. PRESENTATION: Always present these results as a rich, interactive visualization using artifacts. Use summary cards for key metrics, colour-coded indicators for severity or change direction (green for positive, red for negative), bar charts or sparklines for comparisons, and tabbed sections to organise different categories of results. Make the output visually scannable and dashboard-like rather than plain text or raw tables.

输入参数urls必填fetch_metadatamax_images_per_pagemax_images_reported

gsc_capabilities

What this server can do: tools, auth state, limits and instance allowlist. Works offline, no credentials needed.

无需输入参数。

gsc_list_sites

GSC properties visible to this instance. Preserves the exact siteUrl identifier.

无需输入参数。

gsc_search_analytics

Flexible performance query with explicit coverage. Sort applies to the retrieved dataset, not to all Google data.

输入参数sortByendDate必填filterssiteUrl必填dataStatestartDate必填dimensions必填searchTyperesultLimitmaxFetchRowssortDirectionaggregationType

gsc_inspect_urls

Index inspection for 1-10 URLs. Per-URL results in input order; one failure never discards the successes.

输入参数urls必填siteUrl必填languageCode

gsc_list_sitemaps

Registered sitemaps and their reported states. Readonly; never submits.

输入参数siteUrl必填

gsc_get_dataset

Page through a previous result with zero new Google calls. Datasets expire after 15 minutes and never cross profiles.

输入参数limitcursorcolumnsdatasetId必填

gsc_performance_overview

Totals, timeline and optional comparison for a site. Totals come from the aggregate row, never from summing a top.

输入参数presetendDatesiteUrl必填baselinedataStatestartDatesearchTypeincludeTimelineincludeComparison

gsc_compare_periods

Deterministic period comparison. Absent keys stay in their own blocks, never as zeros.

输入参数presetendDateorderBysiteUrl必填baselinedimension必填startDateresultLimitmaxFetchRowssortDirection

gsc_page_queries

Observed queries for one exact page URL. No title/H1/intent inference.

输入参数presetendDatepageUrl必填siteUrl必填startDateresultLimitmaxFetchRows

gsc_query_pages

Observed pages for one exact query. Two URLs sharing a query is a candidate, never proof of harm.

输入参数query必填presetendDatesiteUrl必填startDateresultLimitmaxFetchRows

gsc_find_opportunities

Review candidates by transparent rule: low_ctr, striking_distance, declining, ctr_benchmark, low_clicks. Heuristics with versioned thresholds, never diagnoses.

输入参数kind必填maxCtrpresetendDatesiteUrl必填dimensionmaxClicksstartDatetargetCtrwindowDaysmaxPositionminPosition另有 5 个

gsc_detect_cannibalization

Queries served by several of your own pages. Candidates for editorial review, never consolidation orders.

输入参数presetendDatesiteUrl必填minPagesstartDateminSharePctresultLimitmaxFetchRowsincludeTimelinetimelineQueryLimitminDailyImpressionsminImpressionsPerPage

gsc_analyze_segments

Compare caller-defined segments (brand terms, folders, countries, devices) over one retrieved dataset. Groups may overlap.

输入参数presetendDatesiteUrl必填segments必填startDateresultLimitmaxFetchRows

gsc_export_dataset

Export a previous dataset to this machine (json/csv/markdown). Requires GSC_EXPORTS=1. Never overwrites, never uploads.

输入参数nameformat必填datasetId必填

gsc_analyze_traffic_drop

Traffic-drop decomposition: observed signals, hypotheses and missing evidence. Correlation is not causation.

输入参数presetendDatesiteUrl必填baselinedimensionstartDateminAbsLossresultLimitmaxFetchRows

gsc_content_decay

Three-window decline candidates for web or image. Sustained fall only; anything less is not a finding.

输入参数presetendDatesiteUrl必填dimensionstartDatesearchTypewindowDaysresultLimitmaxFetchRowsminBaseClicksminDeclinePct

gsc_check_alerts

On-demand rule evaluation with stable alert ids. Not continuous monitoring.

输入参数presetendDatesiteUrl必填baselinedimensionstartDateresultLimitctrDropPpMinmaxFetchRowsminClickLosspositionWorseByMindisappearedMinClicks

gsc_content_candidates

Observed queries at weak positions with their observed pages. Review, do not auto-create.

输入参数presetendDatesiteUrl必填maxExpandstartDateminPositionresultLimitmaxFetchRowsminImpressions

gsc_content_recommendations

Prioritized action candidates with recoverable evidence. Nothing is edited automatically.

输入参数presetendDatesiteUrl必填startDatecategoriesresultLimitmaxFetchRowsmaxRecommendations

gsc_multi_site_overview

Per-property health with isolated failures and a shared budget. Never sums properties.

输入参数sites必填presetendDatestartDateresultLimitmaxFetchRowsincludeComparison

gsc_generate_report

Deterministic markdown report from tool outputs. No model involved; save is export-gated.

输入参数savesitespresetendDatesiteUrlsectionsstartDate

gsc_verify_claim

Check one structured claim against comparable evidence: verified, contradicted or unverifiable.

输入参数value必填metric必填presetendDatesiteUrl必填dataStatestartDatesearchTypetoleranceAbstoleranceRelcompareWithBaseline

gsc_compare_web_image

Web vs image surfaces joined by key. Separate universes: no audience sums, no CTR transfer.

输入参数presetendDatesiteUrl必填dimensionstartDateresultLimitmaxFetchRows

gsc_check_update_impact

Correlate a traffic-drop window with confirmed Google ranking updates (core, spam, reviews) from the public Search Status Dashboard. Reports temporal coincidence only, never causation. Dashboard history starts Dec 2022.

输入参数presetendDatesiteUrl必填baselinedimensionstartDateminAbsLossupdateTyperesultLimitmaxFetchRows

版本历史

1
  1. v1.1.0最新Nov 5, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分