collimer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COLLIMER_API_BASE | No | API base URL | https://app.collimer.com |
| COLLIMER_MAX_POLLS | No | Max poll attempts | 60 |
| COLLIMER_SCAN_SOURCE | No | Funnel-attribution channel (set per distribution) | mcp |
| COLLIMER_POLL_INTERVAL_MS | No | Poll interval | 5000 |
| COLLIMER_REQUEST_TIMEOUT_MS | No | Per-request timeout | 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 |
|---|---|
| collimer_scanA | Run a free Collimer scan on a website to measure how visible its brand is in AI search — ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews. Returns an AI-visibility score (0–100), a confidence interval, the single biggest gap, and a branded report URL. The full ranked fix plan + verification re-scan unlock with a free account on the web. Tip: after the site makes changes, re-run the scan to measure the delta. |
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 1 tool
There is only one tool, so there is no possibility of the agent confusing it with another. Its purpose (run a brand AI-visibility scan and return a score) is unambiguous.
The single name collimer_scan uses a clean snake_case vendor_noun/verb pattern with no competing conventions. Nothing in the set conflicts with it.
A one-tool surface is on the thin side even for a focused scan service, since follow-on actions like re-scanning, comparing deltas, or fetching the full report are alluded to in the description but not exposed. It is defensible as a minimal wrapper, but borderline.
The tool covers the core scan action, but the description explicitly defers the ranked fix plan and the verification re-scan to a web account, and there is no way to list past scans or retrieve the report programmatically. That leaves notable gaps around the re-scan/delta workflow the description itself recommends.