iposignal

IPO snapshot (premium)

get_ipo_snapshot

Read-only

Retrieve a complete IPO company profile — deal terms, pricing range, expected market cap, SEC registration and prospectus details, offering structure, lifecycle timeline, and IBKR indicative borrow fee rate when available. When available, includes AI-generated research with valuation models, competitor benchmarking, underwriter ratings, board analysis, and risk factors. Provide exactly one of companyId, symbol, or cik. PREMIUM: paid per call over x402 (USDC on Base); an unpaid call returns the payment terms, and a not-found is never charged. Same data and price as the HTTP endpoint /api/agent/ipo/{id} or /api/agent/ipo/by-symbol/{symbol}.

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, with or without leading zeros, e.g. 1876042 or 0001876042.
`symbol`	No	US ticker symbol, e.g. CRCL. Case-insensitive. Tickers get reassigned, so a response may carry a symbolNote.
`companyId`	No	IPOSignal company id (24-character hex), as returned by other IPOSignal responses.

Output Schema

TableJSON Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, 10 digits.
`sec`	No	SEC company data.
`venue`	No	Listing exchange.
`symbol`	No	Ticker.
`company`	No	Registrant name.
`offering`	No	Offering structure from the prospectus; termsAreFinal is true only for a final 424B* prospectus.
`research`	No	AI-generated research: valuation models, competitors, underwriters, board, risks. Figures are sourced from filings.
`borrowFee`	No	Latest IBKR indicative borrow fee (annualized %), when available.
`updatedAt`	No	ISO timestamp of the last update to this record.
`ipoDetails`	No	Deal facts: date, exchange, shares offered, priceRange, offerPrice (final terms only), marketCap (post-IPO economic shares × offer price), offerSize (gross proceeds), and the source of each.
`symbolNote`	No	Present only when the requested ticker is contested: which registrant it belongs to now vs. the record served.
`registration`	No	SEC registration statement: form type and filing URL.
`freedom24News`	No	Freedom24 articles about the deal.
`lifecycleEvents`	No	Dated status history: filed, priced, listed, withdrawn.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "borrowFee": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Latest IBKR indicative borrow fee (annualized %), when available."
+    },
+    "cik": {
+      "description": "SEC Central Index Key, 10 digits.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "company": {
+      "description": "Registrant name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "freedom24News": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Freedom24 articles about the deal."
+    },
+    "ipoDetails": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Deal facts: date, exchange, shares offered, priceRange, offerPrice (final terms only), marketCap (post-IPO economic shares × offer price), offerSize (gross proceeds), and the source of each."
+    },
+    "lifecycleEvents": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Dated status history: filed, priced, listed, withdrawn."
+    },
+    "offering": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Offering structure from the prospectus; termsAreFinal is true only for a final 424B* prospectus."
+    },
+    "registration": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "SEC registration statement: form type and filing URL."
+    },
+    "research": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "AI-generated research: valuation models, competitors, underwriters, board, risks. Figures are sourced from filings."
+    },
+    "sec": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "SEC company data."
+    },
+    "symbol": {
+      "description": "Ticker.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "symbolNote": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Present only when the requested ticker is contested: which registrant it belongs to now vs. the record served."
+    },
+    "updatedAt": {
+      "description": "ISO timestamp of the last update to this record.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "venue": {
+      "description": "Listing exchange.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedSep 23, 2026

addedInput schema / properties / cik / description

Added value: +"SEC Central Index Key, with or without leading zeros, e.g. 1876042 or 0001876042."

addedInput schema / properties / companyId / description

Added value: +"IPOSignal company id (24-character hex), as returned by other IPOSignal responses."

addedInput schema / properties / symbol / description

Added value: +"US ticker symbol, e.g. CRCL. Case-insensitive. Tickers get reassigned, so a response may carry a symbolNote."

First observedMay 14, 2026

TDQS

A4/5.0

Behavior4/5

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

The readOnlyHint and destructiveHint annotations already establish that this is a safe read operation, and the description adds meaningful behavioral context beyond that: it is a premium paid-per-call tool, unpaid calls return payment terms, not-found lookups are never charged, and it maps to specific HTTP endpoints. No contradiction with annotations is present.

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 dense but front-loaded with the purpose and main content areas before moving to identifier rules and payment terms. The list of profile contents is long, but each item adds meaningful selection-relevant information, and the payment section is concise.

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?

Although the data surface is broad, the presence of an output schema reduces the need to describe return values. The description covers identifier constraints, premium pricing behavior, endpoint equivalence, and the conditional availability of research fields, making the tool reasonably complete for an agent to invoke.

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 descriptions already cover all three parameters fully, giving formats, examples, and the symbolNote caveat. The description adds the material constraint that exactly one of companyId, symbol, or cik must be supplied, which is not reflected in the schema's required fields.

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, 'Retrieve a complete IPO company profile', and enumerates concrete content areas: deal terms, pricing range, prospectus details, lifecycle timeline, and borrow fee. It implicitly distinguishes itself from sibling tools by positioning itself as the comprehensive snapshot rather than a focused events, sentiment, or financials tool.

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 invocation guidance, 'Provide exactly one of companyId, symbol, or cik', but gives no guidance about when to choose this tool over get_ipo_overview, get_ipo_events, or get_company_financials. No alternative or exclusion criteria is mentioned, so the agent is left to infer routing decisions from the description and sibling names alone.

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

All iposignal tools Inspect

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.