Unified 5-in-1 B2B ATS job and signal feed: Greenhouse, Workday, Ashby, Lever, SmartRecruiters.
Nothing to run from here
Plan Data API 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.
96/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Form 5500 data for prospecting and research: U.S. retirement plans, recordkeepers, fees, switches.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http plan-data-api-mcp https://api.form5500data.com/mcp
# 2 — ask your agent for something these tools do
# search_plans, get_plan, get_plan_history and 4 more
Plan Data API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FOAll 1 server
form5500data1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http plan-data-api-mcp https://api.form5500data.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 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.
Find plans. Give at least one of name, ein, state or recordkeeper; the other filters narrow the list. Each result is a short summary: call get_plan with its ein and pn for the profile. With name, results are ordered by match score, then size; without it, largest plans first. Plans that ended are hidden unless include_ended=true. Paging stops at offset 500: narrow the filters to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | no | Company or plan name, as you know it. Fuzzy: typos, missing suffixes (Inc, LLC), DBA names and former names all match, and the last word can be a prefix ("starb"). Results come best match first with a | |
| ein | no | Sponsor EIN (9 digits, dashes allowed). Lists every retirement plan under it. | |
| state | no | Two-letter state of the sponsor's address, e.g. TX. | |
| min_assets | no | Minimum end-of-year net assets in dollars, latest plan year. | |
| max_assets | no | Maximum end-of-year net assets in dollars. | |
| min_participants | no | Minimum end-of-year total participants. | |
| max_participants | no | Maximum end-of-year total participants. | |
| recordkeeper | no | Recordkeeper, any brand old or new ("Empower", "Great-West", "Fidelity"). Matched to the firm's family, so Great-West and Prudential filings count as Empower. Only plans that filed a Schedule C can ma | |
| plan_type | no | Plan type: 401k, 403b, cash_balance, db_and_dc, defined_benefit, esop, ira_based, money_purchase, other_dc, profit_sharing, stock_bonus, target_benefit, type_not_coded, db, dc. dc = any defined cont | |
| filer_size | no | large = files Schedule H (generally 100+ participants; has providers and fees); small = 5500-SF or Schedule I. | |
| include_ended | boolean | no | Include plans that are terminated, merged into another plan, or stopped filing. Off by default. |
| limit | integer | no | Results per page (1-50). |
| offset | integer | no | Results to skip (0-500). |
The plan as of its latest filing: identity and status, plan type and features, assets and participants, average balance and approximate return, recordkeeper, advisors and auditor, headline fees, screening signals and data-quality flags. When the latest year is a small-plan filing (no Schedule C), the recordkeeper shown is the last one seen on an earlier Schedule C, labeled with its year and a low
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ein | string | yes | Sponsor EIN (9 digits, dashes allowed). |
| pn | no | Plan number (1-999; 1 and 001 both work). Optional when the EIN sponsors only one retirement plan; otherwise the error lists the plans to choose from. |
One entry per plan year, oldest first: the filing used, assets and participants, average balance, approximate return, participant growth (flagged across the 2023 counting change), the growth breakdown (contributions, investment return, distributions, expenses, transfers), plan-paid expenses and Schedule C fees in bps, the year's recordkeeper / primary advisor / auditor, and the change events detec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ein | string | yes | Sponsor EIN (9 digits, dashes allowed). |
| pn | no | Plan number (1-999). Optional when the EIN has one plan. |
For each large plan year: Schedule C pay by role (recordkeeping, advisory, participant advice, TPA, investment management, trustee, other) in dollars and basis points of average net assets; every provider on the Schedule C with names as filed, codes, direct and indirect pay; Schedule H line 2i expenses as a second view; and a completeness rating with the reasons. Small plans file no Schedule C: t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ein | string | yes | Sponsor EIN (9 digits, dashes allowed). |
| pn | no | Plan number (1-999). Optional when the EIN has one plan. | |
| plan_year | no | One plan year only. Default: every year. |
Change events detected by comparing each plan's consecutive filings, newest filing first. Each event has before/after values, a confidence, the year compared against, a plain-English detail and the ACK ID of the filing that shows it. Providers are compared by family, so a rebrand (Great-West → Empower) isn't a change. Each event also has the plan's size around the event (net_assets_at_event), w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ein | no | Only this sponsor's plans (EIN, 9 digits, dashes allowed): what changed at one company. | |
| pn | no | With ein: only this plan number. | |
| state | no | Two-letter state of the sponsor (latest filing). | |
| event_type | no | Event type(s); repeat the parameter or separate with commas. One of: recordkeeper_change, advisor_added, advisor_removed, advisor_changed, auditor_change, audit_opinion_change, late_deposits_appeared, | |
| since | no | Only events whose filing DOL received on or after this date (YYYY-MM-DD): "what's new since I last checked". Excludes filings_stopped, which no filing reveals. | |
| plan_year_from | no | Earliest plan year of the event. | |
| plan_year_to | no | Latest plan year of the event. | |
| min_confidence | string | no | Lowest confidence to include: high = high only, medium = high and medium, low = all. |
| recordkeeper | no | Only recordkeeper_change events to or from this recordkeeper family (any brand name works). | |
| from_recordkeeper | no | Only recordkeeper_change events away from this recordkeeper family (any brand name). Combine with to_recordkeeper for one move, e.g. Empower to Fidelity. | |
| to_recordkeeper | no | Only recordkeeper_change events to this recordkeeper family (any brand name). | |
| plan_type | no | Plan type, as in search_plans (e.g. 401k, dc, db). | |
| filer_size | no | large or small, in the event's plan year. | |
| min_assets | no | Minimum net assets around the event (net_assets_at_event: the larger of the event year's start and end). | |
| sort | string | no | newest (the default: newest filing first) or assets (largest plan first, by net_assets_at_event). |
| limit | integer | no | Events per page (1-50). Each event is about 200 tokens of JSON, so the default 25 keeps an answer compact; narrow the filters rather than asking for more. |
| offset | integer | no | Events to skip (0-500). |
A list of plans for prospecting or research, many per call: plan and sponsor name, mailing address, EIN and plan number, industry, plan type, effective (inception) date, participants and net assets at the end of the latest plan year, form type, recordkeeper and primary advisor last seen on Schedule C, and the filing's ACK ID. Filter by industry, place (state, city, ZIP), size, plan type, effectiv
| Parameter | Type | Required | Notes |
|---|---|---|---|
| industry | no | The sponsor's industry: words ("restaurants", "car dealers", "law firms") or a NAICS business code or its start ("62" = health care, "5411" = legal services). Separate several with commas. `meta.query | |
| state | no | Two-letter state of the sponsor's address, e.g. OH. | |
| city | no | Sponsor's city, as on the filing (case doesn't matter). Best with state. | |
| zip | no | Sponsor's ZIP code or its start (3-5 digits), e.g. 432 for the Columbus, OH area. | |
| plan_type | no | Plan type, as in search_plans (e.g. 401k, dc, db). | |
| filer_size | string | no | large (the default) = long-form filers: Form 5500 with Schedule H, generally 100+ participants, with providers on Schedule C. small = 5500-SF or Schedule I. any = both. |
| min_participants | no | Minimum end-of-year participants, in the plan's latest plan year. | |
| max_participants | no | Maximum end-of-year participants. | |
| min_assets | no | Minimum end-of-year net assets in dollars, in the plan's latest plan year. | |
| max_assets | no | Maximum end-of-year net assets in dollars. | |
| effective_after | no | Only plans whose effective (inception) date is on or after this date (YYYY-MM-DD). | |
| effective_before | no | Only plans whose effective (inception) date is on or before this date (YYYY-MM-DD). | |
| recordkeeper | no | Only plans whose latest Schedule C names this recordkeeper (any brand, matched to its family as in search_plans). | |
| include_ended | boolean | no | Include plans that are terminated, merged into another plan, or stopped filing. Off by default. |
| sort | string | no | assets (largest first, the default), participants (most first), name (A-Z by sponsor) or newest_plan (latest effective date first). |
| limit | integer | no | Plans per page (1-100). The price is per call, whatever the limit. |
| offset | integer | no | Plans to skip (0-500). |
What the data covers per plan year, every limitation, the coverage-note codes responses can carry, the event types, the screening signals and the plan-type values. Free. Also lists the prices and what isn't charged. Same data as GET /coverage of the Plan Data API.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Plan Data API or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.0 · scanned 9 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest40b0dccfc141ed2d8b965fc2094ee76d6d4ff18ed62e980219187962ca151dbf
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| search_plans | no tags | |
| get_plan | no tags | |
| get_plan_history | no tags | |
| get_plan_fees | no tags | |
| find_plan_changes | no tags | |
| list_prospects | no tags | |
| get_coverage | no tags |
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
Integrityfirst-seen
Surface digest40b0dccfc141ed2d
Scanned2026-11-09
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Plan Data API can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.