Model Context Protocol (MCP) server for freee API integration
Filingpulse is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Fresh SEC filing intel: 8-K events, Form 4 insider activity, filing search and digests.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user cloudcorprecords-filingpulse-mcp '--' npx -y @reneturcios/filingpulse mcp
# 2 — ask your agent for something these tools do
# whats_new_since, filing_digest, company_watch and 2 more
Filingpulse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Filingpulse as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user cloudcorprecords-filingpulse-mcp '--' npx -y @reneturcios/filingpulse mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Return SEC filings that are NEW since a cursor token (your bookmark). Pass the cursor from a prior call to get only filings since then. Filter by form type, ticker, CIK, 8-K item code, and minimum event severity. This is the fresh-filing delta feed's core lock-in primitive. Monitoring/research…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cursor | string | no | Opaque cursor from a previous response; omit for first call. |
| form | array | no | Form types, e.g. ['8-K','4']. |
| ticker | string | no | Stock ticker symbol of the company |
| cik | string | no | CIK number of the company in the SEC EDGAR system |
| item | string | no | 8-K item code, e.g. '5.02'. |
| minEventScore | number | no | Severity floor 1-10 (material events only). |
| limit | number | no | Max filings to return (default 100). |
Digest for a filter over the last N days: material 8-K events, insider (Form 4) activity, new registrations, and periodic reports. Best summary signal for a desk.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| form | array | no | SEC form types to include, such as 10-K or 8-K |
| ticker | string | no | Stock ticker symbol of the company |
| cik | string | no | CIK number of the company in the SEC EDGAR system |
| company | string | no | Company name to match filings against |
| item | string | no | Filing item or section to focus the digest on |
| minEventScore | number | no | Minimum event score for a filing to be included |
| days | number | no | Lookback days (default 7). |
Given a company CIK, return recent filings, insider activity, and a filing-velocity stat (last-90 vs prior-90 days). Live-backfilled from EDGAR so it works day one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cik | string | yes | CIK number of the company in the SEC EDGAR system |
Recent Form 4/3/5 insider transactions with insider-cluster detection (multiple insiders filing on the same issuer). Optionally filter by ticker/CIK.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | no | Stock ticker symbol of the company |
| cik | string | no | CIK number of the company in the SEC EDGAR system |
| days | number | no | Number of days of insider activity to look back over |
Direct live search of SEC EDGAR full-text for the latest filings of a form type in a date range. Use for ad-hoc lookups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| form | string | no | Form type, e.g. '8-K'. |
| q | string | no | Optional full-text query. |
| start | string | no | Start date of the filing search range |
| end | string | no | End date of the filing search range |
| limit | number | no | Default 50, max 100. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Filingpulse or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Filingpulse can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.