Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Impact Plexus 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
Find Canadian and US funders and funding opportunities from public charity and grant filings.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http impact-plexus-mcp https://mcp.impactplexus.com/mcp
# 2 — ask your agent for something these tools do
# funder_search, funder_profile, opportunity_search and 1 more
Impact Plexus 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. 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.
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 impact-plexus-mcp https://mcp.impactplexus.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
4 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 funders by jurisdiction, cause area, size band and region. Results are ordered by how much each funder has given toward the requested cause and region in its recent public filings: larger, steadier and more widely giving funders first; funders that give mostly to one recipient or to their own related organizations, and donation platforms that pass donors' directed gifts through, come later; t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cause_area | string | no | Canonical cause area. Values match the platform taxonomy (core/cra_to_canonical.py, core/ntee_to_canonical.py). |
| jurisdiction | string | no | Country of operation or grantmaking (CA or US). |
| page | integer | no | Page number, starting at 1. |
| page_size | integer | no | Results per page, 1 to 50. |
| region_code | string | no | ISO 3166-2 province or state code, for example CA-ON or US-WA. Matches funders and opportunities that serve that region, including national ones. |
| size_band | string | no | Funder size by average annual giving over the last five reported years. See the SizeBand schema for band limits. |
Return one funder's plain-language profile, computed from active global observations. Each fact carries its public source name and the date it was last verified.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| funder_slug | string | yes | Public URL slug from a funder_search result. Not an internal database identifier. |
Find open and upcoming opportunities by jurisdiction, cause area, region and deadline. Ordered by deadline (soonest first, rolling and unknown deadlines last), then name, then slug. Results are not ranked against an organization. Use the slug of a result with opportunity_detail.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cause_area | string | no | Canonical cause area. Values match the platform taxonomy (core/cra_to_canonical.py, core/ntee_to_canonical.py). |
| deadline_after | string | no | Only opportunities with a fixed deadline on or after this date (YYYY-MM-DD). |
| deadline_before | string | no | Only opportunities with a fixed deadline on or before this date (YYYY-MM-DD). |
| include_rolling | boolean | no | Include opportunities with rolling or unpublished deadlines. Ignored when a deadline filter is set. |
| jurisdiction | string | no | Country of operation or grantmaking (CA or US). |
| page | integer | no | Page number, starting at 1. |
| page_size | integer | no | Results per page, 1 to 50. |
| region_code | string | no | ISO 3166-2 province or state code, for example CA-ON or US-WA. Matches funders and opportunities that serve that region, including national ones. |
| status | string | no | Restrict to opportunities that are open now or announced as upcoming. Omit for both. |
Return one opportunity: plain-language eligibility, deadline, and a link to the funder's own page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| opportunity_slug | string | yes | Public URL slug from an opportunity_search result. Not an internal database identifier. |
- 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 Impact Plexus 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 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
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 |
|---|---|---|
| funder_search | no tags | |
| funder_profile | no tags | |
| opportunity_search | no tags | |
| opportunity_detail | 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
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.2.0.
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 Impact Plexus 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.