Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AngelBacked Angel Investors

REMOTE · WWW.ANGELBACKED.CO

Search 58,000+ angel investors and VCs by market and location, see portfolios, and reveal emails.

+2 this week 78 Trust /100

Last scanned (22 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 797 tokens (~159/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://www.angelbacked.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=angelbacked.co CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA256 907468aa258e6fd0134ffc7ccd05610d
SANs: angelbacked.co, *.angelbacked.co
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.angelbacked.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
angelbacked.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.angelbacked.co/api/mcp Verified 200
http (plaintext) http://www.angelbacked.co/api/mcp HTTPS enforced 308 https://www.angelbacked.co/api/mcp
MCP tools · 5 exposed · ~664 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
company_investors ~67

Angel investors in AngelBacked who backed a named company (exact company name, case-insensitive), most active first, up to 50. Use it to find investors who already back companies like yours.

NameTypeReqDescription
companystringyesCompany name, e.g. "Notion".

No output schema declared.

No examples provided.

get_investor ~80

Full profile for one investor by id or slug (from search results or an angelbacked.co/investor/<slug> URL): title, firm, location, markets, social links and up to 100 portfolio companies. No email; use reveal_investor_email.

NameTypeReqDescription
investorstringyesInvestor id (uuid) or profile slug.

No output schema declared.

No examples provided.

recent_funding_rounds ~151

Recent startup funding rounds tracked by AngelBacked Signals: company, date, stage, amount and industry, newest first. Filter by days back (max 180), industry and stage (e.g. "Seed", "Series A", "Pre-Seed").

NameTypeReqDescription
daysinteger–Lookback in days. Default 30.
industrystring–Industry, partial match (e.g. "Health").
pageinteger–Page number (1-20). Default 1.
per_pageinteger–Results per page (max 25). Default 25.
stagestring–Exact round stage, case-insensitive (e.g. "Seed").

No output schema declared.

No examples provided.

reveal_investor_email ~99

Reveal one investor's email address. Uses the account's email reveal allowance (the same one as the Reveal button on angelbacked.co; Annual: 500 per day, 3,000 per 30 days). Revealing an investor the account has already revealed is free. Only reveal investors the user intends to contact.

NameTypeReqDescription
investor_idstringyesInvestor id (uuid) from search_investors or get_investor.

No output schema declared.

No examples provided.

search_investors ~267

Search 58,000+ angel investors and VCs in AngelBacked. Filter by free text (name, firm, title), market/sector, location, or a company they backed. Returns id, name, title, firm, city/state/country, markets, portfolio_count, LinkedIn/Twitter/website, profile_url and has_email. Emails are not included: call reveal_investor_email for the investors you actually want to contact. Sorted by portfolio size.

NameTypeReqDescription
locationstring–City, state or country, partial match (e.g. "Austin", "California", "United Kingdom").
marketstring–Market/sector, partial match (e.g. "FinTech", "Artificial Intelligence", "SaaS").
min_portfoliointeger–Minimum number of portfolio companies (activity filter).
pageinteger–Page number (1-20). Default 1.
per_pageinteger–Results per page (max 25). Default 25.
portfolio_companystring–Only investors who backed this company (partial match, e.g. "Stripe").
querystring–Free text matched against name, firm and title (e.g. "former founder", "Sequoia").

No output schema declared.

No examples provided.

Install

How do I install the AngelBacked Angel Investors MCP server?

AngelBacked Angel Investors is a hosted endpoint at https://www.angelbacked.co/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.angelbacked.co

# add to Claude Code
claude mcp add --transport http co-angelbacked-angel-investors 'https://www.angelbacked.co/api/mcp'
Common questions

What is the AngelBacked Angel Investors MCP server?

AngelBacked Angel Investors is an MCP server listed in the public MCP registry as co.angelbacked/angel-investors. Search 58,000+ angel investors and VCs by market and location, see portfolios, and reveal emails. This page covers its hosted endpoint (https://www.angelbacked.co/api/mcp).

Is the AngelBacked Angel Investors MCP server safe to use?

AngelBacked Angel Investors scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AngelBacked Angel Investors MCP server expose?

AngelBacked Angel Investors exposes 5 tools: search_investors, get_investor, company_investors, reveal_investor_email, recent_funding_rounds. Their descriptions and schemas cost roughly 664 tokens of context every time the server is loaded.

Does the AngelBacked Angel Investors MCP server require authentication?

No. We connected to AngelBacked Angel Investors without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AngelBacked Angel Investors MCP server still maintained?

AngelBacked Angel Investors is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AngelBacked Angel Investors MCP server?

VerifyMCP ran 12 checks on AngelBacked Angel Investors, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about AngelBacked Angel Investors: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.