AI & Machine Learning
ninar.ai
Analyzes and improves a brand's AI visibility by scanning, auditing, and generating content for AI engines.
ENDPOINT 1
https://ninar.ai/mcp
MCP server metadata
- Name
- ninar-ai
- Version
- 1.0.0
Known tools 5
get_latest_scoreGet the AI Visibility Index (0-100) for the signed-in user's most recently scanned brand, broken down by engine.
Inferred read-onlylist_content_gapsList AI-generated content suggestions (FAQs, differentiators, use cases, about copy) the signed-in user can publish to close visibility gaps found in their latest scan.
Potential side effectsgenerate_contentGenerate AI-optimized content (FAQ, about copy, use cases, differentiators) for the gaps in your latest scan.
Inferred read-onlyaudit_brand_visibilityCheck whether a brand or entity surfaced by an AI engine is a genuine competitor in your category (e.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ninar-ai]
url = "https://ninar.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ninar-ai": {
"type": "http",
"url": "https://ninar.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ninar-ai
Remote MCP URL: https://ninar.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ninar-ai": {
"url": "https://ninar.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ninar-ai": {
"type": "http",
"url": "https://ninar.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ninar-ai",
"transport": "streamable-http",
"url": "https://ninar.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.