mcp server
mcp
People and property search for Claude and ChatGPT. Phones, emails, addresses, relatives, properties.
Description as published by the maintainer. Source
- version 1.0.1
- archived
- retrieval
archived — The linked repository returns 404. It was deleted, renamed or made private. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
expand_person_record(pid, searchId)- Expand a person id into its full record. If you pass the searchId of a prior result that already contains the id, the record is returned free. A credit is charged only when elevating a stub id (a relative, associate, or property owner) that no prior result contains. The response meta.source reports whether the record came from cache (free) or fresh (billed). Required: pid.
get_search_history(pid, limit, offset, searchId)- Free detail-expander for prior results, and the way to check the current credit balance. Four call modes: (1) no args → list recent searches and return current credit balance in the response envelope (use this when the user asks how many credits they have left); (2) `searchId` → re-read trimmed envelope; (3) `searchId + pid` → full record for one hit; (4) `searchId + offset + limit` → paged slice of full records (default limit 5, max 25). Use this for follow-ups on existing results — do NOT call `search_person_or_address` again to drill in. Zero credits consumed.
search_person_or_address(zip, city, state, address, lastName, firstName, middleName, addressRecency, nicknameSearch)- Returns contact and property records for a person (by name with city/state/zip) or by address. Billed 1 credit per non-null result; empty results are not billed. Results are trimmed per-hit summaries; expand individual records or page through full results with `get_search_history` (free).
Last successful function declaration observed on . Source: https://mcp.skipshit.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.skipshit.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-30 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-30 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | not_found | GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. | as of fetch | GitHub | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.skipshit.com | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | mcp.skipshit.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json