原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

aflink: search AF links

✓ 服务方 · aflink.us

作者:dadatuputi版本 1.0.0i★ 5 (整个仓库的星标)i在云端运行官方网站 ↗
注册名称us.aflink/search

安装方法

能做什么

Read-only search of aflink.us, a public mirror of the U.S. Air Force portal quick links.

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 无需密钥
  • 分类 搜索与 AI 记忆

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

作者:google-research★ 35,6381 个 skill

Skill · 操作手册

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

作者:BigBodyCobain★ 11,6051 个 skill

Skill · 操作手册

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

作者:gosom★ 8,2361 个 skill

Skill · 操作手册

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-11-07

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 4/4 项(仅展示,不用于排序)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 aflink: search AF links。按照 https://mcp.popnx.com/i/us-aflink-search.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/4 项检查 · 你的提问会经过开发者的服务器(api.aflink.us) · ✓ 命令已检查 2026年11月20日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称aflink: search AF links
    Remote MCP server URL · 地址https://api.aflink.us/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +Connectorsaflink: search AF links

  4. 试一试

    用 aflink: search AF links 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 aflink: search AF links,或回答中出现 aflink: search AF links 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称aflink: search AF links
    Connection · 地址https://api.aflink.us/mcp
  3. 在聊天中选择 aflink: search AF links

    开启新聊天,输入前先从插件列表中选择 aflink: search AF links

  4. 试一试

    用 aflink: search AF links 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 aflink: search AF links,或回答中出现 aflink: search AF links 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user search https://api.aflink.us/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 aflink: search AF links 在列表中并显示已连接

  4. 试一试

    用 aflink: search AF links 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 aflink: search AF links,或回答中出现 aflink: search AF links 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 aflink: search AF links 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 aflink: search AF links,或回答中出现 aflink: search AF links 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 aflink: search AF links 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 aflink: search AF links,或回答中出现 aflink: search AF links 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://api.aflink.us/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 aflink: search AF links 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user search https://api.aflink.us/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "search": {
      "url": "https://api.aflink.us/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "search": {
      "type": "http",
      "url": "https://api.aflink.us/mcp"
    }
  }
}

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

GitHub 星标i
5 (整个仓库的星标)
该仓库包含多个 MCP 条目,星标在排名中只计算一次
每周下载量i
不在 npm/PyPI 上
已验证域名
✓ aflink.us
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.0.0
发布到注册中心i
2026年11月8日
代码最后更新i
2026年11月20日
最近检查
2026年11月17日
作者
dadatuputi
网站
aflink.us
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月17日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • search_links

    Search aflink.us for Air Force and DoD websites by name, acronym, URL, category or purpose (for example "mypay", "travel voucher", "leave"). Every word must match. Returns each link's title, URL and category, best matches (title matches) first. Links in the UNOFFICIAL category ar

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 aflink.us 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • – 不适用

    有许可证

    不适用:由 aflink.us 的所有者自己运行的云端服务器,你不会运行仓库里的代码

  • ✓ 通过

    端点有响应

    在 71 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 1 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/us-aflink-search.svg)](https://mcp.popnx.com/en/servers/us-aflink-search)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 6470 个服务器的 76%
  • 发布到注册中心的时间比此分类中其他 6470 个服务器的 76% 更新
  • 基础检查结果等于或优于此分类中其他 6470 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

aflink: search AF links 安全吗?

它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于今天,最新版本(1.0.0)于12天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

作者:every-app广泛使用★ 2.8万6天前更新

在云端运行✓ everyapp.com

Exa

Official Exa MCP for web search, content fetching, and multi-step research.

作者:exa-labs广泛使用★ 5245今天更新

在云端运行✓ 服务方 · exa.aiPopNx 团队已实际试用

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

作者:MicrosoftDocs广泛使用★ 200012个月前更新

在云端运行✓ 服务方 · microsoft.comPopNx 团队已实际试用

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

作者:proxysoul正在增长★ 16282个月前更新

在云端运行✓ empryo.com
与相似项目对比
本项
aflink: search AF links
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是是是否否
基础检查4/45/52/44/44/44/4
许可证MITMITMITCC-BY-4.0NOASSERTIONApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Search worker

Cloudflare Worker behind the address-bar autocomplete (OpenSearch suggestions) for aflink.us, and aflink's public, read-only MCP server. Deployed as aflink-autocomplete and served at https://api.aflink.us; the site points at it through suggestedURL in updater.js, which the browser discovers via osdd.xml.

How a suggestion round trips

  1. The browser calls GET /search/{searchTerms} while the user types.
  2. The worker answers [" ", [" {CATEGORY}", ...]] — the title, a zero-width space, then the category.
  3. Picking one loads aflink.us/?q= .
  4. The page (src/includes/js/search.js) sees the zero-width space, searches on the title, finds the row whose title *and* category match the suggestion, and follows it.

So a suggestion is only useful if the page can find the same link. Anything the worker offers that the page hides, or matches differently, is a dead suggestion — the user picks it and lands somewhere else, or nowhere.

Staying in sync with the site

Two things keep the two ends together, and both are load-bearing:

  • Matching rules live in src/includes/js/search-match.js. The page inlines that file; this worker imports it. There is one implementation, so normalization, multi-word matching, title/URL/category matching and the ranking score cannot drift. Change matching there and both ends move together. While searching, the page lists its rows in score order, ties in page order, which is the order this worker suggests them in.
  • The link list is assembled from src/links/ by scripts/assemble-links.js, which both builds run: updater.js for the site and its links.json, and build-links.js for this worker, which bundles the result in the links.json shape. The worker rebuilds what the page displays from it: official categories in page order (skipping isDeleted links, which the page hides), then the unofficial list.

npm test in the repo root covers both — including checks that the links.json the site build actually produces is what the worker reads, and that the worker's bundle holds the same links.

Deploys

Cloudflare Workers Builds deploys the worker on every push to master that touches one of its watch paths, running cd search_worker && npx wrangler deploy. Wrangler first runs the build command in wrangler.jsonc, node build-links.js, which writes src/links.generated.js (gitignored) from that commit's src/links/. So the deployed worker carries exactly the links the commit lists: nothing is fetched at request time and nothing is cached.

That only works if a link-only change triggers a build, so the watch paths (Workers & Pages → aflink-autocomplete → Settings → Build) must cover everything the worker is built from:

search_worker/*

src/links/* src/includes/js/search-match.js scripts/assemble-links.js scripts/link-status.js

A new file the worker or build-links.js imports goes on that list too. Retirement is by date (scripts/link-status.js), so a link that retires without any commit leaves the worker at the next link change; the weekly link health commit bounds that to a week.

Changes that need the worker updated
Change on the siteWhat the worker needs
How search matches or ranks (normalizing, word splitting, what fields count, score)Nothing, if the change is made in search-match.js; the worker imports it
A new field or source of links (another section, another JSON file)Add it in assemble-links.js (both builds pick it up); publishedLinks(), build-links.js's slim() and to_entries() must carry it, and a new file needs a watch path
A link becoming hidden on the page (a new flag like isDeleted)to_entries() must filter it out too
Renaming or restructuring links.jsonto_entries() reads the new shape
How the page resolves a chosen suggestion (?q= parsing)The suggestion format here has to match it

MCP server (POST /mcp)

The same worker is a Model Context Protocol server, so an AI agent can look up an Air Force or DoD site the way a person does on aflink.us. It is listed in the MCP Registry as us.aflink/search. The Registry verifies that name against the aflink.us domain itself (see below), and the endpoint is on the same domain, so the listing, the site and the server are visibly one publisher.

  • Endpoint: https://api.aflink.us/mcp (api.aflink.us is a Cloudflare custom domain on this worker, declared in wrangler.jsonc, that also serves the suggestions and submissions), Streamable HTTP transport (MCP spec 2025-11-25; 2025-06-18 and 2025-03-26 clients are also accepted).
  • One tool, `search_links`: takes a query (and an optional limit, 1–50, default 10) and returns matching links with title, URL, category and summary, title matches first. Links in the UNOFFICIAL category come back with official: false, and links marked as opening only from a government network with milOnly: true.
  • Read-only: the tool searches the link list bundled into the worker, the same list aflink.us publishes as links.json, and nothing else. It cannot add, change or request links; that still goes through the issue forms and their review.
  • No authentication: it serves only what https://aflink.us/links.json already publishes. No login, no API key, no cookies, and the worker stores nothing about the caller.
  • Same answers as the site: it uses the list and ranking the suggestions use (to_entries() and search() in src/index.js) and the page's own matching rules in search-match.js, so the parity rules above cover it too.

It is stateless: each POST gets one JSON response, no session is kept, and GET /mcp is 405 because the server never sends anything unprompted. Any web origin may call it (CORS *), since there is nothing private to protect; an Origin that is not an http(s) origin is refused, as the transport spec asks. The code is src/mcp.js with no SDK dependency, and test/mcp-server.test.js covers the protocol, the tool and server.json.

Discovery. Besides the Registry listing, the server can be found from the domain itself, as the MCP Server Cards extension (SEP-2127) describes. src/.well-known/ai-catalog.json is served at https://aflink.us/.well-known/ai-catalog.json and lists one entry, which points to the server card at GET https://api.aflink.us/mcp/server-card, the place the spec reserves for a server at /mcp. The card (SERVER_CARD in mcp.js) gives the name, version, description and endpoint, with CORS, an ETag and an hour's caching; it does not list tools, which clients still get from tools/list. It is built in mcp.js rather than read from server.json, so the worker needs no new watch path, and a test checks the two agree. Both formats are new, so update them if the extension changes.

To try it:

claude mcp add --transport http aflink https://api.aflink.us/mcp

or, with the MCP Inspector

npx @modelcontextprotocol/inspector # transport "Streamable HTTP", the URL above

Publishing to the MCP Registry

server.json in the repository root is the Registry entry. .github/workflows/mcp_publish.yml publishes it, run by hand from the Actions tab:

  1. Merge the change to master. Cloudflare Workers Builds deploys the worker on every push to master that touches search_worker/, and GitHub Pages rebuilds the site; wait for both.
  2. Run Publish MCP server. It runs the MCP tests, checks that https://api.aflink.us/mcp answers initialize as us.aflink/search at the version in server.json and that aflink.us serves the public key, then logs in and publishes.

How the Registry knows aflink.us is ours. The us.aflink/* namespace is proven over HTTP: src/.well-known/mcp-registry-auth holds an Ed25519 public key (v=MCPv1; k=ed25519; p=…), served at https://aflink.us/.well-known/mcp-registry-auth, and the workflow signs its login with the matching private key. Jekyll and the Pages upload skip dot-folders, so src/_config.yml includes it and build.yml uploads hidden files; a test checks both. The private key is the MCP_REGISTRY_KEY secret of the mcp-registry-publish environment, limited to master, because it can publish anything under us.aflink/*. To rotate it, generate a new pair, replace the file and the secret, and let Pages rebuild before publishing.

The custom domain. api.aflink.us was attached once in the dashboard: adding a domain needs zone permission the Workers Builds token does not have, while a deploy that leaves an existing domain as it is needs none. wrangler.jsonc lists it so deploys keep it, and sets workers_dev: true, because a config with routes otherwise turns the workers.dev URL off. The site and getlinks.js now use api.aflink.us; the workers.dev URL stays on only for a month while traffic moves over, and is to be turned off (workers_dev: false) after 2026-12-07.

For a new listing, bump version in server.json and SERVER_VERSION in src/mcp.js together (a test checks they agree, and that the server card matches server.json), merge, let the worker build finish, and run the workflow again. The Registry refuses a version it already has.

Development

npm install          # in this directory

npm run dev # serves the worker on :8787 npm run deploy # wrangler deploy (by hand; normally Workers Builds deploys on push to master)

A development build of the site (npm run dev:build in the repo root) points its suggestions at localhost:8787, so the two can be exercised together. npm run dev bundles the links from your working copy of src/links/, so a local edit shows up when the worker restarts. npm test in the repo root bundles them too (its pretest step).

Portal link submissions (POST /submit)

The same worker receives link lists from getlinks.js, run in the browser console on any AF Portal page: the script fetches every list the portal has and sends them together as { pages: [{ source, afpCategorizedLinksDto }] }. The worker starts the Portal Sync workflow (.github/workflows/portal_sync.yml), which merges the lists on the portal-sync branch and opens or updates one pull request. Nothing reaches the site until that PR is merged.

The endpoint is public, so src/submit.js is strict:

  • Browser origin must be the AF Portal.
  • Every page's source must be one of KNOWN_SOURCES, each at most once; a new portal list is added there and to PAGES in getlinks.js.
  • Only title, link, contentId and a few known fields are kept, each checked for shape and length; the whole payload is capped at 512 KB.
  • Per-address and daily rate limits, counted in the LINKS KV namespace; an identical payload within a day is acknowledged but not re-sent.
  • The packed payload is kept in KV for a day and served at GET /submission/ ; the workflow receives only the id, because workflow_dispatch inputs are capped at 64 KB and the lists with their descriptions are larger.
  • On the workflow side, scripts/af-guard.js fails the run (and opens an issue) if a submission would move an existing link to a non-official domain.

It needs

只显示了开头部分;其余内容请在仓库中阅读