RFP.ai MCP Server

by rfp Your server? Claim it

answering

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

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

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

521 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.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add rfp-ai --transport http https://rfp.ai/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "rfp-ai": {
      "url": "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

{
  "mcpServers": {
    "rfp-ai": {
      "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

URL	Transport	State	Latency	Checked
https://rfp.ai/api/mcp	streamable-http	sign-in	433 ms	11 min ago

Alternatives to RFP.ai

same job, measured the same way

FillTrust security questionnaire corpus

by filltrust

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

5 tools answering

Dingdawg Code Review

by dingdawg

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

50 installs/wk local only

Aperture Wallet Knowledge

by aperturex

Verified Aperture Wallet product, security, network, release, and Journal knowledge.

12 tools answering

pkgxray

by adamsjack711-ux

Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence.

92 installs/wk local only

Base Image Eol Lint

by jmshinhwa

Marks every base image in your Dockerfiles, compose files and CI workflows whose security patches ha

315 installs/wk local only

Stobox Intelligence & Tokenization

by stobox

Verified RWA tokenization knowledge — security tokens, regulation, standards — for any AI.

6 tools answering

MCP Code Review Server

by goodjobwilliam

Code review as an MCP server — structured reviews with OWASP security scanning.

122 installs/wk local only

Eleion Scanner

by hernaninverso

29 installs/wk local only

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 521 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 with the file path 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 521 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.