IPOGrid IPO Calendar & Filing Research
Server Details
IPO calendar, SEC filings, deal terms, and IPO news research via the IPOGrid MCP server.
- Status
- Healthy
- Uptime
- 100.0% over 39 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 4 tools
Each tool targets a distinct function: charts, company details, company discovery, and news. No overlap in purpose.
All tool names follow a consistent verb_noun pattern with 'get' for retrieval and 'list' for discovery.
Four tools cover the core IPO research workflow without being excessive or insufficient.
Covers company discovery, details, charts, and news. Missing a dedicated IPO calendar tool, but existing tools handle date ranges and filters.
Available Tools
4 toolsget_chartGet ChartARead-onlyIdempotentInspect
Build an aggregated IPO chart and return its data plus canonical embed, page, and API URLs. Use this instead of hand-building chart URLs. Anonymous requests are quota-limited and may clamp a 52-week range to 26 weeks or a daily bucket to weekly unless the explicit date window is at most 31 days.
| Name | Required | Description | Default |
|---|---|---|---|
| group | No | Dimension used to split chart series. Defaults to sector for proceeds/returns and form_family for filing counts. | |
| range | No | Trailing window when explicit dates are omitted. Defaults to 26w; anonymous 52w requests are clamped to 26w. | |
| scope | No | Include all matching records or only active offerings. Defaults to active. | |
| bucket | No | Time interval. Defaults to week; anonymous daily requests require an explicit window of at most 31 days or are clamped to week. | |
| issuer | No | Include every issuer or exclude SPACs. Defaults to all. | |
| metric | No | Value to aggregate. Defaults to gross_proceeds. | |
| date_to | No | Inclusive YYYY-MM-DD upper bound. Use with date_from for a custom window instead of range. | |
| date_from | No | Inclusive YYYY-MM-DD lower bound. Use with date_to for a custom window instead of range. | |
| materiality | No | Include all filing forms or only major IPO forms. Defaults to all. |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | |
| links | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by disclosing quota limits and clamping behavior for anonymous requests, which are not captured by annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no fluff. The first sentence states core purpose and output, the second provides important usage guidance and limitations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 9 optional parameters and an output schema, the description covers the tool's purpose, output, and key behavioral notes. It could mention default parameter behaviors briefly, but overall it's sufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already fully describes each parameter. The description does not add parameter-level details beyond schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it builds an aggregated IPO chart and returns data plus URLs, using specific verbs and resource. It distinguishes itself from sibling tools (get_company, list_companies, list_news) by focusing on chart generation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly recommends using this tool instead of hand-building chart URLs, and notes anonymous request limitations. While it doesn't exclude alternative tools among siblings, the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_companyGet CompanyARead-onlyIdempotentInspect
Fetch one issuer by SEC CIK after discovery with list_companies. Optional enrichments add terms and research context; anonymous requests allow only latest_terms, classification, and news.
| Name | Required | Description | Default |
|---|---|---|---|
| cik | Yes | SEC Central Index Key, with or without leading zeroes (for example 1907085 or 0001907085). | |
| include | No | Optional detail sections. Authenticated lockup_schedule includes normalized holder classes, numeric tranche quantities, resolved dates, anchors and offsets, exceptions, conditions, and evidence. Anonymous requests silently omit consensus, financial_snapshot, filings, comps, and lockup_schedule. |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | Issuer detail with the requested and permitted enrichment sections. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, destructiveHint false. The description adds significant behavioral detail: it explains that optional enrichments add terms and research context, and that anonymous requests are limited to certain sections. This is valuable beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the primary action, and every sentence provides essential information without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and detailed annotations, the description covers the key behavioral aspects: auth-dependent behavior, prerequisite, and optional enrichments. It is sufficiently complete for an AI agent to understand when and how to use the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already describes both parameters (cik and include) with clear descriptions. The description adds context by explaining that include sections are optional and that anonymous requests silently omit some sections. This adds meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches one issuer by SEC CIK, includes a prerequisite (after discovery with list_companies), and distinguishes from sibling tools like list_companies that list multiple issuers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context for use: it's used after discovery with list_companies. It also explains the difference between anonymous and authenticated requests regarding enrichments. However, it does not explicitly list alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_companiesList CompaniesARead-onlyIdempotentInspect
Discover IPOGrid companies and active deals with cursor pagination and market, issuer-kind, freshness, or proceeds filters. Use get_company after selecting an issuer. Anonymous requests return at most 10 rows and omit consensus enrichment.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Return only these issuer kinds. Omit to include every kind. | |
| limit | No | Maximum rows to return. Defaults to 50 when authenticated; anonymous requests are capped at 10. | |
| scope | No | Filter to IPO-only rows or all active deal rows. | |
| cursor | No | Opaque next_cursor from a previous response. Omit for the first page. | |
| market | No | Filter by normalized market family. | |
| include | No | Optional enrichments for each row. Anonymous requests silently omit consensus. | |
| updated_since | No | ISO-8601 lower bound on the company update timestamp. | |
| gross_proceeds_gt | No | Lower bound on gross proceeds, using stated gross proceeds or a midpoint estimate from price range times shares offered. | |
| gross_proceeds_lt | No | Upper bound on gross proceeds, using stated gross proceeds or a midpoint estimate from price range times shares offered. |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | Rows for the current page. |
| meta | Yes | |
| has_more | Yes | Whether another page is available. |
| next_cursor | Yes | Opaque cursor for the next page, or null when this is the last page. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, etc. Description adds context on anonymous request caps (10 rows) and omission of consensus enrichment, and mentions cursor pagination. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: first covers purpose and filters, second guides usage and anonymous limits. No fluff, front-loaded with key info.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex tool with 9 parameters and output schema, the description covers purpose, pagination, filtering, and sibling guidance. Omits return format details, but output schema covers that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with detailed parameter descriptions. The description summarizes filter categories (market, issuer-kind, freshness, proceeds) but does not add new meaning beyond the schema; baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Discover' and resource 'IPOGrid companies and active deals', and distinguishes from sibling tool 'get_company' by stating 'Use get_company after selecting an issuer.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises using get_company for a specific company after listing, but does not address when to use alternatives like get_chart or list_news. Also mentions anonymous request limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_newsList NewsARead-onlyIdempotentInspect
List recent IPO-company news, optionally filtered by SEC CIK. Use this for a news feed; use get_company with news for broader issuer context. Anonymous requests return at most 10 rows and omit full content.
| Name | Required | Description | Default |
|---|---|---|---|
| cik | No | Optional SEC CIK filter, with or without leading zeroes. | |
| limit | No | Maximum rows to return. Defaults to 50 when authenticated; anonymous requests are capped at 10. | |
| cursor | No | Opaque next_cursor from a previous response. Omit for the first page. | |
| include | No | Set to ["content"] for stored article body text. Anonymous requests omit content. |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | Rows for the current page. |
| meta | Yes | |
| has_more | Yes | Whether another page is available. |
| next_cursor | Yes | Opaque cursor for the next page, or null when this is the last page. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses anonymous behavior (capped at 10 rows, no content) beyond annotations. Annotations already mark it as read-only, idempotent, and non-destructive, so no contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short, front-loaded sentences covering purpose, usage guidance, and a behavioral quirk. No fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers main behavior, filtering, pagination (cursor), and authentication differences. Output schema exists so return values are not needed. Could mention time range for 'recent', but overall complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. Description adds little beyond what schema already provides (e.g., 'optionally filtered by SEC CIK' is redundant). Does not enhance parameter understanding significantly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'List recent IPO-company news' with optional CIK filter. Explicitly distinguishes from sibling tools (get_company) by advising to use it for broader issuer context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides when-to-use ('for a news feed') and when-not-to-use ('use get_company with news for broader issuer context'). Also notes anonymous request limitations (10 rows, no content).
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 update
- Changed
get_company2 fields changed- changed
Input schema / properties / include / descriptionPrevious value: -"Optional detail sections. Anonymous requests silently omit consensus, financial_snapshot, filings, comps, and lockup_schedule."New value: +"Optional detail sections. Authenticated lockup_schedule includes normalized holder classes, numeric tranche quantities, resolved dates, anchors and offsets, exceptions, conditions, and evidence. Anonymous requests silently omit consensus, financial_snapshot, filings, comps, and lockup_schedule." - added
Output schema / properties / data / propertiesAdded value: +{ + "lockupSchedule": { + "anyOf": [ + { + "additionalProperties": false, + "description": "Complete normalized offering-document lockup terms: ownership classes, numeric quantities, exact or estimated release dates, anchors and offsets, transfer exceptions, triggers, conditions, and source evidence. Available only through authenticated API and MCP access.", + "properties": { + "aggregatePercentOfOutstanding": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "aggregateSharesSubjectToLockup": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "confidence": { + "default": 0, + "maximum": 1, + "minimum": 0, + "type": "number" + }, + "consentParties": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "earliestMaterialReleaseDate": { + "type": [ + "string", + "null" + ] + }, + "earlyReleaseTriggers": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "evidence": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "exceptions": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "foundAnything": { + "default": false, + "type": "boolean" + }, + "lockedParties": { + "default": [], + "items": { + "type": "string" + }, + "type": "array" + }, + "lockupAgreementsFound": { + "default": null, + "type": [ + "boolean", + "null" + ] + }, + "lockupGroups": { + "default": [], + "items": { + "additionalProperties": false, + "properties": { + "earlyReleaseTriggers": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "evidence": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "exceptions": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "holderClassKey": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "lockupPeriodDays": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "lockupPeriodText": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "ownershipScope": { + "default": "unknown", + "enum": [ + "exclusive_class", + "aggregate", + "subset", + "unknown" + ], + "type": "string" + }, + "parentHolderClassKey": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "partyDescription": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "percentOfOutstanding": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "releaseDate": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "releaseDateText": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "securityDescription": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "sharesSubjectToLockup": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "startAnchor": { + "anyOf": [ + { + "enum": [ + "prospectus_date", + "pricing_date", + "closing_date", + "first_trade_date", + "other", + "unknown" + ], + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "startAnchorDate": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "startAnchorText": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "transferExceptions": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + } + }, + "type": "object" + }, + "type": "array" + }, + "lockupPeriodDays": { + "default": null, + "type": [ + "number", + "null" + ] + }, + "lockupPeriodText": { + "default": null, + "type": [ + "string", + "null" + ] + }, + "ownershipSummary": { + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "excludedAggregateOrSubsetRows": { + "minimum": 0, + "type": "integer" + }, + "reconciliationStatus": { + "enum": [ + "consistent", + "partial", + "conflict", + "unknown" + ], + "type": "string" + }, + "restrictedPercentOfOutstanding": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "restrictedSharesTotal": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "totalSharesOutstandingPostOffering": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + } + }, + "required": [ + "reconciliationStatus", + "excludedAggregateOrSubsetRows" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "default": null + }, + "releaseSchedule": { + "items": { + "additionalProperties": false, + "description": "One normalized release tranche, including quantities, holder linkage, anchor offsets, conditions, and a resolved exact or estimated calendar date.", + "properties": { + "anchorDate": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "anchorEvent": { + "anyOf": [ + { + "enum": [ + "ipo_date", + "prospectus_date", + "pricing_date", + "closing_date", + "first_trade_date", + "business_combination_completion_date", + "offering_sales_commencement_date", + "earnings_release_date", + "explicit_date", + "other", + "unknown" + ], + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "anchorReferenceDate": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "conditions": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "estimatedReleaseDate": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "evidence": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "holderCategories": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "holderClassKey": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "holderClassPercentOfOutstanding": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "holderClassShares": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "isCompleteRelease": { + "default": null, + "type": [ + "boolean", + "null" + ] + }, + "isDateEstimated": { + "type": "boolean" + }, + "materialityBasis": { + "default": "unresolved", + "enum": [ + "percent_of_outstanding", + "share_count", + "complete_holder_class", + "all_restricted_shares", + "all_shareholders", + "unquantified_partial_holder_class", + "unresolved" + ], + "type": "string" + }, + "materialityConfidence": { + "default": "low", + "enum": [ + "high", + "medium", + "low" + ], + "type": "string" + }, + "offsetDays": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "offsetMonths": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "offsetTradingDays": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "quantitySource": { + "default": "unresolved", + "enum": [ + "explicit", + "derived", + "unresolved" + ], + "type": "string" + }, + "releaseDate": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "releaseDateText": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "releasePercentOfHolderClass": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "releasePercentOfOutstanding": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + }, + "releaseScope": { + "default": "unknown", + "enum": [ + "specified_shares", + "issuer_outstanding", + "holder_class", + "all_restricted_shares", + "all_shareholders", + "unknown" + ], + "type": "string" + }, + "releaseTimingText": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "resolvedReleaseDate": { + "type": [ + "string", + "null" + ] + }, + "sharesEligibleForSale": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodDays" + } + }, + "required": [ + "resolvedReleaseDate", + "isDateEstimated" + ], + "type": "object" + }, + "type": "array" + }, + "releasedParties": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "source": { + "additionalProperties": false, + "properties": { + "accessionNumber": { + "type": "string" + }, + "filingDate": { + "type": "string" + }, + "formType": { + "type": "string" + }, + "primaryDocument": { + "type": "string" + }, + "secUrl": { + "format": "uri", + "type": "string" + } + }, + "required": [ + "accessionNumber", + "filingDate", + "formType", + "primaryDocument", + "secUrl" + ], + "type": "object" + }, + "sourceSections": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + }, + "startAnchor": { + "anyOf": [ + { + "enum": [ + "prospectus_date", + "pricing_date", + "closing_date", + "first_trade_date", + "other", + "unknown" + ], + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "startAnchorDate": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "startAnchorText": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockupPeriodText" + }, + "transferExceptions": { + "$ref": "#/properties/data/properties/lockupSchedule/anyOf/0/properties/lockedParties" + } + }, + "required": [ + "releaseSchedule", + "source", + "earliestMaterialReleaseDate" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "Complete normalized offering-document lockup terms: ownership classes, numeric quantities, exact or estimated release dates, anchors and offsets, transfer exceptions, triggers, conditions, and source evidence. Available only through authenticated API and MCP access." + } +}
1 tool update
- Changed
get_company2 fields changed- changed
Input schema / properties / include / descriptionPrevious value: -"Optional detail sections. Anonymous requests silently omit consensus, financial_snapshot, filings, and comps."New value: +"Optional detail sections. Anonymous requests silently omit consensus, financial_snapshot, filings, comps, and lockup_schedule." - changed
Input schema / properties / include / items / enumPrevious value: -[ - "latest_terms", - "classification", - "consensus", - "financial_snapshot", - "filings", - "news", - "comps" -]New value: +[ + "latest_terms", + "classification", + "consensus", + "financial_snapshot", + "filings", + "news", + "comps", + "lockup_schedule" +]
4 tool updates
- Changed
get_chart10 fields changed- added
Input schema / properties / bucket / descriptionAdded value: +"Time interval. Defaults to week; anonymous daily requests require an explicit window of at most 31 days or are clamped to week." - added
Input schema / properties / date_from / descriptionAdded value: +"Inclusive YYYY-MM-DD lower bound. Use with date_to for a custom window instead of range." - added
Input schema / properties / date_to / descriptionAdded value: +"Inclusive YYYY-MM-DD upper bound. Use with date_from for a custom window instead of range." - added
Input schema / properties / group / descriptionAdded value: +"Dimension used to split chart series. Defaults to sector for proceeds/returns and form_family for filing counts." - added
Input schema / properties / issuer / descriptionAdded value: +"Include every issuer or exclude SPACs. Defaults to all." - added
Input schema / properties / materiality / descriptionAdded value: +"Include all filing forms or only major IPO forms. Defaults to all." - added
Input schema / properties / metric / descriptionAdded value: +"Value to aggregate. Defaults to gross_proceeds." - added
Input schema / properties / range / descriptionAdded value: +"Trailing window when explicit dates are omitted. Defaults to 26w; anonymous 52w requests are clamped to 26w." - added
Input schema / properties / scope / descriptionAdded value: +"Include all matching records or only active offerings. Defaults to active." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "data": { + "additionalProperties": false, + "properties": { + "points": { + "items": { + "additionalProperties": false, + "properties": { + "period": { + "description": "Date bucket label.", + "type": "string" + }, + "series": { + "description": "Grouped series label.", + "type": "string" + }, + "value": { + "description": "Aggregated value for this bucket and series.", + "type": "number" + } + }, + "required": [ + "period", + "series", + "value" + ], + "type": "object" + }, + "type": "array" + }, + "spec": { + "additionalProperties": {}, + "description": "Normalized chart filters actually applied to the query.", + "type": "object" + }, + "subtitle": { + "description": "Display subtitle describing the filters.", + "type": "string" + }, + "summary": { + "additionalProperties": false, + "properties": { + "periods": { + "minimum": 0, + "type": "integer" + }, + "series": { + "minimum": 0, + "type": "integer" + }, + "total": { + "description": "Total or average across returned points.", + "type": "number" + } + }, + "required": [ + "total", + "periods", + "series" + ], + "type": "object" + }, + "title": { + "description": "Display title for the chart.", + "type": "string" + }, + "unit": { + "description": "Unit used by point values and summary.total.", + "enum": [ + "count", + "usd", + "percent" + ], + "type": "string" + } + }, + "required": [ + "spec", + "title", + "subtitle", + "unit", + "points", + "summary" + ], + "type": "object" + }, + "links": { + "additionalProperties": false, + "properties": { + "apiUrl": { + "description": "Chart JSON API URL.", + "type": "string" + }, + "embedUrl": { + "description": "Embeddable chart URL.", + "type": "string" + }, + "pageUrl": { + "description": "Public chart page URL.", + "type": "string" + } + }, + "required": [ + "embedUrl", + "pageUrl", + "apiUrl" + ], + "type": "object" + } + }, + "required": [ + "data", + "links" + ], + "type": "object" +}
- Changed
get_company3 fields changed- added
Input schema / properties / cik / descriptionAdded value: +"SEC Central Index Key, with or without leading zeroes (for example 1907085 or 0001907085)." - added
Input schema / properties / include / descriptionAdded value: +"Optional detail sections. Anonymous requests silently omit consensus, financial_snapshot, filings, and comps." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "data": { + "additionalProperties": {}, + "description": "Issuer detail with the requested and permitted enrichment sections.", + "type": "object" + } + }, + "required": [ + "data" + ], + "type": "object" +}
- Changed
list_companies6 fields changed- added
Input schema / properties / cursor / descriptionAdded value: +"Opaque next_cursor from a previous response. Omit for the first page." - changed
Input schema / properties / include / descriptionPrevious value: -"Optional enrichments to include in each company row."New value: +"Optional enrichments for each row. Anonymous requests silently omit consensus." - changed
Input schema / properties / kind / descriptionPrevious value: -"Company kind filter."New value: +"Return only these issuer kinds. Omit to include every kind." - added
Input schema / properties / limit / descriptionAdded value: +"Maximum rows to return. Defaults to 50 when authenticated; anonymous requests are capped at 10." - changed
Input schema / properties / updated_since / descriptionPrevious value: -"ISO-8601 lower bound on companies.updated_at"New value: +"ISO-8601 lower bound on the company update timestamp." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "data": { + "description": "Rows for the current page.", + "items": { + "additionalProperties": {}, + "type": "object" + }, + "type": "array" + }, + "has_more": { + "description": "Whether another page is available.", + "type": "boolean" + }, + "meta": { + "additionalProperties": false, + "properties": { + "count": { + "description": "Number of rows returned in this page.", + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "count" + ], + "type": "object" + }, + "next_cursor": { + "description": "Opaque cursor for the next page, or null when this is the last page.", + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "data", + "next_cursor", + "has_more", + "meta" + ], + "type": "object" +}
- Changed
list_news5 fields changed- added
Input schema / properties / cik / descriptionAdded value: +"Optional SEC CIK filter, with or without leading zeroes." - added
Input schema / properties / cursor / descriptionAdded value: +"Opaque next_cursor from a previous response. Omit for the first page." - added
Input schema / properties / include / descriptionAdded value: +"Set to [\"content\"] for stored article body text. Anonymous requests omit content." - added
Input schema / properties / limit / descriptionAdded value: +"Maximum rows to return. Defaults to 50 when authenticated; anonymous requests are capped at 10." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "data": { + "description": "Rows for the current page.", + "items": { + "additionalProperties": {}, + "type": "object" + }, + "type": "array" + }, + "has_more": { + "description": "Whether another page is available.", + "type": "boolean" + }, + "meta": { + "additionalProperties": false, + "properties": { + "count": { + "description": "Number of rows returned in this page.", + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "count" + ], + "type": "object" + }, + "next_cursor": { + "description": "Opaque cursor for the next page, or null when this is the last page.", + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "data", + "next_cursor", + "has_more", + "meta" + ], + "type": "object" +}
1 tool update
- Changed
get_chart1 field changed- added
Input schema / properties / issuerAdded value: +{ + "enum": [ + "all", + "exclude_spacs" + ], + "type": "string" +}
1 tool update
- Changed
get_chart1 field changed- changed
Input schema / properties / metric / enumPrevious value: -[ - "gross_proceeds", - "prospectus_count", - "final_prospectus_count" -]New value: +[ + "gross_proceeds", + "prospectus_count", + "final_prospectus_count", + "day1_return_pct" +]
1 tool update
- Changed
get_company1 field changed- changed
Input schema / properties / include / items / enumPrevious value: -[ - "latest_terms", - "classification", - "consensus", - "financial_snapshot", - "filings", - "news" -]New value: +[ + "latest_terms", + "classification", + "consensus", + "financial_snapshot", + "filings", + "news", + "comps" +]
4 tool updates
- First observed
get_chart - First observed
get_company - First observed
list_companies - First observed
list_news
Related MCP Connectors
IPO deal terms, SEC filings, AI research and sentiment, plus live valuation metrics for US stocks.
Financial data and research MCP for US/CN/JP equities: filings, statements, ownership, signals.
SEC filings, insider trades, 13F, IPO calendar, macro & FX MCP tools via x402.
Financial data MCP for market, company, news, macro, and US Congress research.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceHosted MCP server that gives AI agents real-time access to SEC EDGAR filings search, 10-K/8-K reading, XBRL financial facts, and insider-trade (Form 4) alerts.27 npm1MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for SEC EDGAR data, providing company search, financial statements, XBRL concepts/frames, filings, Form 4 insider trades, and 13F filings via User-Agent authentication.-
- AlicenseNot gradedqualityBmaintenanceQuery SEC EDGAR filings, XBRL financials, and company data through MCP.376 npm10Apache 2.0

shareseer-mcpofficial
AlicenseNot gradedqualityBmaintenanceShareSeer provides: SEC filings data (10-K, 10-Q, 8-K forms) & related financials Insider trading transaction data per company Largest insider purchases & Sales in a day and week Integration: Remote MCP server (https://shareseer.com/mcp)9MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.