Direct answer: Apify's hosted MCP server lets compatible clients discover and run Apify Actors, then retrieve their outputs. Aurora's catalog points to the official endpoint, so a verified connection can support scoped public-web investor or company research when the team chooses the Actor, respects source terms, reviews cost, and treats every result as evidence to verify rather than a fact to import automatically.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Apify remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
How the Apify connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.apify.com |
| Authentication and transport | Provider OAuth through Aurora; Streamable HTTP |
| Source of truth | Apify remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Search Apify Store for an Actor suited to a clearly defined research source and task.
- Run an approved Actor with reviewed inputs and retrieve its structured output from the hosted MCP endpoint.
- Collect public source URLs, page fields, and timestamps for a research dossier.
- Prepare a source-linked company or investor research summary without claiming universal coverage or accuracy.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Apify
Public investor-thesis research
Outcome: A source-linked evidence set for checking a fund's publicly stated stage, sector, geography, and recent activity.
- Define the approved public sources and select an Actor whose behavior and terms fit those sources.
- Run a narrow job for the named fund or investor and preserve source URLs and retrieval times.
- Compare extracted claims with the original pages and present contradictions or missing evidence.
Human decision: A researcher approves the source list, Actor, cost, and any claim used for targeting or outreach.
Company landscape research for a relationship brief
Outcome: A current public-web snapshot that complements private relationship memory without overwriting it.
- Specify the company, allowed domains, fields, and maximum run scope.
- Run the approved Actor and retain the result set with source receipts.
- Draft a comparison of public facts and existing private context, clearly labeling each source.
Human decision: A person verifies identity and source evidence before the information enters Finta or shapes contact strategy.
How to connect Apify to Aurora
- Select Apify from Aurora's catalog and complete the provider OAuth flow.
- Confirm the Apify account, workspace, spending controls, and Actors available to the user.
- Choose a low-risk Actor and inspect its input schema, data sources, pricing, and terms.
- Run a small test against an approved public page and retrieve structured output.
- Review the original source before using or storing any extracted result.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Aurora should not select an arbitrary scraper, bypass access controls, or run broad collection by default. A person must approve the Actor, sources, terms, inputs, scope, expected cost, and destination of the output. CRM writes and outreach remain separate approved actions.
Limitations to understand
- Actor quality, source coverage, pricing, runtime, and maintenance vary by provider and individual Actor.
- Web content can be stale, ambiguous, duplicated, wrong, or restricted by source terms and privacy law.
- Long-running jobs can time out or require later output retrieval.
- The page must not promise LinkedIn scraping, legal compliance, complete investor data, or automatic CRM enrichment.
Verification checklist
- Confirm https://mcp.apify.com and oauth_dynamic in the live catalog.
- Complete OAuth in a controlled Apify account with spending limits.
- Discover Actors and inspect the exact Actor selected for the page proof.
- Run a narrow test against an approved public source and record cost, runtime, and output schema.
- Compare at least one extracted fact with the original page and preserve its URL.
- Confirm no public copy implies universal source access, automated outreach, or unreviewed CRM writes.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- Apify official MCP documentation (docs.apify.com)
- Apify official MCP documentation 2 (docs.apify.com)