_ registry / mcp streamable-http · checked 53m ago

angelbacked

https://www.angelbacked.co

Registry code: 8e32760422d37b91

api record

AngelBacked: 58,000+ angel investors and VCs with markets, locations, portfolios and verified emails, plus recent funding rounds. Typical flow: search_investors (or company_investors) to build a shortlist, get_investor to check fit, then reveal_investor_email only for investors the user will actually contact. Results are 25 per page, fair-use limited (150 requests/day); refine filters rather than paging through everything. Requires an AngelBacked Annual API key (https://www.angelbacked.co/profile?tab=api). Docs: https://www.angelbacked.co/mcp

endpoint
https://www.angelbacked.co/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is angelbacked live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is angelbacked free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does angelbacked have?
5 tools: company_investors, search_investors, get_investor, reveal_investor_email, recent_funding_rounds.
Is angelbacked safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
445ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 auth-required 5 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • company_investors auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company name, e.g. \"Notion\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_investors auth-required 52m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Page number (1-20). Default 1."
        },
        "query": {
          "type": "string",
          "description": "Free text matched against name, firm and title (e.g. \"former founder\", \"Sequoia\")."
        },
        "market": {
          "type": "string",
          "description": "Market/sector, partial match (e.g. \"FinTech\", \"Artificial Intelligence\", \"SaaS\")."
        },
        "location": {
          "type": "string",
          "description": "City, state or country, partial match (e.g. \"Austin\", \"California\", \"United Kingdom\")."
        },
        "per_page": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Results per page (max 25). Default 25."
        },
        "min_portfolio": {
          "type": "integer",
          "minimum": 0,
          "description": "Minimum number of portfolio companies (activity filter)."
        },
        "portfolio_company": {
          "type": "string",
          "description": "Only investors who backed this company (partial match, e.g. \"Stripe\")."
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • get_investor auth-required 52m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "investor"
      ],
      "properties": {
        "investor": {
          "type": "string",
          "description": "Investor id (uuid) or profile slug."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • reveal_investor_email auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "investor_id"
      ],
      "properties": {
        "investor_id": {
          "type": "string",
          "description": "Investor id (uuid) from search_investors or get_investor."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • recent_funding_rounds auth-required never probed

    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").

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 180,
          "minimum": 1,
          "description": "Lookback in days. Default 30."
        },
        "page": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Page number (1-20). Default 1."
        },
        "stage": {
          "type": "string",
          "description": "Exact round stage, case-insensitive (e.g. \"Seed\")."
        },
        "industry": {
          "type": "string",
          "description": "Industry, partial match (e.g. \"Health\")."
        },
        "per_page": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Results per page (max 25). Default 25."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8e32760422d37b91.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8e32760422d37b91/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8e32760422d37b91/badge.svg)](https://brick.blue/agent/8e32760422d37b91?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.