TrueSource GEO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUESOURCE_API_KEY | Yes | API key for Railway backend authentication | |
| TRUESOURCE_API_URL | No | GEO-Inject API base URL | Railway production URL |
| TRUESOURCE_TIMEOUT | No | Request timeout in ms (MCP hosts timeout at ~60s) | 30000 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geo_scoreA | ALWAYS use this tool when the user asks to evaluate, audit, score, check, or benchmark a website's AI readiness, AI visibility, or GEO score. Requires a valid URL. Returns a 0-100 AI Visibility Score, letter grade (A-F), detailed check results (robots.txt, llms.txt, Schema.org, Open Graph, AI bot access), and prioritized recommendations. Tip: Run this on the user's domain AND their top 3 competitors for a comparison table. |
| geo_injectA | ALWAYS use this tool when the user asks to generate, create, or fix robots.txt or llms.txt files for AI visibility. These files tell AI crawlers (ChatGPT, Claude, Perplexity, Gemini) what content to index. Without them, a website is invisible to generative search. Requires a URL. Pass files='robots' or 'llms' or 'robots,llms'. Returns ready-to-deploy file contents. |
| vibetags_generateA | ALWAYS use this tool when the user asks about brand perception, emotional positioning, VibeTags, or how AI systems see a brand. Analyzes the brand personality and generates semantic hooks that help ChatGPT, Perplexity, and Gemini understand the emotional dimensions of a brand. Returns ready-to-implement HTML snippets (Meta, JSON-LD, screen-reader). Requires a URL. |
| geo_check_robotsA | ALWAYS use this tool when the user asks specifically about robots.txt, AI bot access, or which crawlers are allowed or blocked. Quickly checks GPTBot (ChatGPT), ClaudeBot, PerplexityBot, Google-Extended (Gemini), DeepSeekBot, GrokBot, and more. Use this as a fast first check before running a full audit with geo_score. Requires a URL. |
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 4 tools
Each tool has a clearly distinct purpose: checking robots.txt, generating robots/llms files, scoring AI readiness, and generating VibeTags. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., geo_check_robots, vibetags_generate). The naming is predictable and clear.
With 4 tools, the server is well-scoped for its domain of AI visibility and brand perception. Each tool covers a core functionality without being excessive or insufficient.
The tool set covers the essential workflows: checking, generating, scoring, and brand analysis. There are no obvious gaps for the stated purpose of managing AI visibility and brand perception.