signals

by com.datahyena

Overview Discussions Admin

Server Details

Deduplicated, entity-resolved funding rounds, acquisitions, and exec moves as MCP tools.

Ownership verified

Status: Healthy
Uptime: 99.9% over 41 days
Last Tested: 2026-09-27 23:44
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A3.9/5.0

Scored 2026-09-14 14:50 across 11 tools

Disambiguation4/5

The core entity and event tools are clearly distinct: companies, investors, funding_events, acquisitions, and exec_moves target different record types. However, company_timeline overlaps functionally with the single-company filters on funding_events, acquisitions, and exec_moves, so an agent could reasonably hesitate between the aggregate timeline and the specialized event tools.

Naming Consistency4/5

All names use snake_case consistently, and the watchlist mutation tools follow a clear verb_noun pattern (add_to_watchlist, create_watchlist, get_watchlist, list_watchlists, remove_from_watchlist). The entity/event search tools are noun-only (companies, investors, acquisitions, etc.), which is logical but a minor deviation from uniform verb_noun naming.

Tool Count5/5

With 11 tools, the server is well-scoped for company intelligence plus watchlist management. Each tool covers a distinct resource, event type, or watchlist lifecycle operation, and none appear redundant or padding.

Completeness4/5

The set provides broad read coverage for companies, investors, funding, acquisitions, executive moves, and a useful aggregated company timeline. Watchlists support create, list, get, add, and remove, but there is no delete or rename operation for a watchlist, and no lightweight standalone company detail without a timeline charge.

Available Tools

11 tools

acquisitionsA

Read-only

Inspect

List acquisition and merger events ordered by announcement date, newest first. Filter by payment type, deal amount range, merger flag, or a company that is the acquirer or target. Costs one credit per returned record.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum records to return (1-100). Each returned record costs one credit.
`since`	No	Return records announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp.
`until`	No	Return records announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp.
`cursor`	No	Opaque pagination cursor returned as pagination.nextCursor on the previous page.
`isMerger`	No	Filter to mergers (true) or acquisitions (false).
`companyId`	No	Return only events where this company is the acquirer or target.
`countries`	No	Headquarters country codes (ISO alpha-2, OR). Pass "unknown" to include companies with no country on file.
`naicsCode`	No	NAICS 2022 code for the target (acquired) company. Matches the code and everything beneath it, so "51" also returns 5132 and 5173. Sector ranges work: "31-33" returns all manufacturing.
`verticals`	No	Target company sector filters (OR). Canonical values: ai, fintech, saas, devtools, healthcare, climate, robotics, cybersecurity, logistics, commerce, data, crypto, media, education, marketing, telecom, realestate, hardware, gaming, space.
`paymentType`	No	Payment type filters. Canonical values: cash, stock, mixed, undisclosed.
`maxAmountUsd`	No	Maximum deal amount in USD.
`minAmountUsd`	No	Minimum deal amount in USD.
`industryGroups`	No	Company industry groups (OR). Matched literally against the LinkedIn labels. Pass "unknown" for companies with no industry on file.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavior beyond annotations: the credit cost per returned record and the deterministic ordering. This is exactly the kind of operational context an agent needs.

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?

Two sentences with no redundancy: the first states the core operation and ordering, the second lists filtering capabilities and the credit cost. The most important facts are front-loaded, and every sentence earns its place.

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

Completeness4/5

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

For a 13-parameter read-only list tool, the description covers the essential operational facts: entity type, ordering, available filters, and cost. With no output schema, it could theoretically list return fields, but the annotations and rich parameter descriptions compensate for most gaps. Pagination is left to the schema's cursor description, which is acceptable.

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?

Schema description coverage is 100%, so the baseline is 3. The description echoes some parameter concepts such as payment type, deal amount range, merger flag, and companyId, but does not add meaning beyond the schema. It omits mention of date filters, countries, NAICS, verticals, and pagination, though the schema fully documents those.

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?

The description opens with a specific verb and resource: 'List acquisition and merger events', with ordering specified as 'by announcement date, newest first'. This clearly distinguishes it from sibling tools like funding_events or exec_moves by naming the exact event category covered.

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?

The description gives clear context for when this tool is appropriate: M&A event lookup against data sources, with a focused set of filters for payment type, deal amount, merger flag, and company involvement. It does not explicitly name alternatives or exclusion criteria, but the event-type framing makes the use case evident.

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

add_to_watchlistAInspect

Add companies (domain, name, LinkedIn URL, or id) to a watchlist. Returns a per-item result of added, already_present, or unresolved. Free.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Watchlist id.
`companies`	Yes	Company identifiers: domain, name, LinkedIn URL, or Datahyena id.

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses meaningful behavior beyond the annotations: it returns a per-item result with states 'added', 'already_present', or 'unresolved', which conveys partial success semantics and idempotency-like behavior. Annotations only provide false hints, so this output detail adds significant value, though auth/permissions or mutation effects are not discussed.

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?

The description is two concise sentences: the first states the action and accepted inputs, the second explains the return format. Every sentence earns its place with no redundant filler.

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 the tool's moderate complexity (2 required params, no output schema), the description covers the core behavior, accepted input forms, and the return result format. It is sufficient for an agent to select and invoke the tool correctly.

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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description mostly restates the accepted company identifier types already present in the schema, adding no new parameter-level meaning.

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?

The description uses a specific verb ('Add') with a clear resource ('companies... to a watchlist') and enumerates accepted identifier types (domain, name, LinkedIn URL, or id). This distinguishes it from sibling tools like remove_from_watchlist, create_watchlist, get_watchlist, and list_watchlists.

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?

The description implies when to use the tool: when adding companies to an existing watchlist. However, it does not explicitly state when not to use it or mention alternatives such as remove_from_watchlist for removal operations.

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

companiesA

Read-only

Inspect

Search and filter company records by keyword, exact domain, HQ country, industry group, NAICS code, employee-count bucket, or founded-year range. Costs one credit per returned record.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum records to return (1-100). Each returned record costs one credit.
`since`	No	Return companies created/updated on or after this date (YYYY-MM-DD) or ISO-8601 timestamp.
`cursor`	No	Opaque pagination cursor returned as pagination.nextCursor on the previous page.
`domain`	No	Exact company domain.
`search`	No	Keyword search over name, domain, and description.
`countries`	No	Headquarters country codes (ISO alpha-2, OR). Pass "unknown" to include companies with no country on file.
`naicsCode`	No	NAICS 2022 code. Matches the code and everything beneath it, so "51" also returns 5132 and 5173. Sector ranges work: "31-33" returns all manufacturing. Pass "unknown" for unclassified companies.
`foundedYearMax`	No	Maximum founded year.
`foundedYearMin`	No	Minimum founded year.
`industryGroups`	No	Company industry groups (OR). Matched literally against the LinkedIn labels. Pass "unknown" for companies with no industry on file.
`employeeCountBuckets`	No	LinkedIn employee count buckets (OR), e.g. 51-200. Pass "unknown" for no headcount.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a meaningful operational detail beyond the annotations: 'Costs one credit per returned record,' which is not otherwise visible and directly affects agent planning of result sizes.

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?

The description is a single dense sentence followed by one critical cost note. Every phrase carries information, and the core search/filter capability is front-loaded before the cost caveat. There is no filler, repetition, or schema duplication.

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

Completeness4/5

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

With 11 optional parameters, no output schema, and no required inputs, the description names all major filtering categories and flags credit usage, which is the most important non-obvious behavior. Pagination and detailed filter semantics are already in the schema, so nothing essential to invoking the tool correctly is missing.

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?

Parameter schema coverage is 100%, with each parameter already having a descriptive purpose and, where relevant, enums or defaults. The description adds only a high-level grouping of the available filters (keyword, domain, country, industry, NAICS, headcount, founded year), which is useful for comprehension but does not materially deepen the schema's parameter-level explanations.

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?

The description uses a specific verb ('Search and filter') and names the exact resource ('company records'), then enumerates the full set of filtering dimensions. This makes it clearly distinct from the sibling tools, which cover acquisitions, funding events, exec moves, and watchlist management rather than company lookup.

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?

The description implicitly tells an agent when to use this tool: whenever company records need to be searched or filtered by domain, country, industry, NAICS, headcount, or founding year. It does not explicitly name alternatives, but the sibling list makes the comparison obvious, so an agent can route correctly without extra guidance.

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

company_timelineA

Read-only

Inspect

Return one company's timeline: firmographics, investors, and a chronological list of funding rounds, acquisitions, and executive moves. Resolve the company by id, domain, name, or LinkedIn URL. Pick event kinds with include (default all). Costs one credit for the company plus one per pulled event; nothing is charged if no company matches.

ParametersJSON Schema

Name	Required	Description
`id`	No	Datahyena company id.
`name`	No	Company name.
`domain`	No	Company domain, e.g. legora.com.
`include`	No	Which event kinds to include (default all). Each pulled event costs one credit.
`linkedinUrl`	No	Company LinkedIn URL or handle.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and open-world assumptions. The description adds cost transparency: 'Costs one credit for the company plus one per pulled event; nothing is charged if no company matches.' This is valuable behavioral context—agents can weigh cost implications. It also discloses that resolution can be done via multiple identifiers, and implies partial result behavior when no company matches. No contradiction 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?

The description is three sentences: first states the core purpose, second lists resolution keys, third explains event filtering and cost. Every sentence earns its place—no fluff, front-loaded with the most important information. It's concise and logically structured.

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

Completeness4/5

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

The description covers all critical aspects for a tool with 5 optional parameters and moderate complexity: what it returns (timeline components), resolution methods, filtering, and cost. There's no output schema, so the description does a good job conveying return content. It doesn't discuss pagination or limits, but these are not critical for a timeline tool and are likely documented elsewhere. Overall, it's complete enough for an agent to invoke correctly.

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%, so parameters are already well-documented. The description adds meaning by clarifying that id, domain, name, and linkedinUrl are alternative identification methods ('Resolve the company by...'), which isn't explicitly stated in the schema descriptions. It also reinforces the include parameter's role and cost implication. This adds value beyond the 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?

The description opens with a specific verb and resource: 'Return one company's timeline' and enumerates the contained data (firmographics, investors, funding rounds, acquisitions, executive moves). It also clarifies resolution methods (id, domain, name, LinkedIn URL), distinguishing it from sibling tools like acquisitions or funding_events which focus on specific event types. This is unambiguous and differentiates from alternatives.

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?

The description provides clear context: it returns a comprehensive timeline for a single company and allows filtering event kinds via the include parameter (default all). It doesn't explicitly name alternative tools (e.g., 'use funding_events for funding only'), but it implies this is the one-stop timeline tool versus the more specialized sibling tools. The guidance is sufficient for most agents to select it appropriately.

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

create_watchlistBInspect

Create a named account watchlist. Free.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	Watchlist name.

TDQS

B3.4/5.0

Behavior2/5

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

Annotations (readOnlyHint=false) already indicate this is a write operation, and the description's 'Create' aligns with that. However, the description adds no behavioral context beyond the annotations, such as permissions, side effects, or rate limits. 'Free' is irrelevant to behavior. With annotations present, the bar is lower, but the description adds nothing of value.

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?

The description is extremely concise (two short phrases) and front-loaded with the purpose. Every word earns its place, with no redundant or filler content. It is appropriately sized for a simple tool.

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

Completeness4/5

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

For a simple 1-parameter creation tool with annotations and no output schema, the description is adequate. It conveys the core purpose and the key qualifier 'account.' It could mention success behavior or prerequisites, but given the minimal complexity and full schema coverage, it is nearly complete. A small gap is the lack of mention that this is a distinct setup step before using add_to_watchlist, but that belongs to usage guidelines.

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?

Schema description coverage is 100% (the 'name' parameter is described as 'Watchlist name.'). The tool description does not add any additional meaning beyond what the schema provides. Baseline of 3 applies because the schema already fully documents the parameter.

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?

The description clearly states the action ('Create') and the resource ('a named account watchlist'), which is a specific verb+resource pairing. It distinguishes from sibling tools like add_to_watchlist or get_watchlist by indicating it creates the watchlist itself, though it doesn't explicitly contrast them.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions 'Free' but that is not usage guidance. No exclusions or alternative tool names are given, leaving the agent to infer usage from the tool name alone.

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

exec_movesA

Read-only

Inspect

List executive appointment, promotion, departure, and transition events ordered by announcement date, newest first. Filter by company, person, role seniority, move type, or a time window. Costs one credit per returned record.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum records to return (1-100). Each returned record costs one credit.
`since`	No	Return records announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp.
`until`	No	Return records announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp.
`cursor`	No	Opaque pagination cursor returned as pagination.nextCursor on the previous page.
`moveType`	No	Move type filters. Canonical values: appointment, promotion, departure, transition.
`personId`	No	Filter by person id.
`companyId`	No	Filter by company id.
`countries`	No	Headquarters country codes (ISO alpha-2, OR). Pass "unknown" to include companies with no country on file.
`naicsCode`	No	NAICS 2022 code for the company. Matches the code and everything beneath it, so "51" also returns 5132 and 5173. Sector ranges work: "31-33" returns all manufacturing.
`roleSeniority`	No	Role seniority filters. Canonical values: c_level, vp_level, founder.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds valuable behavioral detail beyond those: results are ordered newest-first by announcement date, and each returned record costs one credit. This cost disclosure is especially useful for an agent deciding how large a result set to request.

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?

The description is three short sentences with no filler: purpose and ordering first, then filtering options, then cost. Every sentence adds independent value, and the most decision-relevant facts are front-loaded.

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

Completeness4/5

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

For a list tool with no output schema and 10 parameters, the description covers the essential operational context: what is returned, in what order, what filters exist, and the cost model. Pagination is handled by the cursor parameter description in the schema, so the absence of explicit pagination wording in the description is not a significant gap.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description only restates the filter categories (company, person, role seniority, move type, time window) without adding syntax, defaults, or enum semantics beyond what the schema provides. This is the baseline score for a fully documented 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?

The description uses a specific verb and resource: 'List executive appointment, promotion, departure, and transition events.' It also specifies the ordering ('ordered by announcement date, newest first') and the filter dimensions, making it clearly distinct from sibling tools like acquisitions, funding_events, and companies.

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?

The description gives clear context for when to use the tool: whenever executive move events are needed, with filters for company, person, seniority, move type, or time window. It does not explicitly name sibling alternatives or state when not to use it, but the domain is clear enough that an agent can route correctly.

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

funding_eventsA

Read-only

Inspect

List funding events ordered by announcement date, newest first. Filter by round, amount range, company HQ country, industry group, or a specific company id. Costs one credit per returned record.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum records to return (1-100). Each returned record costs one credit.
`round`	No	Funding round filters. Canonical values: pre-seed, seed, angel, series-a, series-b, series-c, series-d, series-e, series-f, series-g, series-h, series-i, growth, private-equity, extension, bridge, convertible, safe, debt, grant, pre-ipo, secondary, pipe, other.
`since`	No	Return records announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp.
`until`	No	Return records announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp.
`cursor`	No	Opaque pagination cursor returned as pagination.nextCursor on the previous page.
`companyId`	No	Return only events for this entity-resolved company id.
`countries`	No	Headquarters country codes (ISO alpha-2, OR). Pass "unknown" to include companies with no country on file.
`naicsCode`	No	NAICS 2022 code for the company. Matches the code and everything beneath it, so "51" also returns 5132 and 5173. Sector ranges work: "31-33" returns all manufacturing.
`verticals`	No	High-level sector filters (OR). Canonical values: ai, fintech, saas, devtools, healthcare, climate, robotics, cybersecurity, logistics, commerce, data, crypto, media, education, marketing, telecom, realestate, hardware, gaming, space.
`enrichedOnly`	No	Return only rounds whose company resolved, so every result carries a domain, industry and country rather than a bare name. Leave it off for maximum coverage: some markets are reported nowhere else, and those rounds arrive with the company name alone.
`maxAmountUsd`	No	Maximum funding amount in USD.
`minAmountUsd`	No	Minimum funding amount in USD.
`industryGroups`	No	Company industry groups (OR). Matched literally against the LinkedIn labels. Pass "unknown" for companies with no industry on file.
`employeeBuckets`	No	Company employee-count buckets (OR). Canonical values: 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+.

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so the safety profile is covered by structured data. The description adds genuinely useful behavior beyond that: the newest-first ordering and the per-record credit cost, which matters for a metered data endpoint. It omits pagination mechanics, but the schema covers the cursor.

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?

Two sentences with zero waste: the first establishes resource, ordering, and filters, the second front-loads the cost implication. Nothing is repeated or padded.

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

Completeness4/5

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

For a 14-parameter list endpoint with a 100% documented schema and an output schema absent, the description supplies ordering and cost but does not explain the return shape or pagination flow. Given the schema's cursor documentation, this is close to complete but not exhaustive.

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?

Schema description coverage is 100%, so every one of the 14 parameters is already documented in the schema (including enum values, NAICS hierarchy matching, and the enrichedOnly tradeoff). The description's filter list adds no syntax or semantics beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ("List funding events") plus the default ordering (announcement date, newest first) and the filterable dimensions. It never names or distinguishes itself from siblings, but the sibling set (companies, investors, acquisitions) covers clearly different resources so the risk of confusion is low.

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?

The description enumerates the filter dimensions, which implies when the tool is useful, but gives no explicit when-to-use/when-not guidance or pointers to alternatives. Usage is inferable rather than stated.

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

get_watchlistA

Read-only

Inspect

Return one watchlist with its resolved company members. Free.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Watchlist id.

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already cover the read-only and non-destructive nature of the tool. The description adds 'resolved company members' as a return detail but 'Free.' is vague and adds little behavioral context. No contradiction 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.

Conciseness4/5

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

The description is very short and front-loaded with the core purpose. The standalone 'Free.' sentence is ambiguous and arguably unnecessary, but overall the description avoids fluff and is easy to parse.

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

Completeness4/5

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

For a simple one-parameter read-only lookup, the description is reasonably complete with annotations covering safety. It clarifies the return content ('resolved company members'), which is useful since no output schema exists.

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?

The schema already documents the single parameter 'id' with description 'Watchlist id,' giving 100% coverage. The description does not add significant parameter semantics beyond implying a single watchlist is fetched.

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?

The description clearly states the tool's function with a specific verb and resource: 'Return one watchlist with its resolved company members.' This distinguishes it from sibling tools like list_watchlists (plural) and add_to_watchlist/remove_from_watchlist (mutations).

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?

The description implies usage for retrieving a specific watchlist by ID, but it does not explicitly mention when to use it over alternatives or provide any exclusions. The context is clear but guidance is minimal.

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

investorsA

Read-only

Inspect

Search and filter investor records by keyword, type, HQ country, or exact domain. Costs one credit per returned record.

ParametersJSON Schema

Name	Required	Description
`type`	No	Investor type filters. Canonical values: vc, angel, cvc, pe, growth, accelerator, family_office, syndicate, unknown.
`limit`	No	Maximum records to return (1-100). Each returned record costs one credit.
`since`	No	Return investors created/updated on or after this date (YYYY-MM-DD) or ISO-8601 timestamp.
`cursor`	No	Opaque pagination cursor returned as pagination.nextCursor on the previous page.
`domain`	No	Exact investor domain.
`search`	No	Keyword search over investor name and domain.
`countries`	No	Headquarters country codes (ISO alpha-2, OR). Pass "unknown" to include companies with no country on file.
`investsIn`	No	Only investors that have funded companies headquartered in these countries (OR), e.g. ["US"]. Filters on where an investor deploys rather than where it is registered, and is far better covered than HQ country.
`minRounds`	No	Only investors that have participated in at least this many rounds.
`activeSince`	No	Only investors whose most recent round was announced on or after this date (YYYY-MM-DD).
`minRoundUsd`	No	Only investors that have participated in at least one round at or above this amount, in whole USD. Filters on behaviour rather than on a type label, which is sparse.
`hasFirmographics`	No	Only investors whose domain and type we have resolved.

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-destructive; the description reinforces that with 'Search and filter' and adds a useful economic constraint: 'Costs one credit per returned record.' This credit cost is material behavioral information beyond what annotations provide, though pagination and result format are not disclosed.

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?

Two short sentences with the core action and filters first, followed by the cost warning. No filler, no redundancy with the schema, and every sentence earns its place.

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

Completeness3/5

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

The description gives the essential purpose and cost, and the schema covers all inputs, but with 12 optional filters, no output schema, and no pagination or return-format note, an agent may not know the full breadth of filters (e.g., investsIn, minRounds, activeSince) or what a returned record contains. Adequate but with clear gaps.

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?

All 12 parameters are fully described in the schema (100% coverage), so the description is not required to repeat them. It echoes the main filters (type, countries, domain, search) and adds the credit-cost nuance on limit, but adds no new semantics beyond the schema. Baseline 3 applies.

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?

The description uses the action verbs 'Search and filter' on 'investor records' and names the key dimensions (keyword, type, HQ country, exact domain), making it clear what resource this tool operates on. This distinguishes it from resource-specific siblings like companies, funding_events, or acquisitions.

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?

The description implies usage by naming the resource and filter dimensions, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. There are no exclusions or references to sibling tools, so the agent must infer that investor-record queries go here.

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

list_watchlistsA

Read-only

Inspect

List the workspace's account watchlists with member counts. Free.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already state readOnlyHint=true and destructiveHint=false, so the description need not repeat those. It adds value by specifying the scope ('workspace's account'), that member counts are included, and the 'Free.' note, which could indicate no cost or restrictions. No contradiction with annotations exists, and the description supplements them meaningfully.

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?

The description is two short sentences with zero fluff. It front-loads the core action and outcome, and the 'Free.' addition is a concise extra. Every word earns its place, making it exceptionally efficient.

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?

For a simple list operation with no parameters and no output schema, the description is sufficiently complete. It specifies the scope, includes a notable detail (member counts), and is supported by strong annotations. Sibling tools provide context that this is the enumeration function, so nothing essential is missing.

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?

There are zero parameters, so the schema coverage is trivially 100%. Per rubric, baseline is 4 for 0 parameters. The description doesn't need to add parameter details since there are none; it correctly focuses on the tool's behavior. No additional semantic information is required.

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?

The description uses a specific verb ('List') and resource ('workspace's account watchlists') with a distinct outcome ('with member counts'). It clearly differentiates from siblings like get_watchlist (which likely retrieves a single watchlist) and create/remove/add tools. The purpose is unambiguous and well-scoped.

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?

The description implies when to use (to list all watchlists in the workspace) but does not explicitly mention alternatives or exclusion criteria. Given sibling names, the context is clear enough that an agent could infer when to use this tool over get_watchlist. However, it lacks an explicit 'use this when you need all watchlists' statement, so it isn't a perfect 5.

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

remove_from_watchlistA

DestructiveIdempotent

Inspect

Remove companies from a watchlist. Free.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Watchlist id.
`companies`	Yes	Company identifiers: domain, name, LinkedIn URL, or Datahyena id.

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate destructiveHint=true, and the description's 'Remove' is consistent. However, the description adds no additional behavioral context such as irreversibility, permission requirements, or side effects beyond the annotation. Since annotations cover the safety profile, this is acceptable but not enhanced.

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?

The description is extremely concise: 'Remove companies from a watchlist. Free.' It contains no unnecessary words, and the structure is clean. The 'Free.' is somewhat extraneous but does not detract; overall it is highly focused.

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

Completeness4/5

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

The description adequately conveys the core operation, but it does not specify what happens after the removal (e.g., return value or success/failure semantics). Since there is no output schema, this is not required, but a more complete description might mention whether the updated watchlist is returned or if errors are expected. It is sufficient for a simple destructive action but lacks a minor detail.

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?

Schema coverage is 100% with descriptions for both parameters. The description for 'companies' adds useful detail about accepted identifier formats ('domain, name, LinkedIn URL, or Datahyena id'), but the 'id' description is minimal ('Watchlist id.'). This matches the baseline for full schema coverage without significant extra value.

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?

The description clearly states the action: 'Remove companies from a watchlist.' It names the specific verb and resource, and it distinguishes from sibling tools like add_to_watchlist or create_watchlist. The purpose is unambiguous.

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?

The description implies usage (when you need to remove companies) but does not explicitly mention when not to use it or suggest alternative tools. Unlike the HIGH example, it lacks an explicit cross-reference such as 'use add_to_watchlist instead.' The context of sibling tools makes it clear, but the description itself does not provide explicit guidance.

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 tool updateSep 13, 2026

Changedfunding_events1 field changed

addedInput schema / properties / enrichedOnly

Added value: +{
+  "description": "Return only rounds whose company resolved, so every result carries a domain, industry and country rather than a bare name. Leave it off for maximum coverage: some markets are reported nowhere else, and those rounds arrive with the company name alone.",
+  "type": "boolean"
+}

1 tool updateSep 4, 2026

Changedfunding_events2 fields changed

changedInput schema / properties / round / description

Previous value: -"Funding round filters. Canonical values: pre-seed, seed, angel, series-a, series-b, series-c, series-d, series-e, series-f, series-g, series-h, series-i, growth, extension, bridge, convertible, safe, debt, grant, pre-ipo, secondary, pipe, other."New value: +"Funding round filters. Canonical values: pre-seed, seed, angel, series-a, series-b, series-c, series-d, series-e, series-f, series-g, series-h, series-i, growth, private-equity, extension, bridge, convertible, safe, debt, grant, pre-ipo, secondary, pipe, other."

changedInput schema / properties / round / items / enum

Previous value: -[
-  "pre-seed",
-  "seed",
-  "angel",
-  "series-a",
-  "series-b",
-  "series-c",
-  "series-d",
-  "series-e",
-  "series-f",
-  "series-g",
-  "series-h",
-  "series-i",
-  "growth",
-  "extension",
-  "bridge",
-  "convertible",
-  "safe",
-  "debt",
-  "grant",
-  "pre-ipo",
-  "secondary",
-  "pipe",
-  "other",
-  "unknown"
-]New value: +[
+  "pre-seed",
+  "seed",
+  "angel",
+  "series-a",
+  "series-b",
+  "series-c",
+  "series-d",
+  "series-e",
+  "series-f",
+  "series-g",
+  "series-h",
+  "series-i",
+  "growth",
+  "private-equity",
+  "extension",
+  "bridge",
+  "convertible",
+  "safe",
+  "debt",
+  "grant",
+  "pre-ipo",
+  "secondary",
+  "pipe",
+  "other",
+  "unknown"
+]

5 tool updatesAug 27, 2026

Changedacquisitions1 field changed

changedInput schema / properties / countries / items / enum

Previous value: -[
-  "unknown",
-  "AD",
-  "AE",
-  "AF",
-  "AG",
-  "AL",
-  "AM",
-  "AO",
-  "AR",
-  "AT",
-  "AU",
-  "AZ",
-  "BA",
-  "BB",
-  "BD",
-  "BE",
-  "BF",
-  "BG",
-  "BH",
-  "BI",
-  "BJ",
-  "BM",
-  "BN",
-  "BO",
-  "BR",
-  "BS",
-  "BT",
-  "BW",
-  "BY",
-  "BZ",
-  "CA",
-  "CD",
-  "CF",
-  "CG",
-  "CH",
-  "CI",
-  "CL",
-  "CM",
-  "CN",
-  "CO",
-  "CR",
-  "CU",
-  "CV",
-  "CY",
-  "CZ",
-  "DE",
-  "DJ",
-  "DK",
-  "DM",
-  "DO",
-  "DZ",
-  "EC",
-  "EE",
-  "EG",
-  "ER",
-  "ES",
-  "ET",
-  "FI",
-  "FJ",
-  "FM",
-  "FR",
-  "GA",
-  "GB",
-  "GD",
-  "GE",
-  "GG",
-  "GH",
-  "GI",
-  "GM",
-  "GN",
-  "GQ",
-  "GR",
-  "GT",
-  "GW",
-  "GY",
-  "HK",
-  "HN",
-  "HR",
-  "HT",
-  "HU",
-  "ID",
-  "IE",
-  "IL",
-  "IM",
-  "IN",
-  "IQ",
-  "IR",
-  "IS",
-  "IT",
-  "JE",
-  "JM",
-  "JO",
-  "JP",
-  "KE",
-  "KG",
-  "KH",
-  "KI",
-  "KM",
-  "KN",
-  "KP",
-  "KR",
-  "KW",
-  "KY",
-  "KZ",
-  "LA",
-  "LB",
-  "LC",
-  "LI",
-  "LK",
-  "LR",
-  "LS",
-  "LT",
-  "LU",
-  "LV",
-  "LY",
-  "MA",
-  "MC",
-  "MD",
-  "ME",
-  "MG",
-  "MH",
-  "MK",
-  "ML",
-  "MM",
-  "MN",
-  "MO",
-  "MR",
-  "MT",
-  "MU",
-  "MV",
-  "MW",
-  "MX",
-  "MY",
-  "MZ",
-  "NA",
-  "NE",
-  "NG",
-  "NI",
-  "NL",
-  "NO",
-  "NP",
-  "NR",
-  "NZ",
-  "OM",
-  "PA",
-  "PG",
-  "PH",
-  "PK",
-  "PL",
-  "PR",
-  "PS",
-  "PT",
-  "PW",
-  "PY",
-  "QA",
-  "RO",
-  "RS",
-  "RU",
-  "RW",
-  "SA",
-  "SB",
-  "SC",
-  "SD",
-  "SE",
-  "SG",
-  "SI",
-  "SK",
-  "SL",
-  "SM",
-  "SN",
-  "SO",
-  "SR",
-  "SS",
-  "ST",
-  "SV",
-  "SY",
-  "SZ",
-  "TD",
-  "TG",
-  "TH",
-  "TJ",
-  "TL",
-  "TM",
-  "TN",
-  "TO",
-  "TR",
-  "TT",
-  "TV",
-  "TW",
-  "TZ",
-  "UA",
-  "UG",
-  "US",
-  "UY",
-  "UZ",
-  "VA",
-  "VC",
-  "VE",
-  "VG",
-  "VN",
-  "VU",
-  "WS",
-  "YE",
-  "ZA",
-  "ZM",
-  "ZW"
-]New value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AI",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AS",
+  "AT",
+  "AU",
+  "AW",
+  "AX",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BL",
+  "BM",
+  "BN",
+  "BO",
+  "BQ",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CK",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CW",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "EH",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FK",
+  "FM",
+  "FO",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GF",
+  "GG",
+  "GH",
+  "GI",
+  "GL",
+  "GM",
+  "GN",
+  "GP",
+  "GQ",
+  "GR",
+  "GT",
+  "GU",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MF",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MP",
+  "MQ",
+  "MR",
+  "MS",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NC",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NU",
+  "NZ",
+  "OM",
+  "PA",
+  "PE",
+  "PF",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PM",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RE",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SH",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SX",
+  "SY",
+  "SZ",
+  "TC",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TK",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VI",
+  "VN",
+  "VU",
+  "WF",
+  "WS",
+  "YE",
+  "YT",
+  "ZA",
+  "ZM",
+  "ZW"
+]

Changedcompanies1 field changed

changedInput schema / properties / countries / items / enum

Previous value: -[
-  "unknown",
-  "AD",
-  "AE",
-  "AF",
-  "AG",
-  "AL",
-  "AM",
-  "AO",
-  "AR",
-  "AT",
-  "AU",
-  "AZ",
-  "BA",
-  "BB",
-  "BD",
-  "BE",
-  "BF",
-  "BG",
-  "BH",
-  "BI",
-  "BJ",
-  "BM",
-  "BN",
-  "BO",
-  "BR",
-  "BS",
-  "BT",
-  "BW",
-  "BY",
-  "BZ",
-  "CA",
-  "CD",
-  "CF",
-  "CG",
-  "CH",
-  "CI",
-  "CL",
-  "CM",
-  "CN",
-  "CO",
-  "CR",
-  "CU",
-  "CV",
-  "CY",
-  "CZ",
-  "DE",
-  "DJ",
-  "DK",
-  "DM",
-  "DO",
-  "DZ",
-  "EC",
-  "EE",
-  "EG",
-  "ER",
-  "ES",
-  "ET",
-  "FI",
-  "FJ",
-  "FM",
-  "FR",
-  "GA",
-  "GB",
-  "GD",
-  "GE",
-  "GG",
-  "GH",
-  "GI",
-  "GM",
-  "GN",
-  "GQ",
-  "GR",
-  "GT",
-  "GW",
-  "GY",
-  "HK",
-  "HN",
-  "HR",
-  "HT",
-  "HU",
-  "ID",
-  "IE",
-  "IL",
-  "IM",
-  "IN",
-  "IQ",
-  "IR",
-  "IS",
-  "IT",
-  "JE",
-  "JM",
-  "JO",
-  "JP",
-  "KE",
-  "KG",
-  "KH",
-  "KI",
-  "KM",
-  "KN",
-  "KP",
-  "KR",
-  "KW",
-  "KY",
-  "KZ",
-  "LA",
-  "LB",
-  "LC",
-  "LI",
-  "LK",
-  "LR",
-  "LS",
-  "LT",
-  "LU",
-  "LV",
-  "LY",
-  "MA",
-  "MC",
-  "MD",
-  "ME",
-  "MG",
-  "MH",
-  "MK",
-  "ML",
-  "MM",
-  "MN",
-  "MO",
-  "MR",
-  "MT",
-  "MU",
-  "MV",
-  "MW",
-  "MX",
-  "MY",
-  "MZ",
-  "NA",
-  "NE",
-  "NG",
-  "NI",
-  "NL",
-  "NO",
-  "NP",
-  "NR",
-  "NZ",
-  "OM",
-  "PA",
-  "PG",
-  "PH",
-  "PK",
-  "PL",
-  "PR",
-  "PS",
-  "PT",
-  "PW",
-  "PY",
-  "QA",
-  "RO",
-  "RS",
-  "RU",
-  "RW",
-  "SA",
-  "SB",
-  "SC",
-  "SD",
-  "SE",
-  "SG",
-  "SI",
-  "SK",
-  "SL",
-  "SM",
-  "SN",
-  "SO",
-  "SR",
-  "SS",
-  "ST",
-  "SV",
-  "SY",
-  "SZ",
-  "TD",
-  "TG",
-  "TH",
-  "TJ",
-  "TL",
-  "TM",
-  "TN",
-  "TO",
-  "TR",
-  "TT",
-  "TV",
-  "TW",
-  "TZ",
-  "UA",
-  "UG",
-  "US",
-  "UY",
-  "UZ",
-  "VA",
-  "VC",
-  "VE",
-  "VG",
-  "VN",
-  "VU",
-  "WS",
-  "YE",
-  "ZA",
-  "ZM",
-  "ZW"
-]New value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AI",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AS",
+  "AT",
+  "AU",
+  "AW",
+  "AX",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BL",
+  "BM",
+  "BN",
+  "BO",
+  "BQ",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CK",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CW",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "EH",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FK",
+  "FM",
+  "FO",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GF",
+  "GG",
+  "GH",
+  "GI",
+  "GL",
+  "GM",
+  "GN",
+  "GP",
+  "GQ",
+  "GR",
+  "GT",
+  "GU",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MF",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MP",
+  "MQ",
+  "MR",
+  "MS",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NC",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NU",
+  "NZ",
+  "OM",
+  "PA",
+  "PE",
+  "PF",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PM",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RE",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SH",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SX",
+  "SY",
+  "SZ",
+  "TC",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TK",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VI",
+  "VN",
+  "VU",
+  "WF",
+  "WS",
+  "YE",
+  "YT",
+  "ZA",
+  "ZM",
+  "ZW"
+]

Changedexec_moves1 field changed

changedInput schema / properties / countries / items / enum

Previous value: -[
-  "unknown",
-  "AD",
-  "AE",
-  "AF",
-  "AG",
-  "AL",
-  "AM",
-  "AO",
-  "AR",
-  "AT",
-  "AU",
-  "AZ",
-  "BA",
-  "BB",
-  "BD",
-  "BE",
-  "BF",
-  "BG",
-  "BH",
-  "BI",
-  "BJ",
-  "BM",
-  "BN",
-  "BO",
-  "BR",
-  "BS",
-  "BT",
-  "BW",
-  "BY",
-  "BZ",
-  "CA",
-  "CD",
-  "CF",
-  "CG",
-  "CH",
-  "CI",
-  "CL",
-  "CM",
-  "CN",
-  "CO",
-  "CR",
-  "CU",
-  "CV",
-  "CY",
-  "CZ",
-  "DE",
-  "DJ",
-  "DK",
-  "DM",
-  "DO",
-  "DZ",
-  "EC",
-  "EE",
-  "EG",
-  "ER",
-  "ES",
-  "ET",
-  "FI",
-  "FJ",
-  "FM",
-  "FR",
-  "GA",
-  "GB",
-  "GD",
-  "GE",
-  "GG",
-  "GH",
-  "GI",
-  "GM",
-  "GN",
-  "GQ",
-  "GR",
-  "GT",
-  "GW",
-  "GY",
-  "HK",
-  "HN",
-  "HR",
-  "HT",
-  "HU",
-  "ID",
-  "IE",
-  "IL",
-  "IM",
-  "IN",
-  "IQ",
-  "IR",
-  "IS",
-  "IT",
-  "JE",
-  "JM",
-  "JO",
-  "JP",
-  "KE",
-  "KG",
-  "KH",
-  "KI",
-  "KM",
-  "KN",
-  "KP",
-  "KR",
-  "KW",
-  "KY",
-  "KZ",
-  "LA",
-  "LB",
-  "LC",
-  "LI",
-  "LK",
-  "LR",
-  "LS",
-  "LT",
-  "LU",
-  "LV",
-  "LY",
-  "MA",
-  "MC",
-  "MD",
-  "ME",
-  "MG",
-  "MH",
-  "MK",
-  "ML",
-  "MM",
-  "MN",
-  "MO",
-  "MR",
-  "MT",
-  "MU",
-  "MV",
-  "MW",
-  "MX",
-  "MY",
-  "MZ",
-  "NA",
-  "NE",
-  "NG",
-  "NI",
-  "NL",
-  "NO",
-  "NP",
-  "NR",
-  "NZ",
-  "OM",
-  "PA",
-  "PG",
-  "PH",
-  "PK",
-  "PL",
-  "PR",
-  "PS",
-  "PT",
-  "PW",
-  "PY",
-  "QA",
-  "RO",
-  "RS",
-  "RU",
-  "RW",
-  "SA",
-  "SB",
-  "SC",
-  "SD",
-  "SE",
-  "SG",
-  "SI",
-  "SK",
-  "SL",
-  "SM",
-  "SN",
-  "SO",
-  "SR",
-  "SS",
-  "ST",
-  "SV",
-  "SY",
-  "SZ",
-  "TD",
-  "TG",
-  "TH",
-  "TJ",
-  "TL",
-  "TM",
-  "TN",
-  "TO",
-  "TR",
-  "TT",
-  "TV",
-  "TW",
-  "TZ",
-  "UA",
-  "UG",
-  "US",
-  "UY",
-  "UZ",
-  "VA",
-  "VC",
-  "VE",
-  "VG",
-  "VN",
-  "VU",
-  "WS",
-  "YE",
-  "ZA",
-  "ZM",
-  "ZW"
-]New value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AI",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AS",
+  "AT",
+  "AU",
+  "AW",
+  "AX",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BL",
+  "BM",
+  "BN",
+  "BO",
+  "BQ",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CK",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CW",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "EH",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FK",
+  "FM",
+  "FO",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GF",
+  "GG",
+  "GH",
+  "GI",
+  "GL",
+  "GM",
+  "GN",
+  "GP",
+  "GQ",
+  "GR",
+  "GT",
+  "GU",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MF",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MP",
+  "MQ",
+  "MR",
+  "MS",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NC",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NU",
+  "NZ",
+  "OM",
+  "PA",
+  "PE",
+  "PF",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PM",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RE",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SH",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SX",
+  "SY",
+  "SZ",
+  "TC",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TK",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VI",
+  "VN",
+  "VU",
+  "WF",
+  "WS",
+  "YE",
+  "YT",
+  "ZA",
+  "ZM",
+  "ZW"
+]

Changedfunding_events1 field changed

changedInput schema / properties / countries / items / enum

Previous value: -[
-  "unknown",
-  "AD",
-  "AE",
-  "AF",
-  "AG",
-  "AL",
-  "AM",
-  "AO",
-  "AR",
-  "AT",
-  "AU",
-  "AZ",
-  "BA",
-  "BB",
-  "BD",
-  "BE",
-  "BF",
-  "BG",
-  "BH",
-  "BI",
-  "BJ",
-  "BM",
-  "BN",
-  "BO",
-  "BR",
-  "BS",
-  "BT",
-  "BW",
-  "BY",
-  "BZ",
-  "CA",
-  "CD",
-  "CF",
-  "CG",
-  "CH",
-  "CI",
-  "CL",
-  "CM",
-  "CN",
-  "CO",
-  "CR",
-  "CU",
-  "CV",
-  "CY",
-  "CZ",
-  "DE",
-  "DJ",
-  "DK",
-  "DM",
-  "DO",
-  "DZ",
-  "EC",
-  "EE",
-  "EG",
-  "ER",
-  "ES",
-  "ET",
-  "FI",
-  "FJ",
-  "FM",
-  "FR",
-  "GA",
-  "GB",
-  "GD",
-  "GE",
-  "GG",
-  "GH",
-  "GI",
-  "GM",
-  "GN",
-  "GQ",
-  "GR",
-  "GT",
-  "GW",
-  "GY",
-  "HK",
-  "HN",
-  "HR",
-  "HT",
-  "HU",
-  "ID",
-  "IE",
-  "IL",
-  "IM",
-  "IN",
-  "IQ",
-  "IR",
-  "IS",
-  "IT",
-  "JE",
-  "JM",
-  "JO",
-  "JP",
-  "KE",
-  "KG",
-  "KH",
-  "KI",
-  "KM",
-  "KN",
-  "KP",
-  "KR",
-  "KW",
-  "KY",
-  "KZ",
-  "LA",
-  "LB",
-  "LC",
-  "LI",
-  "LK",
-  "LR",
-  "LS",
-  "LT",
-  "LU",
-  "LV",
-  "LY",
-  "MA",
-  "MC",
-  "MD",
-  "ME",
-  "MG",
-  "MH",
-  "MK",
-  "ML",
-  "MM",
-  "MN",
-  "MO",
-  "MR",
-  "MT",
-  "MU",
-  "MV",
-  "MW",
-  "MX",
-  "MY",
-  "MZ",
-  "NA",
-  "NE",
-  "NG",
-  "NI",
-  "NL",
-  "NO",
-  "NP",
-  "NR",
-  "NZ",
-  "OM",
-  "PA",
-  "PG",
-  "PH",
-  "PK",
-  "PL",
-  "PR",
-  "PS",
-  "PT",
-  "PW",
-  "PY",
-  "QA",
-  "RO",
-  "RS",
-  "RU",
-  "RW",
-  "SA",
-  "SB",
-  "SC",
-  "SD",
-  "SE",
-  "SG",
-  "SI",
-  "SK",
-  "SL",
-  "SM",
-  "SN",
-  "SO",
-  "SR",
-  "SS",
-  "ST",
-  "SV",
-  "SY",
-  "SZ",
-  "TD",
-  "TG",
-  "TH",
-  "TJ",
-  "TL",
-  "TM",
-  "TN",
-  "TO",
-  "TR",
-  "TT",
-  "TV",
-  "TW",
-  "TZ",
-  "UA",
-  "UG",
-  "US",
-  "UY",
-  "UZ",
-  "VA",
-  "VC",
-  "VE",
-  "VG",
-  "VN",
-  "VU",
-  "WS",
-  "YE",
-  "ZA",
-  "ZM",
-  "ZW"
-]New value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AI",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AS",
+  "AT",
+  "AU",
+  "AW",
+  "AX",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BL",
+  "BM",
+  "BN",
+  "BO",
+  "BQ",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CK",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CW",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "EH",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FK",
+  "FM",
+  "FO",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GF",
+  "GG",
+  "GH",
+  "GI",
+  "GL",
+  "GM",
+  "GN",
+  "GP",
+  "GQ",
+  "GR",
+  "GT",
+  "GU",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MF",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MP",
+  "MQ",
+  "MR",
+  "MS",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NC",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NU",
+  "NZ",
+  "OM",
+  "PA",
+  "PE",
+  "PF",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PM",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RE",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SH",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SX",
+  "SY",
+  "SZ",
+  "TC",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TK",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VI",
+  "VN",
+  "VU",
+  "WF",
+  "WS",
+  "YE",
+  "YT",
+  "ZA",
+  "ZM",
+  "ZW"
+]

Changedinvestors2 fields changed

changedInput schema / properties / countries / items / enum

Previous value: -[
-  "unknown",
-  "AD",
-  "AE",
-  "AF",
-  "AG",
-  "AL",
-  "AM",
-  "AO",
-  "AR",
-  "AT",
-  "AU",
-  "AZ",
-  "BA",
-  "BB",
-  "BD",
-  "BE",
-  "BF",
-  "BG",
-  "BH",
-  "BI",
-  "BJ",
-  "BM",
-  "BN",
-  "BO",
-  "BR",
-  "BS",
-  "BT",
-  "BW",
-  "BY",
-  "BZ",
-  "CA",
-  "CD",
-  "CF",
-  "CG",
-  "CH",
-  "CI",
-  "CL",
-  "CM",
-  "CN",
-  "CO",
-  "CR",
-  "CU",
-  "CV",
-  "CY",
-  "CZ",
-  "DE",
-  "DJ",
-  "DK",
-  "DM",
-  "DO",
-  "DZ",
-  "EC",
-  "EE",
-  "EG",
-  "ER",
-  "ES",
-  "ET",
-  "FI",
-  "FJ",
-  "FM",
-  "FR",
-  "GA",
-  "GB",
-  "GD",
-  "GE",
-  "GG",
-  "GH",
-  "GI",
-  "GM",
-  "GN",
-  "GQ",
-  "GR",
-  "GT",
-  "GW",
-  "GY",
-  "HK",
-  "HN",
-  "HR",
-  "HT",
-  "HU",
-  "ID",
-  "IE",
-  "IL",
-  "IM",
-  "IN",
-  "IQ",
-  "IR",
-  "IS",
-  "IT",
-  "JE",
-  "JM",
-  "JO",
-  "JP",
-  "KE",
-  "KG",
-  "KH",
-  "KI",
-  "KM",
-  "KN",
-  "KP",
-  "KR",
-  "KW",
-  "KY",
-  "KZ",
-  "LA",
-  "LB",
-  "LC",
-  "LI",
-  "LK",
-  "LR",
-  "LS",
-  "LT",
-  "LU",
-  "LV",
-  "LY",
-  "MA",
-  "MC",
-  "MD",
-  "ME",
-  "MG",
-  "MH",
-  "MK",
-  "ML",
-  "MM",
-  "MN",
-  "MO",
-  "MR",
-  "MT",
-  "MU",
-  "MV",
-  "MW",
-  "MX",
-  "MY",
-  "MZ",
-  "NA",
-  "NE",
-  "NG",
-  "NI",
-  "NL",
-  "NO",
-  "NP",
-  "NR",
-  "NZ",
-  "OM",
-  "PA",
-  "PG",
-  "PH",
-  "PK",
-  "PL",
-  "PR",
-  "PS",
-  "PT",
-  "PW",
-  "PY",
-  "QA",
-  "RO",
-  "RS",
-  "RU",
-  "RW",
-  "SA",
-  "SB",
-  "SC",
-  "SD",
-  "SE",
-  "SG",
-  "SI",
-  "SK",
-  "SL",
-  "SM",
-  "SN",
-  "SO",
-  "SR",
-  "SS",
-  "ST",
-  "SV",
-  "SY",
-  "SZ",
-  "TD",
-  "TG",
-  "TH",
-  "TJ",
-  "TL",
-  "TM",
-  "TN",
-  "TO",
-  "TR",
-  "TT",
-  "TV",
-  "TW",
-  "TZ",
-  "UA",
-  "UG",
-  "US",
-  "UY",
-  "UZ",
-  "VA",
-  "VC",
-  "VE",
-  "VG",
-  "VN",
-  "VU",
-  "WS",
-  "YE",
-  "ZA",
-  "ZM",
-  "ZW"
-]New value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AI",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AS",
+  "AT",
+  "AU",
+  "AW",
+  "AX",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BL",
+  "BM",
+  "BN",
+  "BO",
+  "BQ",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CK",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CW",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "EH",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FK",
+  "FM",
+  "FO",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GF",
+  "GG",
+  "GH",
+  "GI",
+  "GL",
+  "GM",
+  "GN",
+  "GP",
+  "GQ",
+  "GR",
+  "GT",
+  "GU",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MF",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MP",
+  "MQ",
+  "MR",
+  "MS",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NC",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NU",
+  "NZ",
+  "OM",
+  "PA",
+  "PE",
+  "PF",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PM",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RE",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SH",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SX",
+  "SY",
+  "SZ",
+  "TC",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TK",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VI",
+  "VN",
+  "VU",
+  "WF",
+  "WS",
+  "YE",
+  "YT",
+  "ZA",
+  "ZM",
+  "ZW"
+]

addedInput schema / properties / investsIn

Added value: +{
+  "description": "Only investors that have funded companies headquartered in these countries (OR), e.g. [\"US\"]. Filters on where an investor deploys rather than where it is registered, and is far better covered than HQ country.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

1 tool updateAug 27, 2026

Changedinvestors3 fields changed

addedInput schema / properties / activeSince

Added value: +{
+  "description": "Only investors whose most recent round was announced on or after this date (YYYY-MM-DD).",
+  "type": "string"
+}

addedInput schema / properties / minRoundUsd

Added value: +{
+  "description": "Only investors that have participated in at least one round at or above this amount, in whole USD. Filters on behaviour rather than on a type label, which is sparse.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / minRounds

Added value: +{
+  "description": "Only investors that have participated in at least this many rounds.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

5 tool updatesAug 26, 2026

Changedacquisitions1 field changed

addedInput schema / properties / countries / items / enum

Added value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AT",
+  "AU",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BM",
+  "BN",
+  "BO",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FM",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GG",
+  "GH",
+  "GI",
+  "GM",
+  "GN",
+  "GQ",
+  "GR",
+  "GT",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MR",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NZ",
+  "OM",
+  "PA",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SY",
+  "SZ",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VN",
+  "VU",
+  "WS",
+  "YE",
+  "ZA",
+  "ZM",
+  "ZW"
+]

Changedcompanies1 field changed

addedInput schema / properties / countries / items / enum

Added value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AT",
+  "AU",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BM",
+  "BN",
+  "BO",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FM",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GG",
+  "GH",
+  "GI",
+  "GM",
+  "GN",
+  "GQ",
+  "GR",
+  "GT",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MR",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NZ",
+  "OM",
+  "PA",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SY",
+  "SZ",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VN",
+  "VU",
+  "WS",
+  "YE",
+  "ZA",
+  "ZM",
+  "ZW"
+]

Changedexec_moves1 field changed

addedInput schema / properties / countries / items / enum

Added value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AT",
+  "AU",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BM",
+  "BN",
+  "BO",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FM",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GG",
+  "GH",
+  "GI",
+  "GM",
+  "GN",
+  "GQ",
+  "GR",
+  "GT",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MR",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NZ",
+  "OM",
+  "PA",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SY",
+  "SZ",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VN",
+  "VU",
+  "WS",
+  "YE",
+  "ZA",
+  "ZM",
+  "ZW"
+]

Changedfunding_events1 field changed

addedInput schema / properties / countries / items / enum

Added value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AT",
+  "AU",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BM",
+  "BN",
+  "BO",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FM",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GG",
+  "GH",
+  "GI",
+  "GM",
+  "GN",
+  "GQ",
+  "GR",
+  "GT",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MR",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NZ",
+  "OM",
+  "PA",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SY",
+  "SZ",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VN",
+  "VU",
+  "WS",
+  "YE",
+  "ZA",
+  "ZM",
+  "ZW"
+]

Changedinvestors1 field changed

addedInput schema / properties / countries / items / enum

Added value: +[
+  "unknown",
+  "AD",
+  "AE",
+  "AF",
+  "AG",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AT",
+  "AU",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BM",
+  "BN",
+  "BO",
+  "BR",
+  "BS",
+  "BT",
+  "BW",
+  "BY",
+  "BZ",
+  "CA",
+  "CD",
+  "CF",
+  "CG",
+  "CH",
+  "CI",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CU",
+  "CV",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FM",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GG",
+  "GH",
+  "GI",
+  "GM",
+  "GN",
+  "GQ",
+  "GR",
+  "GT",
+  "GW",
+  "GY",
+  "HK",
+  "HN",
+  "HR",
+  "HT",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IQ",
+  "IR",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KP",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "LY",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MG",
+  "MH",
+  "MK",
+  "ML",
+  "MM",
+  "MN",
+  "MO",
+  "MR",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NE",
+  "NG",
+  "NI",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NZ",
+  "OM",
+  "PA",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RO",
+  "RS",
+  "RU",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SD",
+  "SE",
+  "SG",
+  "SI",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SO",
+  "SR",
+  "SS",
+  "ST",
+  "SV",
+  "SY",
+  "SZ",
+  "TD",
+  "TG",
+  "TH",
+  "TJ",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VE",
+  "VG",
+  "VN",
+  "VU",
+  "WS",
+  "YE",
+  "ZA",
+  "ZM",
+  "ZW"
+]

5 tool updatesAug 26, 2026

Changedacquisitions3 fields changed

addedInput schema / properties / countries

Added value: +{
+  "description": "Headquarters country codes (ISO alpha-2, OR). Pass \"unknown\" to include companies with no country on file.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / industryGroups

Added value: +{
+  "description": "Company industry groups (OR). Matched literally against the LinkedIn labels. Pass \"unknown\" for companies with no industry on file.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / until

Added value: +{
+  "description": "Return records announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp.",
+  "type": "string"
+}

Changedcompanies6 fields changed

addedInput schema / properties / countries

Added value: +{
+  "description": "Headquarters country codes (ISO alpha-2, OR). Pass \"unknown\" to include companies with no country on file.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / country

Removed value: -{
-  "description": "Headquarters country code (ISO alpha-2).",
-  "type": "string"
-}

removedInput schema / properties / employeeCountBucket

Removed value: -{
-  "description": "LinkedIn employee count bucket, e.g. 51-200.",
-  "type": "string"
-}

addedInput schema / properties / employeeCountBuckets

Added value: +{
+  "description": "LinkedIn employee count buckets (OR), e.g. 51-200. Pass \"unknown\" for no headcount.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / industryGroup

Removed value: -{
-  "description": "Company industry group.",
-  "type": "string"
-}

addedInput schema / properties / industryGroups

Added value: +{
+  "description": "Company industry groups (OR). Matched literally against the LinkedIn labels. Pass \"unknown\" for companies with no industry on file.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changedexec_moves2 fields changed

addedInput schema / properties / countries

Added value: +{
+  "description": "Headquarters country codes (ISO alpha-2, OR). Pass \"unknown\" to include companies with no country on file.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / until / description

Previous value: -"Return events announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp."New value: +"Return records announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp."

Changedfunding_events6 fields changed

addedInput schema / properties / countries

Added value: +{
+  "description": "Headquarters country codes (ISO alpha-2, OR). Pass \"unknown\" to include companies with no country on file.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / country

Removed value: -{
-  "description": "Company headquarters country code (ISO alpha-2).",
-  "type": "string"
-}

addedInput schema / properties / employeeBuckets

Added value: +{
+  "description": "Company employee-count buckets (OR). Canonical values: 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+.",
+  "items": {
+    "enum": [
+      "1-10",
+      "11-50",
+      "51-200",
+      "201-500",
+      "501-1000",
+      "1001-5000",
+      "5001-10000",
+      "10001+",
+      "unknown"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / industryGroup

Removed value: -{
-  "description": "Company industry group.",
-  "type": "string"
-}

addedInput schema / properties / industryGroups

Added value: +{
+  "description": "Company industry groups (OR). Matched literally against the LinkedIn labels. Pass \"unknown\" for companies with no industry on file.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / until

Added value: +{
+  "description": "Return records announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp.",
+  "type": "string"
+}

Changedinvestors3 fields changed

addedInput schema / properties / countries

Added value: +{
+  "description": "Headquarters country codes (ISO alpha-2, OR). Pass \"unknown\" to include companies with no country on file.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / country

Removed value: -{
-  "description": "Headquarters country code (ISO alpha-2).",
-  "type": "string"
-}

addedInput schema / properties / hasFirmographics

Added value: +{
+  "description": "Only investors whose domain and type we have resolved.",
+  "type": "boolean"
+}

4 tool updatesAug 20, 2026

Changedacquisitions1 field changed

addedInput schema / properties / naicsCode

Added value: +{
+  "description": "NAICS 2022 code for the target (acquired) company. Matches the code and everything beneath it, so \"51\" also returns 5132 and 5173. Sector ranges work: \"31-33\" returns all manufacturing.",
+  "enum": [
+    "11",
+    "21",
+    "22",
+    "23",
+    "42",
+    "51",
+    "52",
+    "53",
+    "54",
+    "56",
+    "71",
+    "81",
+    "92",
+    "111",
+    "113",
+    "114",
+    "212",
+    "236",
+    "238",
+    "311",
+    "313",
+    "315",
+    "316",
+    "321",
+    "322",
+    "323",
+    "325",
+    "327",
+    "331",
+    "332",
+    "335",
+    "336",
+    "337",
+    "458",
+    "482",
+    "483",
+    "484",
+    "485",
+    "493",
+    "519",
+    "532",
+    "562",
+    "611",
+    "621",
+    "622",
+    "623",
+    "712",
+    "721",
+    "722",
+    "811",
+    "812",
+    "813",
+    "1114",
+    "2111",
+    "2211",
+    "2213",
+    "2361",
+    "2382",
+    "3111",
+    "3115",
+    "3116",
+    "3117",
+    "3118",
+    "3121",
+    "3122",
+    "3162",
+    "3222",
+    "3253",
+    "3254",
+    "3255",
+    "3256",
+    "3261",
+    "3272",
+    "3323",
+    "3325",
+    "3328",
+    "3331",
+    "3332",
+    "3334",
+    "3341",
+    "3342",
+    "3343",
+    "3344",
+    "3345",
+    "3351",
+    "3352",
+    "3353",
+    "3359",
+    "3361",
+    "3363",
+    "3364",
+    "3365",
+    "3366",
+    "3372",
+    "3391",
+    "3399",
+    "4231",
+    "4233",
+    "4234",
+    "4235",
+    "4236",
+    "4238",
+    "4244",
+    "4245",
+    "4246",
+    "4247",
+    "4248",
+    "4411",
+    "4441",
+    "4451",
+    "4491",
+    "4561",
+    "4571",
+    "4591",
+    "4593",
+    "4811",
+    "4851",
+    "4853",
+    "4921",
+    "5121",
+    "5122",
+    "5131",
+    "5132",
+    "5161",
+    "5162",
+    "5173",
+    "5192",
+    "5221",
+    "5231",
+    "5239",
+    "5241",
+    "5242",
+    "5311",
+    "5312",
+    "5322",
+    "5411",
+    "5412",
+    "5413",
+    "5414",
+    "5415",
+    "5416",
+    "5417",
+    "5418",
+    "5419",
+    "5511",
+    "5613",
+    "5614",
+    "5615",
+    "5616",
+    "5617",
+    "5621",
+    "6111",
+    "6113",
+    "6114",
+    "6115",
+    "6213",
+    "6214",
+    "6215",
+    "6216",
+    "6241",
+    "6242",
+    "6244",
+    "7111",
+    "7112",
+    "7115",
+    "7132",
+    "7139",
+    "7225",
+    "8111",
+    "8121",
+    "8123",
+    "8129",
+    "8131",
+    "8132",
+    "8134",
+    "8139",
+    "9211",
+    "9221",
+    "9281",
+    "unknown",
+    "31-33",
+    "44-45",
+    "48-49"
+  ],
+  "type": "string"
+}

Changedcompanies1 field changed

addedInput schema / properties / naicsCode / enum

Added value: +[
+  "11",
+  "21",
+  "22",
+  "23",
+  "42",
+  "51",
+  "52",
+  "53",
+  "54",
+  "56",
+  "71",
+  "81",
+  "92",
+  "111",
+  "113",
+  "114",
+  "212",
+  "236",
+  "238",
+  "311",
+  "313",
+  "315",
+  "316",
+  "321",
+  "322",
+  "323",
+  "325",
+  "327",
+  "331",
+  "332",
+  "335",
+  "336",
+  "337",
+  "458",
+  "482",
+  "483",
+  "484",
+  "485",
+  "493",
+  "519",
+  "532",
+  "562",
+  "611",
+  "621",
+  "622",
+  "623",
+  "712",
+  "721",
+  "722",
+  "811",
+  "812",
+  "813",
+  "1114",
+  "2111",
+  "2211",
+  "2213",
+  "2361",
+  "2382",
+  "3111",
+  "3115",
+  "3116",
+  "3117",
+  "3118",
+  "3121",
+  "3122",
+  "3162",
+  "3222",
+  "3253",
+  "3254",
+  "3255",
+  "3256",
+  "3261",
+  "3272",
+  "3323",
+  "3325",
+  "3328",
+  "3331",
+  "3332",
+  "3334",
+  "3341",
+  "3342",
+  "3343",
+  "3344",
+  "3345",
+  "3351",
+  "3352",
+  "3353",
+  "3359",
+  "3361",
+  "3363",
+  "3364",
+  "3365",
+  "3366",
+  "3372",
+  "3391",
+  "3399",
+  "4231",
+  "4233",
+  "4234",
+  "4235",
+  "4236",
+  "4238",
+  "4244",
+  "4245",
+  "4246",
+  "4247",
+  "4248",
+  "4411",
+  "4441",
+  "4451",
+  "4491",
+  "4561",
+  "4571",
+  "4591",
+  "4593",
+  "4811",
+  "4851",
+  "4853",
+  "4921",
+  "5121",
+  "5122",
+  "5131",
+  "5132",
+  "5161",
+  "5162",
+  "5173",
+  "5192",
+  "5221",
+  "5231",
+  "5239",
+  "5241",
+  "5242",
+  "5311",
+  "5312",
+  "5322",
+  "5411",
+  "5412",
+  "5413",
+  "5414",
+  "5415",
+  "5416",
+  "5417",
+  "5418",
+  "5419",
+  "5511",
+  "5613",
+  "5614",
+  "5615",
+  "5616",
+  "5617",
+  "5621",
+  "6111",
+  "6113",
+  "6114",
+  "6115",
+  "6213",
+  "6214",
+  "6215",
+  "6216",
+  "6241",
+  "6242",
+  "6244",
+  "7111",
+  "7112",
+  "7115",
+  "7132",
+  "7139",
+  "7225",
+  "8111",
+  "8121",
+  "8123",
+  "8129",
+  "8131",
+  "8132",
+  "8134",
+  "8139",
+  "9211",
+  "9221",
+  "9281",
+  "unknown",
+  "31-33",
+  "44-45",
+  "48-49"
+]

Changedexec_moves1 field changed

addedInput schema / properties / naicsCode

Added value: +{
+  "description": "NAICS 2022 code for the company. Matches the code and everything beneath it, so \"51\" also returns 5132 and 5173. Sector ranges work: \"31-33\" returns all manufacturing.",
+  "enum": [
+    "11",
+    "21",
+    "22",
+    "23",
+    "42",
+    "51",
+    "52",
+    "53",
+    "54",
+    "56",
+    "71",
+    "81",
+    "92",
+    "111",
+    "113",
+    "114",
+    "212",
+    "236",
+    "238",
+    "311",
+    "313",
+    "315",
+    "316",
+    "321",
+    "322",
+    "323",
+    "325",
+    "327",
+    "331",
+    "332",
+    "335",
+    "336",
+    "337",
+    "458",
+    "482",
+    "483",
+    "484",
+    "485",
+    "493",
+    "519",
+    "532",
+    "562",
+    "611",
+    "621",
+    "622",
+    "623",
+    "712",
+    "721",
+    "722",
+    "811",
+    "812",
+    "813",
+    "1114",
+    "2111",
+    "2211",
+    "2213",
+    "2361",
+    "2382",
+    "3111",
+    "3115",
+    "3116",
+    "3117",
+    "3118",
+    "3121",
+    "3122",
+    "3162",
+    "3222",
+    "3253",
+    "3254",
+    "3255",
+    "3256",
+    "3261",
+    "3272",
+    "3323",
+    "3325",
+    "3328",
+    "3331",
+    "3332",
+    "3334",
+    "3341",
+    "3342",
+    "3343",
+    "3344",
+    "3345",
+    "3351",
+    "3352",
+    "3353",
+    "3359",
+    "3361",
+    "3363",
+    "3364",
+    "3365",
+    "3366",
+    "3372",
+    "3391",
+    "3399",
+    "4231",
+    "4233",
+    "4234",
+    "4235",
+    "4236",
+    "4238",
+    "4244",
+    "4245",
+    "4246",
+    "4247",
+    "4248",
+    "4411",
+    "4441",
+    "4451",
+    "4491",
+    "4561",
+    "4571",
+    "4591",
+    "4593",
+    "4811",
+    "4851",
+    "4853",
+    "4921",
+    "5121",
+    "5122",
+    "5131",
+    "5132",
+    "5161",
+    "5162",
+    "5173",
+    "5192",
+    "5221",
+    "5231",
+    "5239",
+    "5241",
+    "5242",
+    "5311",
+    "5312",
+    "5322",
+    "5411",
+    "5412",
+    "5413",
+    "5414",
+    "5415",
+    "5416",
+    "5417",
+    "5418",
+    "5419",
+    "5511",
+    "5613",
+    "5614",
+    "5615",
+    "5616",
+    "5617",
+    "5621",
+    "6111",
+    "6113",
+    "6114",
+    "6115",
+    "6213",
+    "6214",
+    "6215",
+    "6216",
+    "6241",
+    "6242",
+    "6244",
+    "7111",
+    "7112",
+    "7115",
+    "7132",
+    "7139",
+    "7225",
+    "8111",
+    "8121",
+    "8123",
+    "8129",
+    "8131",
+    "8132",
+    "8134",
+    "8139",
+    "9211",
+    "9221",
+    "9281",
+    "unknown",
+    "31-33",
+    "44-45",
+    "48-49"
+  ],
+  "type": "string"
+}

Changedfunding_events1 field changed

addedInput schema / properties / naicsCode

Added value: +{
+  "description": "NAICS 2022 code for the company. Matches the code and everything beneath it, so \"51\" also returns 5132 and 5173. Sector ranges work: \"31-33\" returns all manufacturing.",
+  "enum": [
+    "11",
+    "21",
+    "22",
+    "23",
+    "42",
+    "51",
+    "52",
+    "53",
+    "54",
+    "56",
+    "71",
+    "81",
+    "92",
+    "111",
+    "113",
+    "114",
+    "212",
+    "236",
+    "238",
+    "311",
+    "313",
+    "315",
+    "316",
+    "321",
+    "322",
+    "323",
+    "325",
+    "327",
+    "331",
+    "332",
+    "335",
+    "336",
+    "337",
+    "458",
+    "482",
+    "483",
+    "484",
+    "485",
+    "493",
+    "519",
+    "532",
+    "562",
+    "611",
+    "621",
+    "622",
+    "623",
+    "712",
+    "721",
+    "722",
+    "811",
+    "812",
+    "813",
+    "1114",
+    "2111",
+    "2211",
+    "2213",
+    "2361",
+    "2382",
+    "3111",
+    "3115",
+    "3116",
+    "3117",
+    "3118",
+    "3121",
+    "3122",
+    "3162",
+    "3222",
+    "3253",
+    "3254",
+    "3255",
+    "3256",
+    "3261",
+    "3272",
+    "3323",
+    "3325",
+    "3328",
+    "3331",
+    "3332",
+    "3334",
+    "3341",
+    "3342",
+    "3343",
+    "3344",
+    "3345",
+    "3351",
+    "3352",
+    "3353",
+    "3359",
+    "3361",
+    "3363",
+    "3364",
+    "3365",
+    "3366",
+    "3372",
+    "3391",
+    "3399",
+    "4231",
+    "4233",
+    "4234",
+    "4235",
+    "4236",
+    "4238",
+    "4244",
+    "4245",
+    "4246",
+    "4247",
+    "4248",
+    "4411",
+    "4441",
+    "4451",
+    "4491",
+    "4561",
+    "4571",
+    "4591",
+    "4593",
+    "4811",
+    "4851",
+    "4853",
+    "4921",
+    "5121",
+    "5122",
+    "5131",
+    "5132",
+    "5161",
+    "5162",
+    "5173",
+    "5192",
+    "5221",
+    "5231",
+    "5239",
+    "5241",
+    "5242",
+    "5311",
+    "5312",
+    "5322",
+    "5411",
+    "5412",
+    "5413",
+    "5414",
+    "5415",
+    "5416",
+    "5417",
+    "5418",
+    "5419",
+    "5511",
+    "5613",
+    "5614",
+    "5615",
+    "5616",
+    "5617",
+    "5621",
+    "6111",
+    "6113",
+    "6114",
+    "6115",
+    "6213",
+    "6214",
+    "6215",
+    "6216",
+    "6241",
+    "6242",
+    "6244",
+    "7111",
+    "7112",
+    "7115",
+    "7132",
+    "7139",
+    "7225",
+    "8111",
+    "8121",
+    "8123",
+    "8129",
+    "8131",
+    "8132",
+    "8134",
+    "8139",
+    "9211",
+    "9221",
+    "9281",
+    "unknown",
+    "31-33",
+    "44-45",
+    "48-49"
+  ],
+  "type": "string"
+}

4 tool updatesAug 20, 2026

Changedacquisitions1 field changed
- addedInput schema / properties / paymentType / items / enum
```
Added value: +[
+  "cash",
+  "stock",
+  "mixed",
+  "undisclosed"
+]
```

Changedcompanies1 field changed

addedInput schema / properties / naicsCode

Added value: +{
+  "description": "NAICS 2022 code. Matches the code and everything beneath it, so \"51\" also returns 5132 and 5173. Sector ranges work: \"31-33\" returns all manufacturing. Pass \"unknown\" for unclassified companies.",
+  "type": "string"
+}

Changedexec_moves2 fields changed

addedInput schema / properties / moveType / items / enum

Added value: +[
+  "appointment",
+  "promotion",
+  "departure",
+  "transition"
+]

addedInput schema / properties / roleSeniority / items / enum

Added value: +[
+  "c_level",
+  "vp_level",
+  "founder"
+]

Changedfunding_events1 field changed

addedInput schema / properties / round / items / enum

Added value: +[
+  "pre-seed",
+  "seed",
+  "angel",
+  "series-a",
+  "series-b",
+  "series-c",
+  "series-d",
+  "series-e",
+  "series-f",
+  "series-g",
+  "series-h",
+  "series-i",
+  "growth",
+  "extension",
+  "bridge",
+  "convertible",
+  "safe",
+  "debt",
+  "grant",
+  "pre-ipo",
+  "secondary",
+  "pipe",
+  "other",
+  "unknown"
+]

2 tool updatesAug 9, 2026

Changedacquisitions1 field changed

changedInput schema / properties / verticals / description

Previous value: -"Target company sector filters (OR). Canonical values: ai, fintech, saas, devtools, healthcare, climate, robotics, cybersecurity, logistics, commerce, data, crypto."New value: +"Target company sector filters (OR). Canonical values: ai, fintech, saas, devtools, healthcare, climate, robotics, cybersecurity, logistics, commerce, data, crypto, media, education, marketing, telecom, realestate, hardware, gaming, space."

Changedfunding_events1 field changed

changedInput schema / properties / verticals / description

Previous value: -"High-level sector filters (OR). Canonical values: ai, fintech, saas, devtools, healthcare, climate, robotics, cybersecurity, logistics, commerce, data, crypto."New value: +"High-level sector filters (OR). Canonical values: ai, fintech, saas, devtools, healthcare, climate, robotics, cybersecurity, logistics, commerce, data, crypto, media, education, marketing, telecom, realestate, hardware, gaming, space."

3 tool updatesJul 27, 2026

Changedacquisitions1 field changed

changedInput schema / properties / since / description

Previous value: -"Return records discovered/announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."New value: +"Return records announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."

Changedexec_moves2 fields changed

changedInput schema / properties / since / description

Previous value: -"Return records discovered/announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."New value: +"Return records announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."

changedInput schema / properties / until / description

Previous value: -"Return events discovered/announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp."New value: +"Return events announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp."

Changedfunding_events1 field changed

changedInput schema / properties / since / description

Previous value: -"Return records discovered/announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."New value: +"Return records announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."

5 tool updatesJul 25, 2026
- Addedadd_to_watchlist
- Addedcreate_watchlist
- Addedget_watchlist
- Addedlist_watchlists
- Addedremove_from_watchlist
1 tool updateJul 24, 2026
- Addedcompany_timeline

2 tool updatesJul 24, 2026

Changedacquisitions1 field changed

addedInput schema / properties / verticals

Added value: +{
+  "description": "Target company sector filters (OR). Canonical values: ai, fintech, saas, devtools, healthcare, climate, robotics, cybersecurity, logistics, commerce, data, crypto.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changedfunding_events1 field changed

addedInput schema / properties / verticals

Added value: +{
+  "description": "High-level sector filters (OR). Canonical values: ai, fintech, saas, devtools, healthcare, climate, robotics, cybersecurity, logistics, commerce, data, crypto.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

5 tool updatesJul 4, 2026

Changedacquisitions1 field changed

changedInput schema / properties / since / description

Previous value: -"Return records discovered/announced after this ISO-8601 timestamp."New value: +"Return records discovered/announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."

Changedcompanies1 field changed

changedInput schema / properties / since / description

Previous value: -"Return companies created/updated after this ISO-8601 timestamp."New value: +"Return companies created/updated on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."

Changedexec_moves2 fields changed

changedInput schema / properties / since / description

Previous value: -"Return records discovered/announced after this ISO-8601 timestamp."New value: +"Return records discovered/announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."

changedInput schema / properties / until / description

Previous value: -"Return events discovered/announced before this ISO-8601 timestamp."New value: +"Return events discovered/announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp."

Changedfunding_events1 field changed

changedInput schema / properties / since / description

Previous value: -"Return records discovered/announced after this ISO-8601 timestamp."New value: +"Return records discovered/announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."

Changedinvestors1 field changed

changedInput schema / properties / since / description

Previous value: -"Return investors created/updated after this ISO-8601 timestamp."New value: +"Return investors created/updated on or after this date (YYYY-MM-DD) or ISO-8601 timestamp."

1 tool updateJul 1, 2026

Changedfunding_events1 field changed

changedInput schema / properties / round / description

Previous value: -"Funding round filters. Canonical values: pre-seed, seed, angel, series-a, series-b, series-c, series-d, series-e, series-f, growth, extension, bridge, convertible, safe, debt, grant, pre-ipo, secondary, pipe, other."New value: +"Funding round filters. Canonical values: pre-seed, seed, angel, series-a, series-b, series-c, series-d, series-e, series-f, series-g, series-h, series-i, growth, extension, bridge, convertible, safe, debt, grant, pre-ipo, secondary, pipe, other."

5 tool updatesJun 28, 2026
- First observedacquisitions
- First observedcompanies
- First observedexec_moves
- First observedfunding_events
- First observedinvestors

Related MCP Connectors

BounceWatch Signal Intelligence AOAuth
com.bouncewatch
Millions of dated buying and momentum signals: who raised, who's hiring, what changed and when
Customer Data Platforms Data Platforms Research & Data
1
Wokelo MCP Server
io.github.Wokelo-AI
Company and market intelligence, news, enrichment, and agentic workflows for dealmakers.
Finance Research & Data Agent Orchestration
2
akta.pro MCPOAuth
io.github.akta-pro
Private company data, entity-resolved news, targeted lists, and alternative signals for AI agents.
Finance Research & Data
1
IT桔子 MCP A
io.github.lgyers
Hosted MCP for IT桔子 primary market company, funding, investor and sector data.
Finance Research & Data
212

Related MCP Servers

ChangeSignal
Research & Data Documentation Access Search
timkeeeeeen
F
license
Not graded
quality
B
maintenance
Enables querying and analyzing changes in technology company documentation through MCP tools, including change feeds, company info, and evidence-based messaging.
Updated 2 months ago (2026-07-29 19:45 UTC)
-
Funding & Press Signal Scanner
Finance Research & Data Web Scraping
mambalabsdev
A
license
A
quality
A
maintenance
Scans public news and press for a company's funding rounds, executive moves, product launches, acquisitions, partnerships, and IPOs, returning deduplicated events in flat JSON.
Updated 7 days ago (2026-09-20 20:42 UTC)
1
49 npm
MIT
DoableClaw Research
Research & Data Autonomous Agents
ikshan-ai
F
license
Not graded
quality
B
maintenance
AI research on companies and industries — one MCP tool per research domain.
Updated 2 months ago (2026-08-12 07:36 UTC)
-
Frontier Deal Screener
Finance Research & Data
khorovitz
F
license
Not graded
quality
C
maintenance
Enables evaluating quantum and deep-tech startups by providing access to a curated dataset, company profiles with computed ratings, and a configurable deal-scoring rubric through MCP tools.
Updated a month ago (2026-08-30 21:53 UTC)
-

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?