AdPerch

AdPerch over MCP

AdPerch is being built agent-native. Point your agent at the endpoint below, authenticate with a key you mint yourself, and work with your AdPerch record from wherever you already are — your own perch if you are a founder, your fund’s inbound if you are an investor.

The endpoint

https://mcp.adperch.ai

JSON-RPC 2.0 over POST. The same server also answers at https://app.adperch.ai/.netlify/functions/mcp-sse — mcp.adperch.ai is the durable address, so prefer it.

One call needs no key and no account, so you can check the server answers before you have either. describe_adperch is the “is anyone home” probe:

POST https://mcp.adperch.ai
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"tools/call",
 "params":{"name":"describe_adperch","arguments":{}}}

It answers with the standard envelope, carrying a JSON document that describes the product, its vocabulary, and the tools this server exposes:

{"jsonrpc":"2.0","id":1,
 "result":{"content":[{"type":"text","text":"{ … }"}]}}

That document is generated from the server’s own tool registry, so it describes whatever this server exposes at the moment you ask rather than whatever was written down.

Authenticating

Authorization: Bearer agent_key_<your key>

You mint a key yourself, in the app, under Account → MCP. It is shown once and stored only as a fingerprint, so it cannot be retrieved afterwards — copy it when you create it. You can revoke it at any moment, and revocation takes effect immediately.

There is one kind of key, and what it reaches is decided by what your account already is — the same reach you have signed in. An account that owns or holds an active seat on a fund reaches that fund’s side. A founder with a perch, on the Founder or Co-founder Matching plan, reaches their own perch, matches and pipeline. On Community Plus — a plan offered inside the app to free accounts — the key reaches your own perch and conversations, but never the fund side: fund matches, your pipeline and applications are refused and left out of tools/list. An account on co-founder matching reaches the co-founder tools. An account that is more than one of those reaches all of them on the one key, and tools/list is filtered to it. If your account is none of them, the page says which door is missing instead of offering a key that could only ever come back empty.

Most clients take a server block in their config. Substitute your own key for the placeholder — the prefix is part of the key, not something you add:

{
  "mcpServers": {
    "adperch": {
      "url": "https://mcp.adperch.ai",
      "headers": { "Authorization": "Bearer agent_key_<your key>" }
    }
  }
}

Clients differ in where that file lives and in whether they read headers under this exact name; the two things that do not vary are the address and the header itself, both above.

What a key can do

describe_adperch is public — every other tool needs a key, and which ones you see depends on what your key reaches.

On a fund key

describe_adperch — public server discovery. No account, no key, no perch data. The “is anyone home” probe.
list_my_funds read:pipeline — the funds this key can read: every fund you own or hold an active seat on.
list_submitted_applications read:pipeline — applications founders have submitted to a fund you own or hold a seat on, newest first. Founders matched to that fund who have not applied are a different set and are not returned.
list_founders_fitting_criteria read:pipeline — founders whose stage and sector fit the criteria of a fund you own or hold a seat on, ranked by sector focus, returned a page at a time. Card-only: company, stage, sectors, a short pitch, and whether they are actively raising — no founder name and no contact details. These founders have not applied to you.
get_founder_application read:application — one submitted application in full, from the applications made to your fund.
read_my_fund · list_my_board · read_supplementals read:funds / read:pipeline — your fund’s own perch, the founders matched to its criteria, and its supplemental material.
track_founder · untrack_founder · update_vc_pipeline · update_fund_thesis · greenlight_founder — the fund-side actions you could take by hand. untrack_founder archives a match rather than deleting it, and is recoverable in the app under “Show archived” — there is no way back from here.

On a founder or co-founder-matching key

list_my_perches · read_my_perch read:perch — your own perch in full: what you are building, your stage and sectors, your raise.
list_my_matches read:matches — funds that FIT your perch, computed fresh from your stage and sectors each time you ask. Suggestions, not a board: nothing is stored, and a fund appearing here does not mean you have engaged it.
list_my_pipeline read:matches — funds ON your Pipeline board: the ones you are actually working, with where each stands, when it last moved, your notes, your next step and whether you starred it. Each row carries the match_id that update_pipeline and greenlight_match need. A fund arrives here once you or it has acted.
list_my_chats read:chats — who each conversation is with and when it last moved. Never the message text: bodies are encrypted and no key can read them.
list_cofounder_interests read:cofounder — your co-founder matches, mutual only. One-sided interest is never returned, in either direction.
update_my_perch · update_pipeline · dismiss_fund · archive_application — the reversible edits you could make by hand.
submit_application · withdraw_application · greenlight_match — one-way. See Before you use this for anything real below.
express_interest · withdraw_interest · archive_match · pause_matching · resume_matching · save_my_entry — co-founder matching.

Never more than you can already do signed in. A key reaches exactly one account’s record — your own perch, or the funds you own or hold an active seat on — and nothing beyond it. It cannot read another founder’s record, it cannot reach a fund you have no seat on, and if your seat ends the key stops with it. Fund-side reads stay card-only: company, stage, sectors, a short pitch, and whether a founder is actively raising — no founder name and no contact details — and there is no fund-wide search and no directory of founders. A criteria fit is not an introduction; a name is disclosed only where a match already exists.

It writes. Every write is an action you could take by hand on your own record, and none of them reaches anyone else’s.

tools/list is the authority on what exists, and it is filtered to the key you present — a founder key lists the founder tools, a fund key lists the fund tools, and a key that is both lists both. This page describes every set in prose and can lag the server; if the two disagree, believe the server.

Before you use this for anything real

Set the one-way tools to ask first, in your client. Four actions cannot be undone — submit_application, withdraw_application, greenlight_match and greenlight_founder. Each of them refuses unless the call passes confirm: true.

That guard stops a malformed call. It does not stop an agent. The parameter is documented in the tool’s own schema as required, so an agent asked to greenlight something will read that and set it — correctly, and without being told. For a person a confirmation is a decision; for an agent it is one more field to fill in.

So the real control is your client’s, not ours. Most MCP clients let you set a tool to ask before running — in Claude that is the tool-permissions panel on the connector. Set those four to ask, and leave the reads and the reversible writes alone.

Which clients can use a key today

AdPerch authenticates with a bearer token in an Authorization header. Any client that can send a fixed header works:

Claude Code, Cursor, and most agent frameworks — a server block in the config, with the key in headers. The snippet above is that block.
claude.ai custom connectors — choose Authentication: None, then add a request header Authorization: Bearer <your key>. ⚠ The Request headers section is in a limited beta. If you do not see it, claude.ai cannot use an AdPerch key yet — the dialog will only offer OAuth, which this server does not speak. That is a client limitation, not a problem with your key.

A one-click sign-in that removes the key-pasting step is the intended destination. It is not the current state, and this page will say so until it is.

The gate

The endpoint is real and its gate is a switch, not a date. A launched beta does not open it and does not close it either.

initialize and tools/list answer whichever way the switch is set.
tools/call returns KILL_SWITCH_ACTIVE_MASS in a 503 while the switch is shut, and serves normally while it is open.
An unregistered tool name returns JSON-RPC -32601 Unknown tool inside a 200. That is the registry answering, not a fault, and it is true in every switch state.

Ask the server, not this page. Call describe_adperch — it reports the gate's position at the moment you ask, derived from the switch itself. Any page that printed the answer would be wrong the first time the switch moved, and would not know it.

Getting access

If you run a fund: claim your perch at adperch.ai/claim. No invite is needed and no account is required to start — you ask, we verify it against the firm's own domain, and the claim link comes back to an address there. Once the claim is approved, the key is two clicks away in Account → MCP. Investors are free; there is no plan to buy.

If you are a founder: the key lives in the same place — Account → MCP — once you have a perch and the Founder, Co-founder Matching or Community Plus plan (beta and comp accounts too). Community Plus is offered inside the app on a free account, and its key stops short of fund matching. The tab is there either way and explains itself; without a plan it says so and links you to Plan & Billing rather than showing a button that would refuse.

If you are building something else against this and want to talk about it: contact@adperch.ai.

Machine-readable version of all of the above: adperch.ai/llms.txt.