Developer · Remote MCP server
RFP.ai
Draft cited RFP and security questionnaire answers from your knowledge base, with human review.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.rfp/rfp-ai- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-11
- Updated
- 2026-06-11
- Publisher
- ai.rfp
- Namespace
- Namespace verified by the MCP Registry via the domain rfp.ai · how
- Website
- rfp.ai/docs/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://rfp.ai/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect RFP.ai
RFP.ai is a remote MCP server: there is nothing to install. Its endpoint is https://rfp.ai/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Review MCPMulti-model code review: a panel of models + detectors return a pass/fail verdict. Paid via x402. | Remote · HTTPLive check: ✓ handshake |
| ReviewGateCode review against your team standards, before the pull request: generator finds, judge confirms. | Local · stdio |
| ReviewGuardSafety boundary for agent written GitHub PR reviews: pending and invisible, submitting is opt-in. | Local · stdio |
| RFixCreate RF signal projects from prompts, inspect graphs, and export IQ data. | Remote · HTTPLive check: ✓ handshake |
| RheaRhea MCP - expert-curated database of biochemical reactions. | Remote · HTTPLive check: ✓ handshake |
| RideDesk Developer DocsDeveloper docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth. | Remote · HTTPLive check: ✓ handshake |
| Rigor MCPVerified statistical inference for AI agents: hypothesis tests, sequential testing, power. | Local · stdio |
| RigourQuality gates for AI agents. Lint, test, build checks with memory persistence. | Local · stdio |