viraill-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X_PAYMENT | No | Optional x402 payment header (Base USDC micropayments). | |
| VIRAILL_API_KEY | No | Optional API key for enterprise quotas. Free tier (3 calls/day/IP) works out of the box without any key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geo_auditA | Audit website visibility in generative search engines (ChatGPT, Perplexity, Gemini, Claude). Analyzes intent gaps, market white spaces, and generates RAG-first answer blocks (BLUF) + Schema.org markup. |
| geo_social_generateC | Generate viral social publications (LinkedIn, X/Threads, Debate, Carousel) mathematically aligned with market intent centroids to build external RAG citation consensus. |
| agentic_scanA | Audit a website's Agentic Commerce Readiness (/100 score across 5 pillars: Crawl/Ingestion, OpenAPI, Schema.org, x402 settlement, 8 distribution channels) and generate remediation code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.