POST /mcp is one route inside the God Mode API. It answers Model Context Protocol clients out of the tables /v1
already serves: twenty-six read-only tools, four resources and seven prompts. The tools run through the same plan
functions the REST handlers use. The same bearer key, the same credits, the same problem codes and the same terms of
use apply to them.
The five listing-agent and Investorlift-listing tools, the five lender tools and the prompt that walks the Investorlift
listings are in early access. While the developer tier is in beta, they are open to Investorlift’s team and trusted
partners. Investorlift will restrict them further before they open to every key.
This host does not serve the fields that identify a natural person, on any tool. Those fields are the people behind
an entity, their mailing addresses, the skip-trace targets and parcel owner identity. They also include listing
agents’ names, phones, emails and licence numbers. The borrowers on a mortgage, the parties to an involuntary lien and
the agent named on a listing cycle are also such fields.
Every tool names a registry investor by its registry name: name, the deed spelling, with display_name beside it
to print. That name can be a person’s when someone buys property in their own name. The candidate list a name lookup
returns carries those names, and a matched deed name that is a person’s comes back null. Answers are small by default,
and every one states the date the data ends.
Who it is for: anyone with a key. One user is a developer in Claude Code, Cursor or VS Code on a laptop. Another is an
agent built on the Claude Agent SDK or the Messages API connector, from any place it runs. Another is a product that
gives its own assistant the tools, in-cluster or not. The MCP Inspector is the smoke test. Every one of them uses the
same zpka_ key as /v1 and nothing else.
What it is not: it has no writes. Every tool carries the annotations read-only, non-destructive, idempotent and
closed-world, and nothing on the route can change a row. Cells and a lender’s place rankings are not tools: the map
endpoints, /v1/deals/cells and /v1/lenders/{id}/cells, and /v1/lenders/{id}/rankings stay on /v1.
The server does not geocode: an area is coordinates or a bounding box, never a street address. But the parcel lookup
takes a street address with its ZIP or city, and resolves it through the served address table. The parcel id it
returns centres a search. The server holds no session, pushes nothing and answers no browser.
Where it answers
The key is the same
zpka_ bearer key as /v1. Keys and headers explains what the key gets and how the
gateway attributes a call to you. The page Connecting a client has the entries for Claude Code, Cursor,
VS Code and curl. The twenty-six tools lists every tool with its inputs, and
Worked examples shows one call per tool.
A tools/call on a client that negotiates protocol 2026-07-28 costs what its route costs. That is one credit per
deal, investor or parcel new to your account, plus the tool’s base. A record already seen costs nothing while the plan
has credit. Every result reports the charge in meta.credits.charged, with used, line and period_end beside it.
So a client knows where the period stands after each call (Keys and headers). The API charges a legacy
client per call, refused or served (Plans and limits).
Two MCP servers, and which is which
Two servers exist, and they answer different questions. Both are read-only.
Point an assistant at the documentation server while you build the integration, and at the data server once it
works. You can add both: the questions do not overlap.
From the menu beside its title, you can copy every page of this site as Markdown. You can also open the page directly
in Claude, ChatGPT or Cursor.
Terms of use
Every result carriesmeta.terms, a one-sentence attribution that points at the API’s terms document.
Terms and attribution carries the same terms in full. They bind every consumer of this endpoint until
a signed agreement says otherwise.
In short, these are the terms. The data is public-record and MLS listing data licensed through BatchData, municipal
short-term rental registries and Investorlift marketplace records. Show the attribution line on
Terms and attribution where you show the data. Every value is current to the market’s as-of dates in
meta.coverage[], never to today. You can keep a result for the session in hand, or cache it against its
dataset_version within the cache window. That window is at most 30 days.
Drop a cached result within a business day after the version changes, and check the current version daily with
GET /v1/dataset or the X-Dataset-Version header. A result must not end up in a second database. Do not pass it on,
sell it, or make it training material. Names are public-record spellings that can be stale. Do not use anything here
for any purpose governed by the Fair Credit Reporting Act.
The one carve-out for MCP is the transcript: every result a client shows lands in its session transcript and in its
model provider’s logs. Use only a client and a provider account whose terms or settings bar the provider from training
on your inputs and outputs. The transcript can stay on a device you control for up to 30 days, and in the provider’s
systems for the provider’s stated retention. It is a record of the conversation, never a store to read the data back
out of or search. Send a request to remove a person to support@investorlift.com with the subject “Removal request”.
The Privacy notice says how Investorlift handles a request.