com.skipshit/mcp
REMOTE · MCP.SKIPSHIT.COM
People and property search for Claude and ChatGPT. Phones, emails, addresses, relatives, properties.
Available components
Last scanned (21 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.skipshit.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=skipshit.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5e235588dd90c1013460b404007547d |
| SANs: skipshit.com, mcp.skipshit.com, *.mcp.skipshit.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.skipshit.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| skipshit.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.skipshit.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.skipshit.com/mcp | HTTPS enforced | 301 | https://mcp.skipshit.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
expand_person_record Expand Person Record ~197
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).
| Name | Type | Req | Description |
|---|---|---|---|
| pid | string | yes | Person identifier from a prior result. Pass it with searchId to re-read an already-owned record free; pass it without searchId (or for a stub id no stored result contains) to elevate it into a full r… |
| searchId | string | – | Optional. The searchId from a prior result that already contains this pid. When provided and the record is found in your stored results, the full record is returned free (no credit); otherwise a cred… |
| Name | Type | Req | Description |
|---|---|---|---|
| balance | – | yes | – |
| data | – | – | – |
| error | object | – | – |
| meta | object | yes | – |
| ok | boolean | yes | – |
No examples provided.
get_search_history Search History & Detail ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (1-25). Default depends on mode: 20 for list-mode, 5 for paged-slice mode. |
| offset | integer | – | Zero-based offset for pagination. Used with limit in paged-slice mode (searchId + offset/limit). |
| pid | string | – | Person identifier within a stored search. Pass with searchId to expand that one record from the stored result to its full form. Free. |
| searchId | string | – | Identifier from a prior search response (meta.searchId). Pass alone to re-emit the trimmed envelope; pass with pid for full-record expansion; pass with offset/limit for paged full records. All four m… |
| Name | Type | Req | Description |
|---|---|---|---|
| balance | – | yes | – |
| data | – | – | – |
| error | object | – | – |
| meta | object | yes | – |
| ok | boolean | yes | – |
No examples provided.
search_person_or_address Person or Address Search ~520
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address. Required for address-mode searches (must combine with city + state). Free-form line, no normalization needed. |
| addressRecency | string | – | Filter address-based search results by how recently a person was linked to the search address. `all` = no recency filter (broadest, default when omitted); `current` = address is the subject's current… |
| city | string | – | City name. Used with lastName for name-mode OR with address + state for address-mode. |
| firstName | string | – | Person's first name. Optional but recommended for name-mode searches. Combines with lastName + locality (city/state/zip). Nickname expansion controlled by nicknameSearch. |
| lastName | string | – | Person's last name. Required for name-mode searches (must combine with city, state, or zip). |
| middleName | string | – | Person's middle name. Optional. Tightens name-mode match precision; rarely required. |
| nicknameSearch | boolean | – | Controls how aggressively firstName is expanded to spelling/nickname variants. `true` (default) = broad expansion (Megan → Meagan, Meggan, Meg; Jon → John, Jonathan; Katie → Katy, Kate). `false` = na… |
| state | string | – | Two-letter US state code (e.g. CA, NY, TX). Used with lastName for name-mode OR with address + city for address-mode. |
| zip | string | – | 5-digit US ZIP code. Used with lastName for name-mode (combines with city/state). |
| Name | Type | Req | Description |
|---|---|---|---|
| balance | – | yes | – |
| data | – | – | – |
| error | object | – | – |
| meta | object | yes | – |
| ok | boolean | yes | – |
No examples provided.
How do I install the com.skipshit/mcp server?
com.skipshit/mcp is a hosted endpoint at https://mcp.skipshit.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.skipshit.com
claude mcp add --transport http com-skipshit-mcp 'https://mcp.skipshit.com/mcp'
What is the com.skipshit/mcp server?
com.skipshit/mcp is listed in the public MCP registry as com.skipshit/mcp. People and property search for Claude and ChatGPT. Phones, emails, addresses, relatives, properties. This page covers its hosted endpoint (https://mcp.skipshit.com/mcp).
Is the com.skipshit/mcp server safe to use?
com.skipshit/mcp scores 35 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.skipshit/mcp server expose?
com.skipshit/mcp exposes 3 tools: search_person_or_address, expand_person_record, get_search_history. Their descriptions and schemas cost roughly 1,018 tokens of context every time the server is loaded.
Does the com.skipshit/mcp server require authentication?
No. We connected to com.skipshit/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.skipshit/mcp server still maintained?
com.skipshit/mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.