mcpbeat Sign in

RFP.ai MCP Server

answering

RFP.ai is answering right now. Last checked 10 min ago.

Draft cited RFP and security questionnaire answers from your knowledge base, with human review

Uptime history 90 days of history · worst day 93%
90 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
477 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check RFP.ai every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add rfp-ai --transport http https://rfp.ai/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://rfp.ai/api/mcp
~/.codex/config.toml
[mcp_servers.rfp-ai]
url = "https://rfp.ai/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "rfp-ai": {
      "url": "https://rfp.ai/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "rfp-ai": {
      "type": "http",
      "url": "https://rfp.ai/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://rfp.ai/api/mcp streamable-http sign-in 120 ms 10 min ago

Alternatives to RFP.ai

same job, measured the same way
ResponseHub
by responsehub

Answer security questionnaires and RFPs from your AI knowledge base.

answering
capsulam
by capsulam

Human-reviewed digests on AI, regulation and cybersecurity, every fact linked to its source.

answering
FillTrust security questionnaire corpus
by filltrust

Guidance for answering vendor security questionnaires. Every result carries the page it came from.

5 tools answering
PandaWard
by ratomirjovanovic

Local, evidence-based application security assessment with an evidence ledger and retests.

local only
Dingdawg Code Review
by dingdawg

AI code review — security, quality, performance. Learns your patterns. Receipted.

47 installs/wk local only
SecScan
by secscan

Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.

12 tools answering
Unchore Defend
by smilemino

Grade a site's security headers with fixes and a badge; read logs or code for the defender.

local only
Deep Noodle Security Review Guide
by myzie

Read-only guidance and report templates for reviewing application security with your own agent.

4 tools answering

RFP.ai — questions

Answers built from our own checks of this server.

Why is there no tool list for RFP.ai?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is RFP.ai working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 477 ms. The bar chart above shows every period we have measured.
How do I connect RFP.ai?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to RFP.ai?
No API key is involved. RFP.ai answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is RFP.ai?
It answers our handshake in 477 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.