# Arphie
ID: 13-arphie
Page: https://gtmmcps.com/tools/13-arphie
JSON: https://gtmmcps.com/data/tools/13-arphie.json
Documentation references: https://gtmmcps.com/docs/13-arphie/
Category: Proposals & Deals
MCP support: official
Testing: RESEARCHED
API access: paid
Last checked: 2026-08-24
Endpoint check: not-probed; date: Not recorded

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

## MCP links

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

## Research notes
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. 2026-09-07: LAW 1 FLAG, NOT DOWNGRADED. A repo finder searched GitHub ("Arphie mcp", owners arphie and arphie-ai), npm, PyPI and the official MCP registry and found nothing, and probes of https://mcp.arphie.ai/ and https://mcp.arphie.ai/mcp did not answer an MCP initialize. What the official claim actually rests on: a pricing-tier mention on the vendor site, with no standalone MCP docs page - the finder called it the weakest official claim in the set. A human should decide whether it survives law 1. 2026-09-12 (P6-04 repo sweep): LAW 1 FLAG RE-CHECKED, STILL STANDS, STATUS DELIBERATELY NOT CHANGED because that decision was already handed to a human. Measured today: the vendor's own GitHub org is Arphie-AI, first-party on profile-site evidence (its profile site is arphie.ai), and it has 0 public repositories. The official MCP registry returns 0 servers for the search "arphie". A GitHub repository search for "arphie" returns only third-party work (xinxuxin/arphie, api-evangelist/arphie, heywood-dev/arphie-customer-health and similar), none of it Arphie's own. So there is still no URL of any kind behind this official claim, and this remains the only entry in the directory carrying official with nothing parseable in mcp_url. Under SCHEMA law 1 that reads unknown rather than official, and the change is a human's to make, not this pass's.

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: none-found

Read current vendor documentation before configuring or running commands.