Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Impact Plexus

REMOTE · MCP.IMPACTPLEXUS.COM

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

+3 this week 69 Trust /100

Last scanned (4 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +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.

  • 3 Nov 26 +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.

  • 1 Nov 26 +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.

  • 29 Oct 26 +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.

  • 28 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 27 Oct 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.impactplexus.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=impactplexus.com CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 f1fc699a4f2b58f9130cd9395e070683
SANs: impactplexus.com, mcp.impactplexus.com, *.mcp.impactplexus.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.impactplexus.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
impactplexus.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.impactplexus.com/mcp Verified 200
http (plaintext) http://mcp.impactplexus.com/mcp Inconclusive 405
MCP tools · 4 exposed · ~672 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
funder_profile ~62

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.

NameTypeReqDescription
funder_slugstringyesPublic URL slug from a funder_search result. Not an internal database identifier.
NameTypeReqDescription
cause_areasarrayyes–
factsarrayyes–
geographystringyes–
jurisdictionstringyes–
last_verified_datestringyesMost recent verification date across the facts shown.
namestringyes–
region_codesarrayyes–
size_bandstringyesAverage 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…
slugstringyes–
source_namesarrayyes–
summarystringyesPlain-language narrative only.
website_urlstring|nullyesThe funder's own website, if public.

No examples provided.

funder_search ~280

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.

NameTypeReqDescription
cause_areastring–Canonical cause area. Values match the platform taxonomy (core/cra_to_canonical.py, core/ntee_to_canonical.py).
jurisdictionstring–Country of operation or grantmaking (CA or US).
pageinteger–Page number, starting at 1.
page_sizeinteger–Results per page, 1 to 50.
region_codestring–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_bandstring–Funder size by average annual giving over the last five reported years. See the SizeBand schema for band limits.
NameTypeReqDescription
itemsarrayyes–
paginationobjectyes–

No examples provided.

opportunity_detail ~50

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

NameTypeReqDescription
opportunity_slugstringyesPublic URL slug from an opportunity_search result. Not an internal database identifier.
NameTypeReqDescription
cause_areasarrayyes–
deadlinestring|nullyesNext fixed deadline. Null when deadline_type is rolling or unknown.
deadline_typestringyes–
eligibility_summarystringyesPlain-language eligibility, not an inferred fit score.
funder_namestringyes–
funder_slug–yesSlug for funder_profile, or null when the funder has no public profile.
geographystringyes–
jurisdictionstringyes–
last_verified_datestringyes–
namestringyes–
region_codesarrayyes–
slugstringyes–
source_namesarrayyes–
source_urlstringyesThe funder's own page for this opportunity.
statusstringyes–
summarystringyesPlain-language narrative only.

No examples provided.

opportunity_search ~280

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.

NameTypeReqDescription
cause_areastring–Canonical cause area. Values match the platform taxonomy (core/cra_to_canonical.py, core/ntee_to_canonical.py).
deadline_afterstring–Only opportunities with a fixed deadline on or after this date (YYYY-MM-DD).
deadline_beforestring–Only opportunities with a fixed deadline on or before this date (YYYY-MM-DD).
include_rollingboolean–Include opportunities with rolling or unpublished deadlines. Ignored when a deadline filter is set.
jurisdictionstring–Country of operation or grantmaking (CA or US).
pageinteger–Page number, starting at 1.
page_sizeinteger–Results per page, 1 to 50.
region_codestring–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.
statusstring–Restrict to opportunities that are open now or announced as upcoming. Omit for both.
NameTypeReqDescription
itemsarrayyes–
paginationobjectyes–

No examples provided.

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.

remote · mcp.impactplexus.com

# add to Claude Code
claude mcp add --transport http com-impactplexus-funders 'https://mcp.impactplexus.com/mcp'
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.