mcpbeat

Skipshit MCP Server

com.skipshit/mcp
answering

Skipshit is answering right now. Last checked moments ago. It exposes 3 tools.

People and property search for Claude and ChatGPT. Phones, emails, addresses, relatives, properties.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
3
Tools
read from the server
252 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.skipshit.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.skipshit.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.skipshit.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.skipshit.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.skipshit.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

expand
expand_person_record
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).
history
get_search_history
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.
person
search_person_or_address
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).

Endpoints

URLTransportStateLatencyChecked
https://mcp.skipshit.com/mcp streamable-http answering 352 ms 0 min ago

Skipshit — questions

Answers built from our own checks of this server.

What can Skipshit do?
It exposes 3 tools, read directly from the server on our last check. Among them: expand_person_record, get_search_history, search_person_or_address. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Skipshit working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 252 ms. The bar chart above shows every period we have measured.
Is Skipshit still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Skipshit?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Skipshit need an API key?
No. Skipshit completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Skipshit?
It answers our handshake in 252 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.