viraill-mcp
<!-- mcp-name: io.github.crypto-yannso/viraill-mcp -->
# Viraill MCP Server
Model Context Protocol (MCP) server for **Viraill** — Generative Engine Optimization (GEO) & Agentic Commerce Readiness.
This server enables Claude Desktop, Cursor, Windsurf, Hermes, and any MCP client to diagnose AI search engine visibility, generate intent-aligned social content, and audit Agentic Commerce Readiness.
---
## Tools Exposed
1. **`geo_audit`**
- Audits visibility across ChatGPT, Perplexity, Gemini, and Claude.
- Computes intent gaps against market query centroids.
- Generates RAG Answer Blocks (BLUF) and Schema.org markup.
2. **`geo_social_generate`**
- Generates LinkedIn, X/Threads, Debate, and Carousel content.
- Calibrates posts against market intention centroids.
3. **`agentic_scan`**
- Scores site Agentic Readiness (/100) across 5 pillars.
- Generates complete remediation files (`llms.txt`, `agent.json`, `openapi.json`).
---
## Installation & Configuration
### 1. Claude Desktop (`claude_desktop_config.json`)
```json
{
"mcpServers": {
"viraill": {
"command": "npx",
"args": ["-y", "@crypto-yannso/viraill-mcp"]
}
}
}
```
### 2. Cursor IDE (`.cursor/mcp.json`)
```json
{
"mcpServers": {
"viraill": {
"command": "npx",
"args": ["-y", "@crypto-yannso/viraill-mcp"]
}
}
}
```
### 3. Smithery (Claude & Cursor 1-Click)
```bash
npx -y @smithery/cli install @crypto-yannso/viraill-mcp --client claude
```
---
## Environment Variables (Optional)
- `VIRAILL_API_KEY` : Optional API key for enterprise quotas. Free tier (1 call/day/IP) works out of the box without any key.
- `X_PAYMENT` : Optional x402 payment header (Base USDC micropayments).
## License
MIT © [ARTAIFACT](https://artaifact.online) & [Viraill](https://viraill.com)
TDQS
Scored across 3 tools
The three tools are clearly distinct: geo_audit analyzes generative search visibility, geo_social_generate creates social content, and agentic_scan measures agentic commerce readiness. There is no functional overlap, and each tool targets a unique domain with clear descriptions.
The naming pattern is inconsistent. Two tools share the 'geo_' prefix but use different verb structures (audit vs. generate), while the third uses 'agentic_' with a different verb. The mixing of prefixes and verb placements disrupts a predictable convention.
Three tools is a reasonable, focused count for a server dedicated to GEO and agentic commerce. It avoids bloat and covers core auditing and generation tasks, though it borders on the lower end of the ideal range.
The server covers the primary workflows: auditing generative search visibility, creating social content to build citations, and assessing agentic commerce readiness. Minor gaps exist (e.g., no monitoring or content update tools), but the core lifecycle is well represented for its scope.