Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Find the organization behind a MAC address or OUI prefix in the IEEE registries. No auth, no key.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mac.jasontally.com/mcp在终端中运行这条命令
claude mcp add --transport http mac https://mac.jasontally.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mac": {
"url": "https://mac.jasontally.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mac": {
"type": "http",
"url": "https://mac.jasontally.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mac.jasontally.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 mac.jasontally.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于35天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Free, fast, client-side MAC address vendor lookup. Paste a full or partial MAC address (OUI prefix, MA-M, MA-S, IAB, or CID block) and instantly identify the organization behind it — everything runs in your browser with no backend. We ask nothing of you: no ads, no cookies, no account, no tracking. The project came out of frustration with lookup pages wrapped in intrusive advertising: identifying a MAC vendor is a small utility, and it should be possible to build and host it for close to nothing.
[mac.jasontally.com](https://mac.jasontally.com)
The app does no tracking: there are no ads, no cookies, and every lookup runs in your browser, where the addresses you look up are never processed by a server. Normal requests still reach the host as with any website — a direct link such as /apple carries the term in its URL path, and the app fetches its public data files by URL — but the host only serves static files and runs no search code. The site is hosted on Cloudflare, which collects privacy-first, aggregate web analytics (Cloudflare Web Analytics) that use no cookies or client-side state and do not fingerprint individuals.
00:1A:2B, 001A2B3, 001A2B3C4)arp -a, switch tables, logs) into the search box; every full MAC address inside is extracted and looked up, with non-address text ignoredmac.jasontally.com/001A2B renders the result directly. Batch lookups and vendor searches work the same way.Navigate directly to a result — no form submission needed. Everything after / is the query (address, prefix, vendor/country/former-owner text):
| URL | Result |
|---|---|
https://mac.jasontally.com/001A2B | OUI / prefix lookup |
https://mac.jasontally.com/001B213C4D5E | Full address lookup |
https://mac.jasontally.com/001A2B,005056 | Batch lookup (comma-separated, cap 250) |
https://mac.jasontally.com/apple | Vendor search |
https://mac.jasontally.com/tekelec | Former-owner search |
https://mac.jasontally.com/vendor | Vendor index: every organization with two or more registered blocks |
https://mac.jasontally.com/vendor/apple-inc | Vendor page: every block registered to one organization |
https://mac.jasontally.com/country/us | Country page: every organization with registered blocks |
https://mac.jasontally.com/country | Dimension index rollups: /country, /year, /region, /history, /successor (each is its own table over the corresponding page family) |
https://mac.jasontally.com/former/apple-computer | Former-owner page: what happened to each renamed/reassigned block |
https://mac.jasontally.com/?q=001A2B | Legacy form (canonicalizes to /001A2B) |
The page consumes the value from the URL path and displays the result without any manual input.
A build step pre-renders a real HTML page for every registered IEEE assignment — each OUI (MA-L), MA-M, MA-S, IAB, and CID prefix — so that people can find the tool when they look up a prefix or a vendor in their own words. Every page contains the vendor record without requiring JavaScript, and the interactive tool hydrates on top to resolve everything else in the browser: full addresses, partial prefixes, batch lists, vendor names, former owners, countries, and registration years. No brand is promoted as part of the app; the title is translated into local words for each language, because an English-only brand name would make it harder to find for everyone else. Generated pages include canonical URLs, schema.org metadata, sitemap.xml, and robots.txt. Sitemap: https://mac.jasontally.com/sitemap.xml.
On top of the prefix pages, the build generates vendor pages (/vendor/ , every block registered to one organization — roughly 3,500 today), country pages (/country/ , every organization with blocks registered in a country — roughly 130), former-owner pages (/former/ , roughly 350), and registry/year/region/history/successor dimension pages (/registry, /year, /region, /history, /successor), each family behind its own rollup index — `/vendor` (every organization with two or more blocks) and `/country` (every country) are both in the sitemap. The hub pages are complete static tables with no row caps, plus an internal relational link web: related-prefix sections (same vendor, adjacent prefixes, same registration year) on every prefix page, hub links from prefix pages, org directory links on country pages, and the home page's "MAC address by" nav reaching every rollup index. Rationale and capacity accounting: docs/thin-content-mitigation.md.
llms.txt describes the site and data files for AI tools./.well-known/ai-catalog.json and /.well-known/ard.json are ARD 1.0 catalogs whose single entry describes the MCP server below. Real JSON at those paths also prevents the SPA fallback from serving HTML there.data/registry.ndjson (~13.6 MB, one JSON object per IEEE assignment) and data/lineage.ndjson (ownership-change events). If your client cannot speak MCP, match the longest registered prefix against these yourself./mcp is a stateless MCP server over Streamable HTTP. No key, no auth, no session, and no handshake required: a current client posts a request directly. It also answers an initialize probe statelessly, so a 2025-era client can connect too, and refuses an unsupported protocol version with -32022 listing what it does speak. A GET that sends Accept: text/event-stream gets an SSE stream for clients that still probe the old transport; any other GET gets 405. One tool, lookup, takes a MAC address or OUI prefix and returns the registered organization, block type, address count, country, and a link to the record page in one call. Served by a Cloudflare Snippet (mcp/snippet.js, generated by build/mcp-shards.mjs); see docs/mcp-endpoint.md./.well-known/oauth-protected-resource and /.well-known/oauth-protected-resource/mcp return RFC 9728 metadata naming no authorization server, because the endpoint is public and no token is ever presented.server.json at the repository root is the document the official MCP Registry publishes, and /.well-known/mcp/server-card.json is the same document at the path clients probe for pre-connection discovery (SEP-1649). test/mcp-listing.test.mjs keeps the two copies identical. Where the server can be listed, what each place checks, and the steps that need the account holder: docs/mcp-listing.md.npm run mcp:load drives the live endpoint with a real request mix and validates every response against a brute-force oracle built from registry.ndjson, so a fast wrong answer counts as a failure. See docs/mcp-endpoint.md → *Load and correctness testing*.mac.jasontally.com)docs/architecture.mddocs/design.mdMIT