FilingLens Local SEC Fact Comparison
MCPB · FILINGLENS-0.1.0.MCPB
Compare the same SEC fact and period at two filing cutoffs locally, with source evidence.
Available components
Last scanned (10 hours ago)
Scores higher than 75% of MCPB servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security25
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 3 of 3 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 245 tokens (~61/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +26
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 50 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 40 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 14
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed mcpb/https://github.com/f-tiger/agi-site/releases/download/fleet-mcp-registry-2026-10-10/filinglens-0.1.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
filinglens_compare Compare the same fact at two filing cutoffs ~105
Compare one exact concept, unit and start/end period as reported by the latest eligible filing at each supplied as-of date. Same-day value conflicts yield incomplete. Return source accession links and exact absolute difference. This does not classify restatements, explain causes or recommend trades.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | One SEC companyconcept JSON object obtained by the host from the official SEC API. No arbitrary URLs, file reads or network requests by this server. |
| options | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| absolute_change | string|null | yes | – |
| after | object | yes | – |
| as_of | object | yes | – |
| before | object | yes | – |
| cik | string | yes | – |
| entity | string | yes | – |
| investment_recommendation | boolean | yes | – |
| limits | array | yes | – |
| period | object | yes | – |
| restatement_determined | boolean | yes | – |
| scope | string | yes | – |
| status | string | yes | – |
| tag | string | yes | – |
| taxonomy | string | yes | – |
| unit | string | yes | – |
| version | string | yes | – |
No examples provided.
filinglens_example Learn with a fictional filing comparison ~48
Return clearly fictional same-period revenue observations and cutoffs. The -2000000 difference is a demonstration, not a real company restatement. Sample accession numbers must never be presented as real filings.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
filinglens_periods Inspect exact fact periods and units ~88
List available exact periods from supplied SEC companyconcept data. Use pagination. Never mix a quarter and a year-to-date period, units or entities.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | One SEC companyconcept JSON object obtained by the host from the official SEC API. No arbitrary URLs, file reads or network requests by this server. |
| limit | integer | – | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | yes | – |
| entity | string | yes | – |
| label | string | yes | – |
| next_offset | – | yes | – |
| observations | integer | yes | – |
| periods | array | yes | – |
| periods_total | integer | yes | – |
| tag | string | yes | – |
No examples provided.
How do I install the FilingLens Local SEC Fact Comparison MCP server?
FilingLens Local SEC Fact Comparison ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 717ac5329a4df5cbf5de02015134de5138a427f06d2c76748132c0afa9993b0b; the commands to do that are on this page. If it does not match, do not open it.
mcpb · filinglens-0.1.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
717ac5329a4df5cbf5de02015134de5138a427f06d2c76748132c0afa9993b0b
macOS / Linux
echo "717ac5329a4df5cbf5de02015134de5138a427f06d2c76748132c0afa9993b0b filinglens-0.1.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\filinglens-0.1.0.mcpb).Hash -eq "717ac5329a4df5cbf5de02015134de5138a427f06d2c76748132c0afa9993b0b"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the FilingLens Local SEC Fact Comparison MCP server?
FilingLens Local SEC Fact Comparison is an MCP server listed in the public MCP registry as io.github.f-tiger/filinglens. Compare the same SEC fact and period at two filing cutoffs locally, with source evidence. This page covers its MCPB bundle (https://github.com/f-tiger/agi-site/releases/download/fleet-mcp-registry-2026-10-10/filinglens-0.1.0.mcpb).
Is the FilingLens Local SEC Fact Comparison MCP server safe to use?
FilingLens Local SEC Fact Comparison scores 40 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FilingLens Local SEC Fact Comparison MCP server expose?
FilingLens Local SEC Fact Comparison exposes 3 tools: filinglens_example, filinglens_periods, filinglens_compare. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.