Moonfare vs Titanbay: API, MCP and investor access compared

Key differences

• Email notifications. Moonfare: available. Titanbay: not documented.
• Capabilities. Listed for Moonfare only: Performance; listed for Titanbay only: NAV.
• Regions. Listed for Moonfare only: North America, Asia Pacific and Middle East.
• Asset classes. Listed for Moonfare only: Venture capital.
• MFA methods. Moonfare lists: authenticator app and SMS; none recorded for Titanbay.

What the entries have in common

• API: both are recorded as partner only (for partner users).
• Neither offers an MCP server, according to the registry.
• Neither entry documents SFTP or webhooks.
• Investor-side API: not offered for either, according to the assessment.
• Difficulty: both are rated 4 of 5 (web login only, exports possible).
• Export formats: both list PDF.
• Automation policy: unknown for both.
• Known deployments: none documented for either yet.

Which fits which need

Neither product is right for every team. The statements below are conditional and come straight from the registry fields above.

For investors and LP operations teams

• If your investors or your operations team need documents and data through an API, the registry records the API as partner only (aimed at partner users) for both. Access for the investor itself is recorded as not offered for either.
• If you want to reach the data from an AI assistant, the MCP server is not offered for either.
• If you process capital call and distribution notices from your inbox, email notifications are available for Moonfare and not documented for Titanbay.
• If you load files into your own systems, the registry lists PDF for both.
• If you plan to automate your own login, automation in the terms is unknown for both. Where it is prohibited or unknown, ask the GP or the vendor for a sanctioned channel first.

For GPs, fund administrators and buyers

• If you need to connect the product to your back office, both entries record API partner only, webhooks not documented and SFTP not documented.
• If the product must carry the core LP reporting items (capital calls, distributions, capital account statements and tax documents), the structured capabilities cover capital calls and distributions for both.
• If your investors are concentrated in particular markets, the regions recorded are Europe, DACH, UK, North America, Asia Pacific and Middle East for Moonfare and UK, Europe and DACH for Titanbay.
• If you manage a specific strategy, the asset classes recorded are private equity, venture capital, private credit, infrastructure and fund of funds for Moonfare and private equity, private credit, infrastructure and fund of funds for Titanbay.
• If you want to see who already runs each product, the registry has no documented deployments for either yet. Operators can add theirs to the registry.
• If your investors will want programmatic access later, the difficulty rating is 4 of 5 for both, where 1 is a documented self-serve API an investor can use and 5 is web login only with MFA.

For a structured shortlist beyond these two products, see the guide how to choose an investor portal.

What the research says

Moonfare

Assessment. Default 2FA web login; partner API only for distributing institutions (marketing claims, no docs); investor gets PDFs and email notices.

Research notes. Confidence: high on default 2FA (vendor security page). Medium on partner API (vendor marketing pages, no docs). Partner models: client-directed, advised (POA) and nominee, so delegates can see investments via partner access rather than an investor API. Digital Reporting and quarterly reports appear in the web app 3-6 months after first capital call. No investor-side API, export beyond PDF unknown. Terms of use page not retrievable (404 at tested URLs); automation policy unknown.

• Web: Security page: 2FA enabled by default; app-based 2FA (e.g. Google Authenticator) recommended, implying SMS default. SSO described only for employees.
• API: Institutional pages advertise 'API integration' and white-label for wealth managers, banks, neo-banks and fintechs to offer PE on their own platform; no public docs, base URL or auth published. Fund admin fundcraft integrated via API (press, 2024-2026).
• MCP: None found in MCP registry/GitHub as of 2026-11-07.
• Email: Capital call and quarterly report notifications by email (marketing pages); not verified in help docs.

Sources: www.moonfare.com/security · www.moonfare.com/institutions-type-wealth-manager-and-bank · www.fundcraft.lu/?p=1965

Titanbay

Assessment. B2B infrastructure with API/FIX/SWIFT connectivity claimed in press releases for banks and wealth managers; no public docs; end investor accesses via distributor.

Research notes. Confidence: medium that partner integrations (API/FIX/SWIFT) exist (press-release and Wealth Mosaic profile evidence, weaker than docs). Heads of Germany and Switzerland appointed 2026 (DACH expansion). No investor-side API; access is via the distributing bank/wealth manager. Terms not reviewed.

• Web: B2B2C: white-labelled platform for private banks, wealth managers and MFOs (Wealth Solutions); fund dashboard covers onboarding, capital calls, NAVs, reporting. End-investor login details not published.
• API: Press releases (2026) state 'standard connections via API, FIX, or SWIFT' for banks/wealth managers; vendor site shows FIX 5.0 in TradeEngine. No public developer docs.

Sources: www.titanbay.com/ · www.thewealthmosaic.com/vendors/titanbay/titanbay-wealth-solutions/ · www.fintechfutures.com/press-releases/titanbay-appoints-julius-kolberg-as-head-of-germany

Frequently asked questions