Insider Trading Grounding Data
The tool
Ground enterprise agents in verifiable SEC Form 4 data — insider buys, sells and roles — so insider-activity answers cite real filings.
Once your client is connected to the VerveContext MCP server, this appears in its tool list as InsiderTradingGroundingData. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.
{
"name": "InsiderTradingGroundingData",
"arguments": {
"ticker": "AAPL"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about AAPL in the terms this source covers is enough for it to reach for InsiderTradingGroundingData on its own.
Connecting
One server URL covers every source in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp"
}
}
}https://api.vervecontext.com/v1/mcpPer-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.
| Argument | Type | Example | Description |
|---|---|---|---|
tickerRequired | string | AAPL | Stock ticker symbol (e.g. AAPL, MSFT, ADBE) |
typePremium | string | buy | Filter to open-market buys or sells (buy or sell). |
limitPremium | integer | 10 | Number of transactions to return (1-25). Defaults to 5. |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"ticker": "AAPL",
"cik": "0000320193",
"company": "Apple Inc.",
"totalRecentForm4": 512,
"count": 5,
"lastTransactionDate": "2025-10-14",
"daysSinceLastTransaction": 64,
"transactions": [
{
"filingDate": "2025-10-16",
"transactionDate": "2025-10-14",
"insiderName": "COOK TIMOTHY D",
"insiderTitle": "Chief Executive Officer",
"relationship": {
"director": true,
"officer": true,
"tenPercentOwner": false
},
"security": "Common Stock",
"transactionCode": "S",
"transactionType": "Sale",
"direction": "sell",
"acquiredDisposed": "D",
"shares": 511000,
"pricePerShare": 245.5,
"value": 125450500,
"sharesOwnedAfter": 3280000,
"accessionNumber": "0000320193-25-000118",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000118/xslF345X05/wf-form4.xml"
},
{
"filingDate": "2025-10-02",
"transactionDate": "2025-10-01",
"insiderName": "MAESTRI LUCA",
"insiderTitle": "Senior Vice President, CFO",
"relationship": {
"director": false,
"officer": true,
"tenPercentOwner": false
},
"security": "Common Stock",
"transactionCode": "S",
"transactionType": "Sale",
"direction": "sell",
"acquiredDisposed": "D",
"shares": 74213,
"pricePerShare": 241.18,
"value": 17899091,
"sharesOwnedAfter": 112884,
"accessionNumber": "0000320193-25-000112",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000112/xslF345X05/wf-form4.xml"
},
{
"filingDate": "2025-08-20",
"transactionDate": "2025-08-18",
"insiderName": "WILLIAMS JEFFREY E",Fields
| Field | Type | Example | Description |
|---|---|---|---|
ticker | string | Stock ticker symbol for the company | |
cik | string | SEC Central Index Key unique identifier | |
company | string | Official registered name of the company | |
totalRecentForm4 | number | Total Form 4 filings in the company's recent feed | |
count | number | Number of transactions returned in this response | |
lastTransactionDate | string | Date of the most recent insider transaction | |
daysSinceLastTransactionPremium | number | Days since the most recent insider transaction | |
transactions | array[5] | Recent insider transactions, most recent first | |
└ transactions.0.filingDate | string | Date the Form 4 was filed | |
└ transactions.0.transactionDate | string | Date the transaction occurred | |
└ transactions.0.insiderName | string | Name of the reporting insider | |
└ transactions.0.insiderTitle | string | Role or title of the insider | |
└ transactions.0.relationship | object | Insider relationship flags (director, officer, 10% owner) | |
└ transactions.0.relationship.director | boolean | ||
└ transactions.0.relationship.officer | boolean | ||
└ transactions.0.relationship.tenPercentOwner | boolean | ||
└ transactions.0.security | string | Title of the security transacted | |
└ transactions.0.transactionCode | string | SEC transaction code (P, S, A, M, F, ...) | |
└ transactions.0.transactionType | string | Human-readable transaction type | |
└ transactions.0.direction | string | Open-market direction (buy or sell), when applicable | |
└ transactions.0.acquiredDisposed | string | Whether shares were acquired (A) or disposed (D) | |
└ transactions.0.shares | number | Number of shares in the transaction | |
└ transactions.0.pricePerShare | number | Price per share for the transaction | |
└ transactions.0.value | number | Total transaction value (shares x price) | |
└ transactions.0.sharesOwnedAfter | number | Shares owned by the insider after the transaction | |
└ transactions.0.accessionNumber | string | SEC accession number for the filing | |
└ transactions.0.url | string | Direct link to the Form 4 filing | |
summary | object | Derived insider-sentiment summary | |
└ summary.totalTransactionsPremium | number | Transactions in the summarized window | |
└ summary.distinctInsidersPremium | number | Number of distinct insiders transacting | |
└ summary.buysPremium | object | Open-market buy totals (count, shares, value) | |
└ summary.buys.countPremium | number | Number of transactions returned in this response | |
└ summary.buys.sharesPremium | number | ||
└ summary.buys.valuePremium | number | ||
└ summary.sellsPremium | object | Open-market sell totals (count, shares, value) | |
└ summary.sells.countPremium | number | Number of transactions returned in this response | |
└ summary.sells.sharesPremium | number | ||
└ summary.sells.valuePremium | number | ||
└ summary.netSharesPremium | number | Net shares bought minus sold (open-market) | |
└ summary.netValuePremium | number | Net dollar value bought minus sold (open-market) | |
└ summary.buySellRatioPremium | number | Ratio of buy value to sell value | |
└ summary.sentimentPremium | string | Insider sentiment read (Bullish, Bearish, Neutral) | |
└ summary.clusterBuyPremium | boolean | Whether multiple insiders bought in the window |
Why ground on it
A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value with a shape you can check, which is the difference between an answer you can cite and one you have to hedge.
Point an evaluation at cik: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.
Failure modes
Errors come back as tool errors with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This source isn't part of VerveContext. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
Other ways to use Insider Trading Grounding Data
Set up Insider Trading Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.
Frequently asked questions
Do I have to tell the agent to use InsiderTradingGroundingData?
No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.
Does connecting the server expose every tool at once?
Yes — one connection lists the whole VerveContext catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.
What does a call cost?
1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.
Is there a REST version of this?
Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.