FilingLens Local SEC Fact Comparison MCP server
Compare the same SEC fact and period at two filing cutoffs locally, with source evidence.
0 stars
Reviews
Write oneNobody has reviewed FilingLens Local SEC Fact Comparison yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
FilingLens Local SEC Fact Comparison tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How FilingLens Local SEC Fact Comparison compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
Install FilingLens Local SEC Fact Comparison in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the FilingLens Local SEC Fact Comparison repository's README, as published. We do not edit it. Read it on GitHub
agi-site — one public monorepo, N sites
Public monorepo for the site fleet (owner decision 2026-08-19). Public repos get free GitHub Actions minutes, which ends the account-wide 2,000 min/month problem that froze every private-repo schedule on 2026-08-18.
Each site keeps its own CLAUDE.md, tooling and conventions inside its directory. Root workflows are path-filtered: a commit only deploys the site it touches. History note: each site was imported as a fresh snapshot; pre-import history lives in the original private repos (f-tiger/agiscorecard, f-tiger/aitools, f-tiger/rearchfuture, f-tiger/sexweb), which are archives now — do not push site content there.
Privacy rule for this PUBLIC repo: no owner personal archive (owner-identity/owner-trajectory), no subscriber addresses, no tokens/keys. See CLAUDE.md.
One practical workflow check
帧选：AI 漫剧与短剧找片 is a free Chinese-language discovery catalogue with dated official sources and clearly labelled viewing destinations. It does not host episodes.
For creators, the video publishing assessment tool compares preparation for six Chinese platforms using local video metadata and self-reported checks. Try the worked examples, or cite its public methodology and structured rules. Files and reports stay in the browser; suggestions are test hypotheses, not viral predictions.
Compare coding assistants on a small CRM workflow: a free local exercise covering duplicate events, retries, credential errors and ambiguous timeouts. Synthetic data only; no account or API key required. For a task that remains stuck, use the linked public workflow-question form with a sanitized example. This is a technical help entry, not a checkout.
Owner TODO (one-time, optional but recommended)
integration to f-tiger/agiscorecard (that repo is archived; a stray push there would roll the site back). Until then: simply never push there.
- Cloudflare dashboard → Workers agiscorecard → disconnect the old git
tds-crawl-log schedules are live. Still open, optional (owner deferred GA4 on 2026-08-19; D1 is the primary channel):
- CLOUDFLAREAPITOKEN_ZONE configured 2026-08-19 — tds-traffic and
GA4SERVICEACCOUNT_JSON (they no-op gracefully until then)
- bpj-growth-loop.yml: GA4PROPERTYIDBPJ, GA4SERVICEACCOUNTJSON
- GA4 steps inside tds-traffic.yml: GA4PROPERTYID_TDS,
RESENDAPIKEY/SUPABASESERVICEKEY (eco heat-alert real sends), MCPREGISTRYPRIVATE_KEY (tds registry proof) Copy the values from the old private repos' Settings → Secrets (names unchanged).
- optional senders: TELEGRAMBOTTOKEN/TELEGRAMCHATID (tds grow notify),
Nothing above is checked by us. What we check is on the safety report.
FilingLens Local SEC Fact Comparison: common questions
- Is FilingLens Local SEC Fact Comparison MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the FilingLens Local SEC Fact Comparison safety report
- Does FilingLens Local SEC Fact Comparison need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is FilingLens Local SEC Fact Comparison maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v0.1.0.
- What can I use instead of FilingLens Local SEC Fact Comparison?
- Servers from other publishers that do the same job: EdgarTools MCP server.
Alternatives to FilingLens Local SEC Fact Comparison
Same job from other publishers: the closest match first, then the best rated.
- EdgarToolsOpen-source SEC EDGAR toolkit — 13 tools, 7 prompts, every filing type. No API key required.not reviewedWidely usedA
