Skip to main content
Glama
sandcastlelabs

collimer-mcp

by sandcastlelabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

collimer-mcp

npm · MIT · Model Context Protocol

Let any AI agent run a free AI-search visibility scan on any website — how visible a brand is in ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews.

Trackers tell you you're invisible. Collimer tells you why, and what to fix.

It exposes one tool, collimer_scan, which returns a depth-gated teaser: an AI-visibility score (0–100), a confidence interval, the single biggest gap, and a branded report URL. The full ranked fix plan and verification re-scan unlock with a free account at collimer.com.

Install

Add Collimer to any MCP client. It runs on-demand via npx — no install step.

Claude Desktop / Claude Code — add to your MCP config (claude_desktop_config.json, or .mcp.json in your project):

{
  "mcpServers": {
    "collimer": {
      "command": "npx",
      "args": ["-y", "collimer-mcp"]
    }
  }
}

Cursor / Windsurf / VS Code — same block, in the editor's MCP settings (~/.cursor/mcp.json, Windsurf MCP settings, or .vscode/mcp.json).

Then ask your assistant:

"How visible is stripe.com in AI search?" "Run a Collimer scan on example.com and tell me the biggest AI-visibility gap." "Does ChatGPT cite acme.com when asked about its category?"

Your assistant will call collimer_scan and return the teaser.

Related MCP server: AI Readiness

The tool

collimer_scan(domain, email?)

Arg

domain

required

The website to scan — example.com or https://example.com.

email

optional

Emails the report and speeds claiming the account later.

Returns the teaser — score, confidence interval, top gap, report URL, and an unlock link. The full ranked fix plan and verification re-scan are never returned; they unlock with a free account.

Configuration (env)

Var

Default

Purpose

COLLIMER_API_BASE

https://app.collimer.com

API base URL

COLLIMER_SCAN_SOURCE

mcp

Funnel-attribution channel (set per distribution)

COLLIMER_MAX_POLLS

60

Max poll attempts

COLLIMER_POLL_INTERVAL_MS

5000

Poll interval

COLLIMER_REQUEST_TIMEOUT_MS

30000

Per-request timeout

What is Collimer?

Collimer measures and improves how often AI answer engines cite your brand — generative engine optimization (GEO), the AI-search successor to SEO. This MCP server is the free front door: scan any site from inside your assistant, see the score and the biggest gap, then open the full report and get your ranked fix plan at collimer.com. API docs: app.collimer.com/docs.

Privacy

The server calls Collimer's public scan API for the domain you pass and returns the result. It doesn't read your files or your conversation. Scans carry a source tag (default mcp) so we can see which channels are useful — no personal data beyond the optional email you provide.

Develop

npm install
npm run build          # → dist/
npm run smoke          # real scan against prod, prints the teaser
npm run test:protocol  # spawns the server + calls the tool over MCP/stdio

License

MIT © Sandcastle Labs

Available Tools

2 tools
beacon_free_scanCollimer AI-visibility scanA
Read-only

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 report (share of voice across each engine + every recommendation) unlocks with a free account on the web. Tip: after the site makes changes, re-run the scan to measure the delta. (Deprecated alias for collimer_scan.)

ParametersJSON Schema
NameRequiredDescriptionDefault
emailNoOptional — emails the report and speeds claiming the account later.
domainYesThe website to scan, e.g. 'example.com' or 'https://example.com'.

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint and openWorldHint. Description adds that the scan is free, returns specific data, and that full report requires a free account. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, all informative. Front-loaded with main purpose. No fluff or redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description details what is returned (score, confidence interval, gap, report URL) and explains the limitation of the free scan. Adequate for a 2-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%. Description adds value by explaining 'email' is optional and speeds account claiming, and gives example formats for 'domain' (e.g., 'example.com' or 'https://example.com').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states it runs a free Collimer scan to measure AI-visibility, specifies the engines (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews), and lists returned items (score, confidence interval, gap, report URL). Clearly distinguishes from sibling 'collimer_scan' as a deprecated alias.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context on when to use (measuring brand visibility) and a tip to re-run after changes. Mentions deprecated alias to differentiate from sibling. Does not explicitly state when not to use or provide alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

collimer_scanCollimer AI-visibility scanA
Read-only

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 report (share of voice across each engine + every recommendation) unlocks with a free account on the web. Tip: after the site makes changes, re-run the scan to measure the delta.

ParametersJSON Schema
NameRequiredDescriptionDefault
emailNoOptional — emails the report and speeds claiming the account later.
domainYesThe website to scan, e.g. 'example.com' or 'https://example.com'.

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=true and openWorldHint=true; description adds context about free scan, return values, account unlocking, and re-running for deltas. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is three sentences plus tip, front-loaded with purpose. Efficient but first sentence is slightly long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 2 parameters and no output schema, description explains return values (score, confidence interval, gap, report URL) and mentions tip about re-running. Fully covers what agent needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (domain, email) have descriptions in schema. Description adds no extra meaning beyond what's already in schema. Schema coverage is 100%, baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it runs a scan on a website to measure AI visibility, listing specific AI models and return values. It distinguishes from sibling (beacon_free_scan) by name but does not explicitly differentiate functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes when to use (to measure AI visibility) and includes a tip to re-run after changes. However, no explicit guidance on when not to use or comparison with sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.2.1
    • First observedbeacon_free_scan
    • First observedcollimer_scan
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation1/5

Both tools have identical descriptions and perform the same function; one is explicitly a deprecated alias. An agent cannot distinguish between them, leading to high ambiguity.

Naming Consistency2/5

The names 'beacon_free_scan' and 'collimer_scan' follow different patterns: one uses 'beacon_free_' with an underscore, the other uses the server name directly. The inconsistency is moderate.

Tool Count2/5

With only 2 tools and one deprecated, the server feels too sparse for a meaningful interface. It barely covers its intended purpose.

Completeness2/5

The server offers only a single scan operation with no additional tools for account management, history, or detailed results, leaving significant gaps for typical usage.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • geo-audit

    nycsav
    A
    license
    Not graded
    quality
    C
    maintenance
    Evaluates any website's AI visibility with 15 checks across crawlability, structure, content, and connectivity, and provides actionable fixes.
    3 npm
    MIT

  • AI Readiness

    epistemedeus
    A
    license
    A
    quality
    B
    maintenance
    Check whether a website is visible to AI search engines (ChatGPT, Perplexity, Claude, Google AI Overviews). Returns a 0-100 readiness score, a grade, and a specific fix for each gap. Dependency-free, no API keys.
    2
    3 npm
    MIT

  • sylgeo-mcp

    hitankshah
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to scan brand visibility across ChatGPT, Claude, Gemini & Perplexity, analyze website GEO readiness, compare competitors, and get actionable recommendations.
    MIT

  • Specularis AI Visibility Audit

    AdevAarons
    A
    license
    Not graded
    quality
    B
    maintenance
    Runs AI visibility (GEO/AEO) audits on websites, checking AI crawler access, schema markup, llms.txt, and content signals, with optional full PDF report.
    MIT