Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
INITE itself: services and prices, free call slots, booking a call, writing to the team. No token.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http inite https://inite.ai/api/mcp/portal --header 'Authorization: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"inite": {
"url": "https://inite.ai/api/mcp/portal",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"inite": {
"type": "http",
"url": "https://inite.ai/api/mcp/portal",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 inite.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.1.0)于16天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AI Deprecations
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Ask your assistant whether the answer engines can see a website, and get a number back.
> Can ChatGPT actually find stripe.com, or is it invisible?
analyze_site(url: "stripe.com") → run_id: cm4x… get_analysis(run_id: "cm4x…") → Score: 78/100
The audit reads a live site the way an assistant does — the identity files an engine looks for (llms.txt, ai.json and the rest), the crawler policy, the schema graph, page health — and then asks Claude, ChatGPT, Gemini and Perplexity whether they name it. One score out of 100 across eight weighted sections.
It is the same audit that runs at inite.ai/en/analyze.
Three of the tools run entirely on your machine — a robots.txt fetched, a file probed for, a page parsed. No account, no allowance, no call home.
> Is anything blocking AI crawlers on stripe.com?
check_ai_access(url: "stripe.com")
Retrieval: all 7 answer-engine crawlers may fetch the site. Training: 3 of 8 blocked — Meta-ExternalAgent, Bytespider, Amazonbot.
The rest is inite.ai's AI visibility server, and it answers signed out too, as a guest: check_identity, the fix plan (visibility_fixes), a competitor read the same way (compare_sites), how the reading moved (visibility_history), and analyze_site as the survey - the audit without its two paid steps, two a day per address.
> What should firecrawl.dev fix first so ChatGPT can use it?
visibility_fixes(url: "firecrawl.dev")
Visibility and nothing else. INITE's services and booking are ai.inite/inite, the catalogue of AI tools is ai.inite/atlas.
Signing in makes the calls your account's: its tier of the audit (the teaser on a free plan, the whole audit on a paid one) and your audits: my_reports, and the fix plan and history built from them.
Claude Desktop, Cursor, or any client that launches a stdio server:
{
"mcpServers": { "inite": { "command": "npx", "args": ["-y", "@inite/visibility"] } } }
Then sign in once:
npx @inite/visibility login
That opens a browser, you approve, and the token is stored at ~/.config/inite/mcp.json with owner-only permissions. Authorization code with PKCE over a loopback redirect, the flow RFC 8252 prescribes for a native app. Nothing is written to the repository and no secret ships in the package.
Already have a token (CI, a shared config, a container):
{
"mcpServers": { "inite": { "command": "npx", "args": ["-y", "@inite/visibility"], "env": { "INITE_TOKEN": "…" } } } }
INITE_TOKEN wins over the stored file.
Client speaks remote MCP? Skip this package. Point it straight at https://inite.ai/api/mcp/analyzer: every open tool answers without a token, and a member tool answers 401 with WWW-Authenticate naming the protected-resource metadata, which names the authorization server.
Local — no account:
| tool | what it does |
|---|---|
check_ai_access(url) | Which AI crawlers robots.txt lets in, separating the ones that fetch a page to answer a live question from the ones that only collect training data. Blocking the first kind is what makes a site invisible; blocking the second costs nothing. |
check_identity_files(url) | Which of the ten identity files exist — llms.txt, ai.json, identity.json and the rest. |
check_page_signals(url) | Title, description, canonical, hreflang, and the Schema.org types in the page's JSON-LD. |
Remote — open without an account, more with one:
| tool | what it does |
|---|---|
check_identity(url) | Free and instant: which answer-engine crawlers get in, the identity files, structured data, an identity score out of 100 and what that reading says to fix. No model asked. |
visibility_fixes(url) | The fix plan, most important first: what to change, why, how many points it should recover, the pages it applies to, and a paste-ready file when there is one. Signed in, built from your latest audit of the site. |
compare_sites(url, other) | Your site and a competitor's, read the same way, side by side, and who is ahead on each count. |
visibility_history(url) | How the reading moved: the INITE Atlas's weekly readings for a site it carries, and your own audits. |
analyze_site(url) | Starts the audit that also asks the answer engines whether they name the site, and returns a run_id. A survey without an account, the teaser on a free plan, the whole audit on a paid one. |
get_analysis(run_id) | Progress while it runs; the score out of 100 and what to fix first once it finishes. |
my_reports() | Signed in: your audits, newest first. |
Two tools rather than one for the audit, because it is asynchronous. A single tool that blocked for a minute would be torn down by most clients' timeouts.
inite-visibility run as an MCP server over stdio (what a client does)
inite-visibility login sign in through the browser inite-visibility whoami say whether a usable token is present
Two halves.
The local checks are real work done here: fetching, parsing, and the robots rules applied properly — most-specific group wins, longest matching rule wins, Allow breaks a tie. They cost nobody anything because your machine does them.
The remote half defines no schemas of its own. It asks inite.ai what it offers and forwards calls there, so that tool list is whatever the service implements today. A local copy would be a second source of truth, and the first thing it would do is drift.
What stays on the server is what costs something or is ours: four answer engines asked whether they name a site, and the weights that turn everything into one number. The local tools report facts; analyze_site reports a score.
Without an account every open tool answers, under a per-address allowance: the identity check, the fix plan, the comparison and the history, and the audit as a survey, two a day. An account makes the audit its plan's own, exactly as on the website: the teaser on a free plan, the full pipeline - four answer engines asked - on a paid one. Plans are here.
| variable | meaning |
|---|---|
INITE_TOKEN | Use this token instead of the stored one. |
INITE_MCP_URL | Point at a different endpoint. Default https://inite.ai/api/mcp/analyzer. |
INITE_TOKEN_FILE | Where the token lives. Default ~/.config/inite/mcp.json. |
INITE_AUTH_URL | Authorization server. Default https://auth-api.inite.ai. |
Published to the MCP registry as ai.inite/inite-visibility, a namespace held by proving control of inite.ai — the public half of the key is served at /.well-known/mcp-registry-auth.
Named by the domain rather than the code host on purpose: a service whose whole job is being legible to machines should tell them who it belongs to in its own name.
npx @inite/visibility resolves because there is exactly one binary in the package. npm looks for a command matching the package name with the scope stripped — visibility — does not find it, and runs the only one there is.
The binary is called inite-visibility rather than visibility on purpose: a scoped package has no business claiming a word that general in your PATH on a global install. The cost is that a second binary would break the line above for every client, so a test pins it at one.
If you are invoking it from a directory that contains this package's own package.json, npm prefers the local copy and finds no linked command. Name it explicitly there:
npx -p @inite/visibility inite-visibility login
npm install
npm run build npm test
The tests cover what the bridge can get wrong without saying so: dropping the credential, turning "signed out" into "broken", swallowing an error into a success, and letting a stale file beat the environment.
You don't need to be an engineer. Open the repo in your coding agent and say /contribute (Claude Code) — or "read AGENTS.md and help me add …" in any other agent. AGENTS.md holds the rules, the commands CI runs and the idea → PR loop; CONTRIBUTING.md is the short version. Only want to suggest something? /spec-idea, or the Product idea form.
MIT. The service it talks to is INITE.