# Impact Plexus (remote · mcp.impactplexus.com)

Find Canadian and US funders and funding opportunities from public charity and grant filings.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.impactplexus.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-impactplexus-funders/mcp.md), [page](https://verifymcp.io/servers/com-impactplexus-funders/mcp)

## Channel facts

- Endpoint: `https://mcp.impactplexus.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 672 tokens (~168/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Impact Plexus MCP server?

Impact Plexus is a hosted endpoint at https://mcp.impactplexus.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-impactplexus-funders 'https://mcp.impactplexus.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-impactplexus-funders": {
      "url": "https://mcp.impactplexus.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-impactplexus-funders": {
      "type": "http",
      "url": "https://mcp.impactplexus.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-impactplexus-funders]
url = "https://mcp.impactplexus.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-impactplexus-funders": {
      "type": "remote",
      "url": "https://mcp.impactplexus.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-impactplexus-funders --url 'https://mcp.impactplexus.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-impactplexus-funders:
    url: "https://mcp.impactplexus.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-impactplexus-funders": {
      "Transport": "http",
      "Url": "https://mcp.impactplexus.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-impactplexus-funders -t streamable-http -u 'https://mcp.impactplexus.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-impactplexus-funders": {
      "type": "http",
      "url": "https://mcp.impactplexus.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 65)

First indexed and scored.

## MCP tools (4)

### `funder_search` (~280 tokens)

Search public funders

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; ties by name, then slug. This orders public giving records; it is not a fit assessment for any organization. Use the slug of a result with funder_profile to read the full profile.

Input parameters:

- `cause_area` (string): Canonical cause area. Values match the platform taxonomy (core/cra_to_canonical.py, core/ntee_to_canonical.py).
- `jurisdiction` (string): Country of operation or grantmaking (CA or US).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1 to 50.
- `region_code` (string): 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): Funder size by average annual giving over the last five reported years. See the SizeBand schema for band limits.

Output parameters:

- `items` (array)
- `pagination` (object)

### `funder_profile` (~62 tokens)

Get public funder profile

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.

Input parameters:

- `funder_slug` (string, required): Public URL slug from a funder_search result. Not an internal database identifier.

Output parameters:

- `cause_areas` (array)
- `facts` (array)
- `geography` (string)
- `jurisdiction` (string)
- `last_verified_date` (string): Most recent verification date across the facts shown.
- `name` (string)
- `region_codes` (array)
- `size_band` (string): Average annual giving over the last five reported years, in the funder's reporting currency. small is under 100,000; medium is 100,000 to 1,000,000; large is over 1,000,000; unknown means no public g…
- `slug` (string)
- `source_names` (array)
- `summary` (string): Plain-language narrative only.
- `website_url` (string|null): The funder's own website, if public.

### `opportunity_search` (~280 tokens)

Search public opportunities

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.

Input parameters:

- `cause_area` (string): Canonical cause area. Values match the platform taxonomy (core/cra_to_canonical.py, core/ntee_to_canonical.py).
- `deadline_after` (string): Only opportunities with a fixed deadline on or after this date (YYYY-MM-DD).
- `deadline_before` (string): Only opportunities with a fixed deadline on or before this date (YYYY-MM-DD).
- `include_rolling` (boolean): Include opportunities with rolling or unpublished deadlines. Ignored when a deadline filter is set.
- `jurisdiction` (string): Country of operation or grantmaking (CA or US).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1 to 50.
- `region_code` (string): 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): Restrict to opportunities that are open now or announced as upcoming. Omit for both.

Output parameters:

- `items` (array)
- `pagination` (object)

### `opportunity_detail` (~50 tokens)

Get public opportunity details

Return one opportunity: plain-language eligibility, deadline, and a link to the funder's own page.

Input parameters:

- `opportunity_slug` (string, required): Public URL slug from an opportunity_search result. Not an internal database identifier.

Output parameters:

- `cause_areas` (array)
- `deadline` (string|null): Next fixed deadline. Null when deadline_type is rolling or unknown.
- `deadline_type` (string)
- `eligibility_summary` (string): Plain-language eligibility, not an inferred fit score.
- `funder_name` (string)
- `funder_slug`: Slug for funder_profile, or null when the funder has no public profile.
- `geography` (string)
- `jurisdiction` (string)
- `last_verified_date` (string)
- `name` (string)
- `region_codes` (array)
- `slug` (string)
- `source_names` (array)
- `source_url` (string): The funder's own page for this opportunity.
- `status` (string)
- `summary` (string): Plain-language narrative only.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-impactplexus-funders/mcp#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65
- 2026-10-27: 65

## Common questions

### What is the Impact Plexus MCP server?

Impact Plexus is an MCP server listed in the public MCP registry as com.impactplexus/funders. Find Canadian and US funders and funding opportunities from public charity and grant filings. This page covers its hosted endpoint (https://mcp.impactplexus.com/mcp).

### Is the Impact Plexus MCP server safe to use?

Impact Plexus scores 69 out of 100 on VerifyMCP. 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 Impact Plexus MCP server expose?

Impact Plexus exposes 4 tools: funder_search, funder_profile, opportunity_search, opportunity_detail. Their descriptions and schemas cost roughly 672 tokens of context every time the server is loaded.

### Does the Impact Plexus MCP server require authentication?

No. We connected to Impact Plexus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Impact Plexus MCP server still maintained?

Impact Plexus is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.impactplexus.com/mcp
- Website: https://impactplexus.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-impactplexus-funders/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-impactplexus-funders/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-impactplexus-funders/mcp