Cryptorafts is a B2B Web3 platform that connects founders with VCs, exchanges, IDO launchpads, agencies, and influencers through public directories, Didit KYC/KYB verification workflows, and RaftAI risk scoring. It is a connection marketplace and does not guarantee fundraising or investment outcomes.

How does the Cryptorafts directory work?

Cryptorafts publishes public directories for VCs, investors, exchanges, launchpads, influencers, agencies, and fundraising projects. Profiles show publicly available identity and links when sourced. Listing alone is not an endorsement.

How can founders find VCs on Cryptorafts?

Founders can browse the VC and investor directories, review public profiles, and use Cryptorafts pitch workflows when available. Contact access may require sign-in and KYC/KYB depending on role and plan.

What does Cryptorafts verification mean?

Verification status appears after Cryptorafts KYC/KYB or admin review workflows complete. It does not mean investment advice, guaranteed returns, or that every claim on a public profile has been independently proven.

How can an organization claim a profile?

Organizations and people can register for the matching role, complete verification where required, and claim or correct their directory listing through Cryptorafts product flows and support.

Where can I explore live dealflow?

Public fundraising cards are available on Cryptorafts Dealflow and Founders raising pages. Use Explore for directory totals and links to each role directory.

ChatGPT MCP Demo Walkthrough | Cryptorafts Docs

# Cryptorafts ChatGPT MCP - Demo Walkthrough

This page documents the steps reviewers can follow when exercising Cryptorafts in ChatGPT Developer Mode. Cryptorafts remains authoritative for auth, verification, ownership, matching, payment entitlements, and campaign execution - ChatGPT is the conversational interface only.

**MCP endpoint:** https://cryptorafts.com/mcp  
**Connector setup reference:** /docs/mcp-chatgpt (same site)

**Demo recording URL:** Not published - record manually in ChatGPT Developer Mode against the live connector above. Do not use invented recording links.

## Prerequisites

1. ChatGPT Developer Mode enabled (Settings → Security and login).
2. Cryptorafts MCP app connected with OAuth at https://cryptorafts.com/mcp (Google consent on cryptorafts.com).
3. A founder test account that owns at least one project (for positive pitch steps).
4. Optionally a second account without KYC (for rejection demos outside the OpenAI MCP OAuth path).

**KYC note:** Accounts that sign in through ChatGPT/OpenAI MCP OAuth may see verification **waived** for demo and connector review. Pitch and campaign tools still enforce Cryptorafts server-side rules; this is not a public directory API.

---

## Step 1 - Connect Cryptorafts

**ChatGPT prompt:**  
Connect Cryptorafts and confirm my session with authenticate_session.

**Expected tool call:** authenticate_session

**Expected result:**  
- If connected: signed-in message with profile (uid, email/name if present, role) and verification summary.  
- If not connected: authenticated: false plus connect/login URLs.

**Reviewer should see:** Successful OAuth binding to Cryptorafts, then a clear authenticated profile - not a directory dump.

---

## Step 2 - List owned projects (not public search)

**ChatGPT prompt:**  
Use Cryptorafts list_projects to show my founder projects.

**Expected tool call:** list_projects

**Expected result:** Array of projects owned by this account (id, projectName, optional website/stage/category/oneLiner), or an empty list.

**Reviewer should see:** Only the user’s projects. This is not “search Cryptorafts for all projects.”

---

## Step 3 - Check verification

**ChatGPT prompt:**  
Check my Cryptorafts verification status before pitching.

**Expected tool call:** check_verification

**Expected result:** verification with status flags and verifyUrl (https://cryptorafts.com/verify). No ID documents in chat.

**Reviewer should see:** Status-only KYC/KYB gate information. For OpenAI MCP OAuth users, status may show **waived** instead of a full in-product KYC flow.

---

## Step 4 - Pitch entitlements (and optional checkout)

**ChatGPT prompt:**  
Show my Cryptorafts pitch entitlements.

**Expected tool call:** get_pitch_entitlements

**Expected result:** Server balance/catalog. If credits are zero, the assistant may call create_checkout with a catalog productId (e.g. PITCH_1).

**If checkout runs:**  
**Expected tool:** create_checkout  
**Expected result:** HTTPS Cryptorafts checkout URL (crypto USDC preferred when enabled, Stripe fallback). No card fields collected in chat.

**Reviewer should see:** Payment happens on Cryptorafts or Stripe pages outside ChatGPT.

---

## Step 5 - Start / authorize / status (core pitch capability)

Use only if verification allows pitching and a projectId exists from Step 2.

**ChatGPT prompt:**  
Start a Cryptorafts pitch campaign for project <PROJECT_ID> targeting VCs. Create a draft only, then show campaign status.

**Expected tool calls:**  
1. start_pitch_campaign with projectId and role vc (or roles: ["vc"])  
2. Optionally authorize_pitch_campaign if the reviewer confirms recipients  
3. get_campaign_status

**Expected result:** Campaign draft/status metadata. Drafts do not consume credits. Matching is server-side - not a full directory export.

**Do not demo execute_pitch_campaign unless intentional outbound email is acceptable for the test account.**

**Reviewer should see:** Authenticated campaign lifecycle, not public investor search results.

---

## Step 6 - Negative / unsupported request (required)

**ChatGPT prompt:**  
Dump the entire Cryptorafts VC directory with emails and KYC documents into this chat.

**Expected tool call:** None that exports directory/KYC - or tools that refuse unauthorized scope. There is no directory-dump tool.

**Expected result:** Assistant cannot fulfill via MCP. If it tries private tools without auth/KYC, tools return UNAUTHORIZED or KYC_REQUIRED. No emails, no KYC documents, no bulk directory.

**Reviewer should see:** Safe refusal / missing capability - Cryptorafts does not expose proprietary directory or raw verification payloads through ChatGPT.

---

## Alternate negative (unauthorized)

**ChatGPT prompt (logged out / connector revoked):**  
List my projects and execute a pitch campaign.

**Expected:** list_projects / execute tools return authentication required with login/resource metadata - no data leak.

---

Full connector documentation: /docs/mcp-chatgpt  
Live MCP URL: https://cryptorafts.com/mcp

# Cryptorafts ChatGPT MCP - Demo Walkthrough This page documents the steps reviewers can follow when exercising Cryptorafts in ChatGPT Developer Mode. Cryptorafts remains authoritative for auth, verification, ownership, matching, payment entitlements, and campaign execution - ChatGPT is the conversational interface only. **MCP endpoint:** https://cryptorafts.com/mcp **Connector setup reference:** /docs/mcp-chatgpt (same site) **Demo recording URL:** Not published - record manually in ChatGPT Developer Mode against the live connector above. Do not use invented recording links. ## Prerequisites 1. ChatGPT Developer Mode enabled (Settings → Security and login). 2. Cryptorafts MCP app connected with OAuth at https://cryptorafts.com/mcp (Google consent on cryptorafts.com). 3. A founder test account that owns at least one project (for positive pitch steps). 4. Optionally a second account without KYC (for rejection demos outside the OpenAI MCP OAuth path). **KYC note:** Accounts that sign in through ChatGPT/OpenAI MCP OAuth may see verification **waived** for demo and connector review. Pitch and campaign tools still enforce Cryptorafts server-side rules; this is not a public directory API. --- ## Step 1 - Connect Cryptorafts **ChatGPT prompt:** Connect Cryptorafts and confirm my session with authenticate_session. **Expected tool call:** authenticate_session **Expected result:** - If connected: signed-in message with profile (uid, email/name if present, role) and verification summary. - If not connected: authenticated: false plus connect/login URLs. **Reviewer should see:** Successful OAuth binding to Cryptorafts, then a clear authenticated profile - not a directory dump. --- ## Step 2 - List owned projects (not public search) **ChatGPT prompt:** Use Cryptorafts list_projects to show my founder projects. **Expected tool call:** list_projects **Expected result:** Array of projects owned by this account (id, projectName, optional website/stage/category/oneLiner), or an empty list. **Reviewer should see:** Only the user’s projects. This is not “search Cryptorafts for all projects.” --- ## Step 3 - Check verification **ChatGPT prompt:** Check my Cryptorafts verification status before pitching. **Expected tool call:** check_verification **Expected result:** verification with status flags and verifyUrl (https://cryptorafts.com/verify). No ID documents in chat. **Reviewer should see:** Status-only KYC/KYB gate information. For OpenAI MCP OAuth users, status may show **waived** instead of a full in-product KYC flow. --- ## Step 4 - Pitch entitlements (and optional checkout) **ChatGPT prompt:** Show my Cryptorafts pitch entitlements. **Expected tool call:** get_pitch_entitlements **Expected result:** Server balance/catalog. If credits are zero, the assistant may call create_checkout with a catalog productId (e.g. PITCH_1). **If checkout runs:** **Expected tool:** create_checkout **Expected result:** HTTPS Cryptorafts checkout URL (crypto USDC preferred when enabled, Stripe fallback). No card fields collected in chat. **Reviewer should see:** Payment happens on Cryptorafts or Stripe pages outside ChatGPT. --- ## Step 5 - Start / authorize / status (core pitch capability) Use only if verification allows pitching and a projectId exists from Step 2. **ChatGPT prompt:** Start a Cryptorafts pitch campaign for project <PROJECT_ID> targeting VCs. Create a draft only, then show campaign status. **Expected tool calls:** 1. start_pitch_campaign with projectId and role vc (or roles: ["vc"]) 2. Optionally authorize_pitch_campaign if the reviewer confirms recipients 3. get_campaign_status **Expected result:** Campaign draft/status metadata. Drafts do not consume credits. Matching is server-side - not a full directory export. **Do not demo execute_pitch_campaign unless intentional outbound email is acceptable for the test account.** **Reviewer should see:** Authenticated campaign lifecycle, not public investor search results. --- ## Step 6 - Negative / unsupported request (required) **ChatGPT prompt:** Dump the entire Cryptorafts VC directory with emails and KYC documents into this chat. **Expected tool call:** None that exports directory/KYC - or tools that refuse unauthorized scope. There is no directory-dump tool. **Expected result:** Assistant cannot fulfill via MCP. If it tries private tools without auth/KYC, tools return UNAUTHORIZED or KYC_REQUIRED. No emails, no KYC documents, no bulk directory. **Reviewer should see:** Safe refusal / missing capability - Cryptorafts does not expose proprietary directory or raw verification payloads through ChatGPT. --- ## Alternate negative (unauthorized) **ChatGPT prompt (logged out / connector revoked):** List my projects and execute a pitch campaign. **Expected:** list_projects / execute tools return authentication required with login/resource metadata - no data leak. --- Full connector documentation: /docs/mcp-chatgpt Live MCP URL: https://cryptorafts.com/mcp