RFP & Contract Requirements Extractor MCP avatar

RFP & Contract Requirements Extractor MCP

Pricing

from $0.01 / 1,000 results

Go to Apify Store
RFP & Contract Requirements Extractor MCP

RFP & Contract Requirements Extractor MCP

Extract cited RFP and contract checklists, deadlines, evaluation criteria, and obligations from PDF URLs, web pages, or pasted text. Automated extraction only; verify against the source.

Pricing

from $0.01 / 1,000 results

Rating

0.0

(0)

Developer

Jordan C

Jordan C

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

4 days ago

Last modified

Categories

Share

An MCP server that deterministically extracts actionable RFP and contract terms from pasted text or public PDF/HTML/plain-text URLs. Every output includes source evidence and a location approximation. It does not use an LLM.

Tools

All tools accept exactly one of text or sourceUrl, plus optional maxItems (default 50, maximum 200). URL documents are limited to 10 MB and extracted text/pasted text to 1,000,000 characters.

ToolOutput
extract-rfp-checklistSubmission/compliance requirements with category, mandatory signal, evidence, and line location.
extract-rfp-deadlinesCalendar dates and relative deadlines, related action, evidence; unambiguous calendar dates are normalized to ISO YYYY-MM-DD.
extract-evaluation-criteriaEvaluation/scoring criteria with percentage weights when stated.
extract-contract-obligationsParty-agnostic obligation, notice, renewal, termination, payment, and security terms.

PDF URLs are downloaded with Axios as an array buffer and parsed with pdf-parse; HTML URLs are converted to visible text with Cheerio. Scanned or protected PDFs without an extractable text layer return a helpful error.

Important limitations

Extraction uses deterministic regex and section heuristics. It is automatically extracted information, so verify every item against the supplied document. The contract-obligations tool is not legal advice and does not make legal conclusions.

Run locally

npm install
npm run build
npm test
npm run start:dev

The Streamable HTTP MCP endpoint is http://localhost:3000/mcp (or APIFY_CONTAINER_PORT). The root route responds to Apify standby readiness probes.

Billing

Each MCP tool invocation calls await Actor.charge({ eventName: 'tool-call' }). Configure the matching tool-call pay-per-event entry in Apify before publishing.