F
license-
qualityD
maintenanceReturns verified financial data (SEC EDGAR & FRED) with machine-readable citations. Guaranteed zero hallucinations for AI agents.
SEC Filing Proof
Server Details
Verify whether an official SEC filing supports a specific financial claim.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.1/5.0
Tool DescriptionsA
Average 4.4/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined and distinct.
Naming Consistency5/5
The single tool name 'verify_sec_filing_claim' follows a clear verb_noun pattern and is descriptive. Naming consistency is trivially maintained with one tool.
Tool Count2/5
A single tool for SEC filing verification is extremely thin for a server. While the tool is substantive, the server likely needs additional tools (e.g., get_filing, list_filings) to be useful, making the count feel insufficient.
Completeness2/5
The tool covers a specific verification workflow but lacks supporting operations like retrieving filings or searching across companies. The surface is severely limited for the stated domain, leaving agents with no way to explore or cross-check beyond the single claim verification.
Available Tools
1 toolverify_sec_filing_claimVerify SEC Filing ClaimARead-onlyIdempotentInspect
Verify whether a company's official SEC filing supports a specific financial claim. Input ticker or CIK plus claim. Returns filing/XBRL evidence and supported, contradicted, insufficient-evidence, or explicit ambiguity/failure states. Not a market-data feed or investment advice.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cik | No | SEC Central Index Key. Provide ticker or CIK. | |
| claim | Yes | One atomic financial claim to check against official SEC filings. | |
| period | No | Optional period hint such as latest quarter or FY2025. | |
| ticker | No | Issuer ticker symbol. Provide ticker or CIK. | |
| filing_type | No | Optional filing hint such as 10-Q or 10-K. | |
| fiscal_year | No | Optional fiscal year. | |
| fiscal_quarter | No | Optional fiscal quarter such as Q1. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| cik | Yes | |
| claim | Yes | |
| period | Yes | |
| ticker | Yes | |
| company | Yes | |
| verdict | Yes | |
| evidence | Yes | |
| period_end | Yes | |
| filing_date | Yes | |
| filing_type | Yes | |
| source_urls | Yes | |
| period_start | Yes | |
| retrieved_at | Yes | |
| source_status | Yes | |
| service_version | Yes | |
| reasoning_summary | Yes |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the description doesn't need to repeat those. It adds behavioral context by specifying return states (supported, contradicted, insufficient-evidence, ambiguity/failure) and mentions evidence types (filing/XBRL). This exceeds the baseline without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no redundancy. It front-loads the core purpose, then quickly notes input requirements and output states. Every clause earns its place, making it tightly written and easily scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (7 parameters, 1 required) and the existence of an output schema, the description covers essential usage context (input identifiers, output categories, and limitations). It doesn't dive into parameter nuances, but the schema handles that, and the description is sufficient for an agent to decide when and how to invoke this tool.
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?
With 100% schema description coverage, the baseline is 3. The description adds value by clarifying that 'ticker or CIK' are alternative identifiers and that 'claim' is the primary input, which maps directly to the schema's required field. This is a useful clarification beyond the schema's per-field descriptions.
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 clearly states the tool's function: verify whether a company's official SEC filing supports a specific financial claim. It uses a specific verb ('verify') and resource ('SEC filing'), and distinguishes itself from market-data feeds and investment advice, making its purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context (verifying financial claims against SEC filings) and explicitly states what it is not (market-data feed, investment advice), which provides exclusionary guidance. However, it does not explicitly name alternatives or provide when-not-to-use scenarios, though no siblings exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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 Servers
- Flicense-qualityCmaintenanceEnables AI agents to search, retrieve, and analyze SEC 10-K filings with hybrid BM25+kNN retrieval, per-claim citations, and strict numeric grounding verification.
- AlicenseAqualityBmaintenanceConnects AI agents to over 4 million certified SEC EDGAR financial facts with cryptographic provenance and zero hallucination.67Apache 2.0
- AlicenseAqualityBmaintenanceMCP server that lets an LLM read official SEC financial data, tracing every number back to a specific SEC filing, US-GAAP tag, and filing date.4MIT