com.skipshit/mcp
REMOTE · MCP.SKIPSHIT.COM · SCANNED AUG 3
People and property search for Claude and ChatGPT. Phones, emails, addresses, relatives, properties.
Available components
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 →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1331 tokens (~443/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.skipshit.com
claude mcp add --transport http com-skipshit-mcp https://mcp.skipshit.com/mcp
[mcp_servers.com-skipshit-mcp] url = "https://mcp.skipshit.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-skipshit-mcp": {
"type": "remote",
"url": "https://mcp.skipshit.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-skipshit-mcp --url https://mcp.skipshit.com/mcp --transport streamable-http
mcp_servers:
com-skipshit-mcp:
url: "https://mcp.skipshit.com/mcp" {
"mcpServers": {
"com-skipshit-mcp": {
"type": "http",
"url": "https://mcp.skipshit.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +6
- 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 67
First indexed and scored.
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 3 Aug 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 | 19 Jun 2026 | 17 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 781c2cf0a2f0fadc0eb2f12ed7db2289 |
| 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 |
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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://mcp.skipshit.com/.well-known/oauth-protected-resource"
Bearer realm="mcp", resource_metadata="https://mcp.skipshit.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.skipshit.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.skipshit.com/mcp |
| Authorisation server | https://mcp.skipshit.com |
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.
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.