Arphie

Official MCP Paid, self-serve Proposals & Deals RESEARCHED Checked 2026-08-24

RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0.

Vendor: arphie.ai · entry id 13-arphie · source 13-proposals-deals.md line 204

What it does

AI-native RFP/RFx/security-questionnaire response software, positioned as a faster-drafting alternative/competitor to Loopio and Responsive.

AI features, separated from automation with an AI label on it

Core product is explicitly AI-drafting-first (auto-answering RFP/questionnaire content from a knowledge base) - the category's newer, "AI-native" entrant rather than an established platform with AI bolted on; depth of the underlying model not independently verified.

RevOps role

AI-native RFP response layer, direct competitor to Loopio and Responsive, differentiated mainly on drafting speed and a transparently usage-priced MCP tier.

MCP server

Status bucket

Official MCP

Auth

unknown

Parsed URLs

0 found in the mcp_url field

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-08-24 and has not been re-fetched since.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

referenced via pricing/product pages describing an "Arphie MCP" plan; no distinct standalone MCP docs URL or GitHub repo was independently located beyond the pricing mention - treat with the same caution as DealHub's entry above, logged as official on the strength of a specific named, priced product line rather than a confirmed public technical spec.

Access gate

Gate bucket

Paid, self-serve

Can a solo operator reach it

Yes, by paying, no sales call

api_gate, verbatim from the file:

paid, usage-based for MCP specifically. Core RFP platform uses "concurrent project-based" custom pricing (charges scale with how many RFPs/questionnaires are active at once, not per-seat) with no published rate card. The MCP plan specifically is priced at $50/month plus $0.05 per answered question - notably the same $50/mo base as Responsive's MCP pricing, suggesting a shared MCP-hosting/billing pattern across RFP vendors worth investigating further.

API documentation

No documentation URL recorded.

263 of 293 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

Jobs it can do

Draft an RFP or questionnaire response

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.

Sources

3 source URLs. Raw sources field, verbatim:

https://www.arphie.ai/, https://autorfp.ai/blog/arphie-pricing, https://www.arphie.ai/blog/best-ai-tools-rfx-response-automation-software

Notes, verbatim from the file

FLAG: the "$50/mo + per-answer usage" MCP pricing pattern appearing identically at both Responsive and Arphie (two direct competitors) is worth a dedicated follow-up - either a coincidence, a category-wide pricing convention, or both vendors reselling the same underlying MCP-hosting infrastructure.

Provenance

Entry id

13-arphie

Source file

13-proposals-deals.md

Source line

204

Tier

RESEARCHED

last_checked

2026-08-24

Data baked

2026-08-25

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.