sec-intel-mcp

get_public_company_sec_intel

Read-onlyIdempotent

Resolves all 10,000+ US public stock tickers to SEC CIK numbers, recent 10-K/10-Q/8-K filings, and entity metadata. WHEN TO USE: Call get_public_company_sec_intel when your task requires deterministic sec-intel analysis for ticker; use get_agent_wallet_status to check your remaining free trial quota or prepaid balance. WHEN NOT TO USE: Do not use for unrelated domains or binary media. PARAMETER INTERACTIONS: Pass the target ticker as a non-empty string; omit agent_id and tx_hash during your 5 free trial calls, or supply agent_id (agd_pass_...) / tx_hash for paid execution. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). $0.01 per call. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: get_public_company_sec_intel(ticker='example')

Input Schema

Name	Required	Description
`ticker`	Yes	Public stock ticker symbol (e.g. NVDA, MSFT, AAPL, PLTR).
`tx_hash`	No	Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id.
`agent_id`	No	Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up.

Output Schema

Name	Required	Description
`data`	No	Structured tool output payload.
`status`	Yes	Execution status ('ok' or 'payment_required').
`roi_proof`	No	Token compression and cost-savings verification metrics.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "ticker": "example"
+  }
+]
```

Changed8 schema fields changedOct 18, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / agent_id / description

Previous value: -"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."New value: +"Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up."

addedInput schema / properties / agent_id / maxLength
```
Added value: +256
```
addedInput schema / properties / agent_id / minLength
```
Added value: +1
```

changedInput schema / properties / tx_hash / description

Previous value: -"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."New value: +"Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id."

addedInput schema / properties / tx_hash / maxLength
```
Added value: +256
```
addedInput schema / properties / tx_hash / minLength
```
Added value: +10
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Structured tool output payload.",
+      "type": "object"
+    },
+    "roi_proof": {
+      "description": "Token compression and cost-savings verification metrics.",
+      "type": "object"
+    },
+    "status": {
+      "description": "Execution status ('ok' or 'payment_required').",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 16, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."

changedInput schema / properties / ticker / description

Previous value: -"Public stock ticker symbol (e.g. NVDA, MSFT, AAPL, PLTR)"New value: +"Public stock ticker symbol (e.g. NVDA, MSFT, AAPL, PLTR)."

changedInput schema / properties / tx_hash / description

Previous value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."

Changed3 schema fields changedOct 16, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Optional Agent ID or Session Pass (agd_pass_...)",
+  "type": "string"
+}

addedInput schema / properties / tx_hash

Added value: +{
+  "description": "Optional Base (0x...) or Solana USDC tx hash",
+  "type": "string"
+}

Changed3 schema fields changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / ticker / maxLength
```
Added value: +99999
```
- addedInput schema / properties / ticker / minLength
```
Added value: +1
```

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / ticker / description

Previous value: -"Public stock ticker symbol (e.g. COIN, NVDA, AAPL, MSFT)"New value: +"Public stock ticker symbol (e.g. NVDA, MSFT, AAPL, PLTR)"

First observedOct 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description adds substantial non-obvious behavior: 1-hour caching (<5ms hits), $0.01 per call, 5 free trial calls per agent_id, failed calls never charged, and a payment-required quote (explicitly a non-fatal response) with top-up instructions. Minor deduction for not stating result freshness beyond cache TTL.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Well front-loaded: purpose first, then labeled usage, parameter, and pricing sections. However the free-trial/payment flow is restated three times (trial-call note, pricing paragraph, and closing example), so several sentences do not fully earn their place.

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?

An output schema exists, so return-format detail is unnecessary; the description covers everything else an agent needs — cost, trial limits, caching, and the exact recovery path after a payment-required response. Nothing required for correct invocation 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?

Schema coverage is 100%, so each parameter's type and constraints are already documented, giving a baseline of 3. The description goes further by specifying the interaction pattern: pass a non-empty ticker, omit agent_id/tx_hash during the free trial, and supply agd_pass_ or tx_hash only for paid execution — workflow meaning the schema alone doesn't convey.

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?

Names a concrete verb and resource set — resolving US tickers to SEC CIK numbers plus 10-K/10-Q/8-K filings and entity metadata. This is unmistakably distinct from the only sibling, get_agent_wallet_status, which the description itself identifies as the billing/quota tool.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE and WHEN NOT TO USE blocks, including a named alternative (get_agent_wallet_status) for quota checks and an explicit exclusion for unrelated domains/media. The condition that selects this tool is stated without inference.

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

All sec-intel-mcp 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.

Resources

Need Help?