INITE AI Visibility vs Zevian
A side-by-side look at the INITE AI Visibility and Zevian MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Z
ZevianMarketing · Remote HTTP/SSEAudit a site for SEO and AI search, check localhost pages, and apply or open PRs for fixes.39FairAuth: no auth requiredVerdict: choose INITE AI Visibility for marketing work as a local process; choose Zevian for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose INITE AI Visibility when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
INITE_TOKEN, INITE_MCP_URL, INITE_TOKEN_FILE, INITE_AUTH_URL. - You want tools like
check_ai_access, check_identity_files, check_page_signals.
ZChoose Zevian when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Z Zevian | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 59/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | INITE_TOKENINITE_MCP_URLINITE_TOKEN_FILEINITE_AUTH_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View INITE AI Visibility | View Zevian |
Tools & capabilities
INITE AI Visibility tools 3
check_ai_accessRead a site's robots.txt and say which AI crawlers may fetch it, separating the ones that retrieve pages to answer live questions from the ones that only collect training data. Blocking the first kind is what makes a site invisible in AI answers; blocking the second costs nothing. Runs locally, no account needed.check_identity_filesProbe a site for the identity files an AI engine may look for — llms.txt, ai.json, identity.json and the rest — and report which exist. Runs locally, no account needed.check_page_signalsRead a site's homepage and report the signals an engine uses to work out what it is: title, description, canonical, hreflang and the Schema.org types in its JSON-LD. Runs locally, no account needed.
Zevian tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
INITE AI Visibility
{
"mcpServers": {
"inite-ai-visibility": {
"command": "npx",
"args": [
"-y",
"@inite/visibility"
],
"env": {
"INITE_TOKEN": "YOUR_INITE_TOKEN_HERE",
"INITE_MCP_URL": "YOUR_INITE_MCP_URL_HERE",
"INITE_TOKEN_FILE": "YOUR_INITE_TOKEN_FILE_HERE",
"INITE_AUTH_URL": "YOUR_INITE_AUTH_URL_HERE"
}
}
}
}
Zevian
{
"mcpServers": {
"zevian": {
"url": "https://zevian.tech/mcp"
}
}
}
Frequently asked questions
INITE AI Visibility is categorized under Marketing and uses a local stdio subprocess. Zevian belongs to Marketing and uses a remote HTTP/SSE transport. Pick INITE AI Visibility for marketing work and Zevian for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
INITE AI Visibility has no declared pricing — check the project's own site. Zevian has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add inite-ai-visibility and zevian as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, INITE AI Visibility has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Zevian has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.