Skip to main content
Glama
Stewyboy1990

CompanyScope

get_corporate_registry

Retrieve incorporation date, status, jurisdiction, address, and officers for a company from OpenCorporates using its legal name. Covers 140+ jurisdictions worldwide.

Instructions

Look up corporate registry data from OpenCorporates — incorporation date, status, jurisdiction, registered address, and company officers. Covers companies in 140+ jurisdictions worldwide. Use the company's legal name for best results. Note: this may return no results for very new or small private companies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_nameYesCompany legal name as registered (e.g. 'Stripe, Inc.', 'Alphabet Inc.'). Legal names with suffixes like Inc/Ltd/GmbH produce more accurate results.

Implementation Reference

  • The actual handler for the get_corporate_registry tool. Calls searchOpenCorporates() and returns the result as text content.
    async ({ company_name }) => {
      const result = await searchOpenCorporates(
        company_name,
        env.OPENCORPORATES_TOKEN
      );
      return {
        content: [
          {
            type: "text" as const,
            text: result
              ? JSON.stringify(result, null, 2)
              : `No corporate registry data found for "${company_name}".`,
          },
        ],
      };
    }
  • Input schema for get_corporate_registry: a single required company_name string parameter.
    { company_name: z.string().describe("Company legal name as registered (e.g. 'Stripe, Inc.', 'Alphabet Inc.'). Legal names with suffixes like Inc/Ltd/GmbH produce more accurate results.") },
  • src/index.ts:238-258 (registration)
    Tool registration via server.tool() in the registerTools function of src/index.ts (the Cloudflare Worker version).
    server.tool(
      "get_corporate_registry",
      "Look up corporate registry data from OpenCorporates — incorporation date, status, jurisdiction, registered address, and company officers. Covers companies in 140+ jurisdictions worldwide. Use the company's legal name for best results. Note: this may return no results for very new or small private companies.",
      { company_name: z.string().describe("Company legal name as registered (e.g. 'Stripe, Inc.', 'Alphabet Inc.'). Legal names with suffixes like Inc/Ltd/GmbH produce more accurate results.") },
      async ({ company_name }) => {
        const result = await searchOpenCorporates(
          company_name,
          env.OPENCORPORATES_TOKEN
        );
        return {
          content: [
            {
              type: "text" as const,
              text: result
                ? JSON.stringify(result, null, 2)
                : `No corporate registry data found for "${company_name}".`,
            },
          ],
        };
      }
    );
  • bin/cli.js:97-102 (registration)
    Tool registration in the CLI (stdio) version. Proxies to the remote server via callRemoteTool.
    server.tool(
      "get_corporate_registry",
      "Look up corporate registry data from OpenCorporates — incorporation date, status, jurisdiction, registered address, and company officers. Covers companies in 140+ jurisdictions worldwide. Use the company's legal name for best results. Note: this may return no results for very new or small private companies.",
      { company_name: z.string().describe("Company legal name as registered (e.g. 'Stripe, Inc.', 'Alphabet Inc.'). Legal names with suffixes like Inc/Ltd/GmbH produce more accurate results.") },
      async ({ company_name }) => callRemoteTool("get_corporate_registry", { company_name })
    );
  • Core helper function that queries the OpenCorporates API for corporate registry data (search endpoint). Returns company info including officers.
    export async function searchOpenCorporates(
      companyName: string,
      token: string | undefined
    ): Promise<OpenCorpResult | null> {
      try {
        const query = encodeURIComponent(companyName);
        const tokenParam = token ? `&api_token=${token}` : "";
        const resp = await fetch(
          `https://api.opencorporates.com/v0.4/companies/search?q=${query}&per_page=1${tokenParam}`,
          { signal: AbortSignal.timeout(8000) }
        );
    
        if (!resp.ok) return null;
    
        const data = (await resp.json()) as {
          results: {
            companies: {
              company: {
                name: string;
                company_number: string;
                jurisdiction_code: string;
                incorporation_date: string | null;
                company_type: string | null;
                current_status: string | null;
                registered_address_in_full: string | null;
                officers: {
                  officer: {
                    name: string;
                    position: string | null;
                  };
                }[];
              };
            }[];
          };
        };
    
        const companies = data.results?.companies;
        if (!companies || companies.length === 0) return null;
    
        const c = companies[0].company;
        return {
          companyName: c.name,
          companyNumber: c.company_number,
          jurisdiction: c.jurisdiction_code,
          incorporationDate: c.incorporation_date,
          companyType: c.company_type,
          status: c.current_status,
          registeredAddress: c.registered_address_in_full,
          officers: (c.officers || []).slice(0, 10).map((o) => ({
            name: o.officer.name,
            position: o.officer.position,
          })),
        };
      } catch {
        return null;
      }
    }
Behavior3/5

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

No annotations provided, so description bears full burden. Discloses potential no-results, but does not mention rate limits, data freshness, or auth requirements. Adequate but not thorough.

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?

Three concise sentences; purpose is front-loaded. No superfluous words. Efficient and structured.

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?

Despite no output schema, description enumerates returned data fields (incorporation date, etc.) and covers edge case (no results). Sufficient for a simple lookup 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 covers 100% of the single parameter with clear description. Description adds value by suggesting suffixes improve accuracy, going beyond schema details.

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?

Clearly states lookup of corporate registry data from OpenCorporates, specifying data types (incorporation date, status, etc.) and coverage (140+ jurisdictions). Distinguishes from siblings like get_financials or get_key_people.

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 best practice (use legal name) and acknowledges possible no-results for new/small companies, but does not explicitly contrast with sibling tools or state when to prefer this over alternatives.

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/Stewyboy1990/companyscope-mcp'

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