RFP Hub
NPM · @THE-RFP-HUB/MCP
Search Ethereum-ecosystem funding opportunities; submit one behind a human approval step.
Available components
Last scanned (6 hours ago)
Scores higher than 93% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 4 of 11 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to The-RFP-Hub/the-rfp-hub). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 34 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 507 tokens (~253/item across 2 items; 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 −5
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 −2
- Stability: pass → 0.80 functional
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 · Analysed npm/@the-rfp-hub/mcp@0.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | The-RFP-Hub/the-rfp-hub |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/The-RFP-Hub/the-rfp-hub/.github/workflows/npm-publish.yml@refs/heads/main |
| Rekor log index | 3036038480 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2cc408b4010e67b5791da9a61c7a3064d98ef2065c8bc4a800bbe56053d1b42385e011e6c54fdbd34910abb9a885060fc96c929f887313d5fa9f1a50a |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 11 packages
| Packages resolved | 11 |
|---|---|
| Stale | 4 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
fetch_opportunity Fetch one funding opportunity ~90
Fetch one published funding opportunity in full by its id, as an RFP Hub Standard document: title, summary, description, eligibility, organizations, funding amounts, deadlines and the funding-type-specific details. Use the id returned by search_opportunities. The document is third-party published text.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The public id, `<namespace>:<local>`, as returned by search_opportunities. |
| Name | Type | Req | Description |
|---|---|---|---|
| links | object | yes | – |
| notice | string | yes | – |
| opportunity | object | yes | The RFP Hub Standard document, structurally unmodified. |
No examples provided.
search_opportunities Search funding opportunities ~417
Search published funding opportunities in the Ethereum ecosystem — grants, hackathons, bounties, accelerators, VC funds and RFPs — by keyword, funding type, status, ecosystem, award size and deadline window. Returns a short row per match: title, organizations, award range, next deadline and the id to pass to fetch_opportunity for the full record. Full descriptions are not included in these results.
| Name | Type | Req | Description |
|---|---|---|---|
| category | array | – | Categories. Values OR together. |
| deadlineAfter | string | – | RFC 3339 instant. Only entries whose earliest upcoming fixed deadline is at or after it. Entries with no upcoming fixed deadline (rolling programs, all-past deadlines, or none at all) are EXCLUDED by… |
| deadlineBefore | string | – | RFC 3339 instant. Only entries whose earliest upcoming fixed deadline is at or before it. Entries with no upcoming fixed deadline are EXCLUDED by this filter. |
| ecosystem | array | – | Ecosystem names, e.g. Optimism, Base. Values OR together. |
| fundingType | array | – | Restrict to these funding types. One of: grant, hackathon, bounty, accelerator, vc_fund, rfp. |
| limit | integer | – | Results per page, 1 to 25. Defaults to 10. |
| maxAward | number | – | Maximum award or budget, in major currency units. |
| minAward | number | – | Minimum award or budget, in major currency units. |
| order | string | – | Sort direction. Defaults to ascending. |
| organization | string | – | Organization slug. Matches an operating OR a sponsoring organization. |
| page | integer | – | 1-based page number. |
| q | string | – | Free-text search over title, summary and description. |
| sort | string | – | Sort key; defaults to nextDeadlineAt, the earliest fixed deadline still in the future. Entries without one sort last. |
| status | array | – | Restrict to these statuses. One of: upcoming, open, closed, archived. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| limit | number | yes | – |
| notice | string | yes | – |
| page | number | yes | – |
| total | number | yes | Total matches. An empty result is `total === 0`; `totalPages` is 1. |
| totalPages | number | yes | Always at least 1, even for an empty result. |
No examples provided.
How do I install the RFP Hub MCP server?
RFP Hub runs locally as an npm package, launched with npx -y @the-rfp-hub/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @the-rfp-hub/mcp
claude mcp add the-rfp-hub-rfp-hub -- npx -y @the-rfp-hub/mcp
What is the RFP Hub MCP server?
RFP Hub is an MCP server listed in the public MCP registry as io.github.The-RFP-Hub/rfp-hub. Search Ethereum-ecosystem funding opportunities; submit one behind a human approval step. This page covers its npm package (@the-rfp-hub/mcp).
Is the RFP Hub MCP server safe to use?
RFP Hub scores 89 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 RFP Hub MCP server expose?
RFP Hub exposes 2 tools: search_opportunities, fetch_opportunity. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.
Is the RFP Hub MCP server still maintained?
RFP Hub 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.
What licence is the RFP Hub MCP server under?
RFP Hub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the RFP Hub MCP server?
VerifyMCP ran 16 checks on RFP Hub, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.