AngelList

Name: AngelList MCP Server
Availability: InStock
Author: AngelList

Finance28 tools

Query capital accounts, capital calls, distributions, financial statements and fund documents from your AI assistant. The directory record carries a rare full-paragraph read-only disclosure — and unlike the last paragraph this catalogue tested, it holds up under four independent checks, including sixteen OAuth scopes that are every one of them read scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect AngelList via MCP

https://mcp.angellist.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

AngelList Tools & Capabilities (28)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

Read-only is verified for this build, and AngelList says it will change. The vendor states write access comes next, with the assistant preparing an action for human approval. Diary a re-check rather than treating the current posture as permanent.
GPs only, and only funds administered on AngelList. AngelList states the product is not for LPs, and that it queries the records a fund runs on AngelList. A fund administered elsewhere has nothing for this connector to read.
Vehicle coverage is incomplete. AngelList states that at launch the vast majority of SPVs including roll-up vehicles and most venture funds are supported, while financial data for rolling funds, scout funds and remaining vehicles arrives progressively before the end of 2026. A vehicle that is not yet covered will not announce itself in an answer.
Data refreshes daily, not in real time. AngelList states this explicitly. A figure pulled today may not reflect a movement booked this morning.
Where download_document puts a file is undocumented. Marketing describes download links, which implies a URL, but no signing, expiry or session requirement is published, and no response schema exists. Ask AngelList through the Trust Portal if this matters to your diligence.
A GP's connection reaches their LPs' personal financial records. That is by design and within existing entitlements, but the third parties in those records did not choose the AI client. Vendor guidance places the AI client's own data handling outside AngelList's boundary and calls it the biggest exposure.
No tool is annotated. The endpoint returned 401 to an anonymous request on 2026-08-19, so no inputSchema, readOnlyHint or destructiveHint was readable for any of the 28 tools. The read-only finding rests on scope metadata and vendor statements, not annotations.
AngelList names no tools. There is no vendor tool reference, so the 28 names here come from Anthropic's snapshot alone and cannot be cross-checked against the vendor.
The published documentation URL is a help-centre root. The directory's documentation field points at https://help.angellist.com/, which carries no MCP content; the real articles are reachable only by searching the help centre.
The two OAuth metadata documents disagree in scope vocabulary. The protected-resource descriptor lists sixteen resource scopes; the authorization server lists three OIDC identity scopes. They describe different layers, but a reader checking only the RFC 8414 document would conclude, wrongly, that no resource scopes are declared.
AngelList disclaims the output. Its launch post states responses are for general informational purposes only, do not constitute legal advice, and may be incomplete, outdated, inapplicable or contain errors, and advises consulting counsel before acting. We carry that unsoftened.
Prompts are unconfirmed. Anthropic's 2026-08-16 snapshot lists none, and the gated endpoint blocked our own check.

Frequently asked questions

Is the AngelList MCP server really read-only?

Yes, today. Four independent checks agree: the directory paragraph, AngelList's security page, the product FAQ, and the OAuth descriptor whose sixteen scopes all end in :read. But AngelList states plainly that write access is coming next, with the assistant preparing an action for a human to approve. The claim is verified for this build, not permanently.

Can LPs use AngelList Link, or is it only for fund managers?

General partners and their teams only. AngelList answers this directly in its product FAQ, stating the product is not for LPs and that limited partners continue receiving statements and documents as they do now. Your fund must also be administered on AngelList — the connector queries the records AngelList itself holds, not an external fund administrator's system.

What does download_document do, and where does the file end up?

It retrieves a fund document, and AngelList's marketing describes results grouped by vehicle with download links. That wording points to a URL rather than an inline file, but AngelList publishes no tool reference, so the return shape is not documented. Whether the link is signed, how long it lives, and whether it requires a session are all unstated.

Does connecting as a fund manager expose my LPs' personal financial records?

Yes, within your existing entitlements. AngelList states the connector reaches investor and LP records you administer, and eleven of the twenty-eight tools address partner-level data — capital accounts, subscriptions, distributions and partner lists. Those individuals are third parties who never agreed to an AI connector. The connector adds no new access; it adds a new destination for data you could already see.

What OAuth scopes does the AngelList MCP server request?

Sixteen named scopes, and every single one ends in :read. The RFC 9728 descriptor lists them with human-readable descriptions covering vehicles, capital accounts, capital calls, distributions, documents, financial statements and more. No write scope is advertised anywhere. This is the strongest wire-level corroboration of a read-only claim this catalogue has recorded.

Does AngelList document more MCP tools than Anthropic's directory lists?

No — it documents none by name. AngelList's two published MCP articles describe data categories such as firms, vehicles, capital accounts and documents, but never name an individual tool. The twenty-eight names on this page come from Anthropic's directory snapshot alone. That inverts the usual gap: the listing is the only tool-level source that exists.

Sources

Get AngelList Link — https://help.angellist.com/hc/en-us/articles/47546984470669-Get-AngelList-Link (fetched 2026-08-19 via the Zendesk help_center article search JSON API, which returns clean article text; article updated_at 2026-07-28. Source of the setup instructions per client, the data-category list, the mcp-remote fallback, the OAuth 2.1 with dynamic client registration statement, and the six example prompt workflows used for the vocabulary decoder and use cases) · retrieved 2026-08-19
AngelList Link Data & Privacy — https://help.angellist.com/hc/en-us/articles/47543225581965-AngelList-Link-Data-Privacy (fetched 2026-08-19 via the same JSON API; article updated_at 2026-07-23. Source of the read-only can/cannot lists, the same-infrastructure entitlement statement, "investor and LP records you administer", SOC 2 Type II, TLS in transit, and the guidance naming the AI client's own data handling as the biggest exposure) · retrieved 2026-08-19
AngelList help centre article search — https://help.angellist.com/api/v2/help_center/articles/search.json?query=MCP (fetched 2026-08-19; returned exactly two MCP articles, which is the basis for the claim that AngelList publishes no tool reference) · retrieved 2026-08-19
AngelList Link launch post — https://www.angellist.com/blog/introducing-angellist-link (fetched 2026-08-19; source of "Is this for LPs? No", the read-only-today statement, the coming write-access-with-approval statement, the K-1 PDFs and "download links" phrasing, the daily-refresh statement, the vehicle coverage rollout, and the output disclaimer) · retrieved 2026-08-19
AngelList Link product page — https://www.angellist.com/link (fetched 2026-08-19; corroborates GP-only availability, daily financial refresh and the source-document verification workflow) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor — https://mcp.angellist.com/.well-known/oauth-protected-resource (fetched 2026-08-19; 200, sixteen :read scopes with a scope_descriptions gloss for each, authorization_servers naming https://auth.angellist.com, EdDSA under resource_signing_alg_values_supported. The path-append form at /.well-known/oauth-protected-resource/mcp returns a byte-identical body with a matching weak etag; the path-insert form at /mcp/.well-known/oauth-protected-resource returns 404 with a text/plain body) · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — https://auth.angellist.com/.well-known/oauth-authorization-server (fetched 2026-08-19; PKCE S256, registration_endpoint for dynamic client registration, two grant types, and scopes_supported of openid, email, profile only. Both .well-known forms on the MCP host return 404) · retrieved 2026-08-19
Anonymous initialize probe of https://mcp.angellist.com/mcp (2026-08-19; HTTP 401 with a JSON token_missing error body and a www-authenticate challenge naming the root-form resource_metadata URL. No authentication was attempted and no tool was called) · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/dde63f10-f6b0-4246-a87c-a7cc62ce81b7 (snapshot 2026-08-16; source of the 28 tool_names, the empty prompt_names array, the permissions paragraph, the partner tier, the categories and the documentation root URL. The 1,434-of-1,897 permissions count was computed from this snapshot on 2026-08-19) · retrieved 2026-08-16