Skip to main content
Glama
minghsuy

ctscout

by minghsuy

Search ctscout by company name

ctscout_search_company
Read-onlyIdempotent

Find all apex domains owned by a company using Certificate Transparency log data. Enter an organization name to get attributed domains with certificate and subdomain counts.

Instructions

Search ctscout.dev's domain-attribution warehouse by organization name. Returns apex domains attributed to that organization based on Certificate Transparency log analysis (OV/EV cert subjects matched to entity names).

Args:

  • company_name (string, required): organization name. Partial matches work — 'Goldman' matches 'Goldman Sachs'. Min 2 chars, max 200.

  • response_format ('markdown' | 'json', default 'markdown'): output format.

Returns:

  • In markdown: a table of (domain, org, cert count, subdomain count).

  • In JSON, structured as: { "domains": [ { "org": string, // legal entity name as recorded in cert "apex_domain": string, // e.g. "gs.com" "cert_count": number, // # of certs observed for this domain "subdomain_count": number, // # of distinct subdomains "first_seen": string, // ISO 8601 timestamp "last_seen": string // ISO 8601 timestamp } ], "total": number, // total matching rows in warehouse "truncated": boolean, // true if response is capped "upgrade_hint": string, // present when truncated "source": "warehouse" | "live" // free tier = warehouse, pro = live }

Examples:

  • Use when: "Find all domains owned by Cloudflare" -> { company_name: "Cloudflare" }

  • Use when: "What domains does Goldman own?" -> { company_name: "Goldman Sachs" }

  • Don't use when: You have a specific domain and want to find its owner — use ctscout_lookup_domain instead.

Auth & limits:

  • Requires CTSCOUT_API_KEY env var. Get a free key (no email) at https://ctscout.dev.

  • Free tier: 10 queries/day, top 5 results from weekly snapshot.

  • Pro tier: unlimited queries, full result set, live enrichment.

Error handling:

  • HTTP 401: API key missing or invalid.

  • HTTP 429: daily quota exceeded — wait or upgrade.

  • "No domains found": try a shorter or different company name (see legal-vs-brand caveat below).

Legal-vs-brand caveat (important):

  • The cert subject (O field) uses LEGAL entity names, not brand names.

  • "Travelers Insurance" → 0 results because the legal name is "The Travelers Companies, Inc."

  • "Hartford Financial" → 0 results; legal names are "Hartford Fire Insurance Company" or "The Hartford Financial Services Group".

  • If a brand-name search returns nothing, retry with variants like "X Companies", "X Group", "X Inc", "X Corporation", or "The X". The empty-result markdown output includes these suggestions automatically when the input looks brand-shaped.

Coverage caveat:

  • Best for established US/EU tech companies with OV/EV certs (~5,976 entities indexed).

  • Limited coverage on small private companies, cyber MGAs, and entities using only DV (Let's Encrypt) certs.

  • See https://ctscout.dev for current coverage map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_nameYesCompany / organization name to search for. Partial matches work (e.g. 'Goldman' matches 'Goldman Sachs'). Case-insensitive.
response_formatNoOutput format: 'markdown' for human-readable summary, 'json' for the raw API response (useful for programmatic processing).markdown
Behavior5/5

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

Adds substantial context beyond annotations: auth requirements (CTSCOUT_API_KEY), error handling (401, 429), rate limits (free vs pro tiers), truncation behavior, and the legal-vs-brand caveat which is critical for correct usage.

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?

Well-structured with headers (Args, Returns, Examples, etc.) and front-loaded with core purpose. Slightly long due to necessary caveats, but every section earns its place.

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?

Comprehensive for a 2-param tool with no output schema. Covers purpose, parameters, return formats, usage guidance, auth, errors, and important caveats. Leaves no gaps.

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 coverage is 100% so baseline is 3. Description adds value by explaining partial matching behavior and giving format use cases (markdown for humans, JSON for programmatic). Minor improvement over schema.

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 clearly states the tool searches ctscout.dev's domain-attribution warehouse by organization name and returns apex domains. It distinguishes from sibling tool ctscout_lookup_domain by explicitly stating when not to use this tool.

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

Usage Guidelines5/5

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

Provides explicit when-to-use examples like 'Find all domains owned by Cloudflare' and when-not-to-use guidance directing to ctscout_lookup_domain. Also includes caveats about legal-vs-brand names and coverage limitations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minghsuy/ctscout-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server