Signal8 MCP Serverofficial
A
licenseA
qualityD
maintenanceProvides AI agents with direct access to SEC filing intelligence, company fundamentals, dilution risk scoring, and cross-company analytics for financial research.
87
195
1
MIT
arkolith
Server Details
Evidence-backed capital-change intelligence and sourced financial data for AI agents
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
fund.holdings.as_of2 fields changed- added
Input schema / additionalPropertiesAdded value: +false - changed
Input schema / properties / as_of / descriptionPrevious value: -"ISO date, e.g. '2023-06-30' — holdings as known on this date"New value: +"ISO date or timestamp. A date such as 2023-06-30 includes that full UTC day (through 23:59:59.999Z); a timestamp must include Z or an explicit UTC offset."
1 tool update
- Changed
capital_rotation1 field changed- changed
Input schema / properties / weight_by / descriptionPrevious value: -"fund_quality (default) weights each fund's flow by a price-free smart-money quality score (concentration, selectivity, AUM growth, insider co-buy) so index/market-maker money counts less; equal treats every filer the same."New value: +"fund_quality (default) weights each fund's flow by a price-free focus score (breadth-adjusted top-10 focus, reported book growth, evidence-adjusted insider co-buy) after taxonomy exclusions; equal treats every included filer the same."
2 tool updates
- Added
capital_change_brief - Changed
feedback.submit4 fields changed- added
Input schema / properties / brief_idAdded value: +{ + "description": "The exact brief_id returned by capital_change_brief", + "pattern": "^ccm_[a-f0-9]{64}$", + "type": "string" +} - added
Input schema / properties / tickerAdded value: +{ + "description": "The ticker from the brief", + "pattern": "^[A-Za-z][A-Za-z0-9./-]{0,14}$", + "type": "string" +} - added
Input schema / properties / verdictAdded value: +{ + "description": "The user's explicit verdict, never an agent inference", + "enum": [ + "useful", + "missing" + ], + "type": "string" +} - added
Input schema / properties / workflowAdded value: +{ + "description": "Set to capital_change_brief when recording an explicit verdict for that workflow", + "enum": [ + "capital_change_brief" + ], + "type": "string" +}
1 tool update
- Changed
events.latest1 field changed- changed
Input schema / properties / form / descriptionPrevious value: -"SEC form type, e.g. '4' (insider). Omit for all."New value: +"SEC form type. '4' (insider Form 4) is what's carried today; omit for all carried forms."
1 tool update
- Changed
copy.leaderboard2 fields changed- changed
Input schema / properties / sort / descriptionPrevious value: -"aum = biggest book (default), active = most recently filed, followers = most followed"New value: +"aum = biggest book (default), active = most recently filed, followers = most followed, return = best filed-date 13F clone track record" - changed
Input schema / properties / sort / enumPrevious value: -[ - "aum", - "active", - "followers" -]New value: +[ + "aum", + "active", + "followers", + "return" +]
4 tool updates
- Added
capital_rotation - Added
get_smart_money_leaderboard - Added
get_ticker_confluence - Added
insider.filing
5 tool updates
- Added
clinicaltrials.search - Added
congress.trades - Added
fda.approvals - Added
fda.recalls - Added
pharma.resolve
2 tool updates
- Added
copy.leaderboard - Added
copy.target.get
25 tool updates
- First observed
account.balance - First observed
congress.disclosures.list - First observed
congress.member.search - First observed
divergence.scan - First observed
events.latest - First observed
feedback.submit - First observed
fund.holdings - First observed
fund.holdings.as_of - First observed
fund.holdings.diff - First observed
fund.list - First observed
fund.position.history - First observed
insider.clusters - First observed
insider.company - First observed
insider.transactions - First observed
macro.series.get - First observed
macro.series.search - First observed
predictionmarket.list - First observed
predictionmarket.quote - First observed
provenance.get - First observed
search - First observed
signal.confluence - First observed
signal.crowding - First observed
stock.owners - First observed
watchlist.poll - First observed
watchlist.poll.live
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Private company data & real-time news signals for AI agents.
Prediction markets, on-chain flows, ETF flows, equities and macro intelligence for AI agents.
Point-in-time, survivorship-free SEC EDGAR fundamentals + smart-money signals for AI agents.
The financial MCP for AI agents - 90+ financial tables, SEC filings, signals, alt-data.
Related MCP Servers
- AlicenseAqualityAmaintenancePre-computed financial market intelligence for AI agents. Stocks, crypto, and ETFs.91675MIT
- AlicenseNot gradedqualityCmaintenanceFinancial research data backend for AI agents, offering standardized financial data, semantic news and event search, paragraph-cited company filings, and alternative data across US, Japan, Hong Kong, and China A-shares.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access and synthesize per-ticker financial research data from multiple providers within a private, self-hosted workspace.5MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, such as fund.holdings vs fund.holdings.as_of vs fund.holdings.diff, which are well-differentiated. However, signal.confluence and get_ticker_confluence overlap in providing multi-source confluence, though their descriptions note differences (one includes capital rotation, the other can rank market-wide). This minor ambiguity prevents a perfect score.
Naming Consistency3/5
Naming conventions are mixed: many use dot notation (e.g., account.balance, clinicaltrials.search), but some use underscores (e.g., get_smart_money_leaderboard, get_ticker_confluence) and one is a single word (search). While patterns are recognizable, the inconsistency can be confusing for an agent predicting tool names.
Tool Count3/5
With 37 tools covering domains from SEC filings to FDA approvals, the count is on the higher side but justifiable for a comprehensive financial data platform. It feels slightly heavy, but each tool serves a distinct function within its domain, so it is not excessive.
Completeness4/5
The tool set covers the core domain thoroughly: fund holdings, insider trading, congressional trades, prediction markets, FDA data, clinical trials, macro series, and cross-signal confluences. Minor gaps exist (e.g., no direct stock price tools, but these are intentionally excluded as 'price-free'). Overall, the surface is well-suited for its stated purpose of providing informed finance signals.