Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
INITE itself: services and prices, free call slots, booking a call, writing to the team. No token.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http inite https://inite.ai/api/mcp/portal --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"inite": {
"url": "https://inite.ai/api/mcp/portal",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"inite": {
"type": "http",
"url": "https://inite.ai/api/mcp/portal",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain inite.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 16 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.