com.skipshit/mcp

Est-ce que com.skipshit/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.skipshit/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 3 outils

• expand_person_record≈ 553 tokens

  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).

  Paramètres, retour & exemple (2)

  Paramètres

  • pid · string · requis
    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 record for 1 credit.
  • searchId · string · optionnel
    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 credit is charged to elevate the stub id.

  Exemple d'appel

  {"name": "expand_person_record", "arguments": {"pid": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "data": "texte", "meta": {}, "error": {}, "balance": "texte"}}

• get_search_history≈ 666 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • pid · string · optionnel
    Person identifier within a stored search. Pass with searchId to expand that one record from the stored result to its full form. Free.
  • limit · integer · optionnel
    Max records to return (1-25). Default depends on mode: 20 for list-mode, 5 for paged-slice mode.
  • offset · integer · optionnel
    Zero-based offset for pagination. Used with limit in paged-slice mode (searchId + offset/limit).
  • searchId · string · optionnel
    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 modes are free (no credit consumed).

  Exemple d'appel

  {"name": "get_search_history", "arguments": {"pid": "texte", "limit": 1, "offset": 1, "searchId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "data": "texte", "meta": {}, "error": {}, "balance": "texte"}}

• search_person_or_address≈ 959 tokens

  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).

  Paramètres, retour & exemple (9)

  Paramètres

  • zip · string · optionnel
    5-digit US ZIP code. Used with lastName for name-mode (combines with city/state).
  • city · string · optionnel
    City name. Used with lastName for name-mode OR with address + state for address-mode.
  • state · string · optionnel
    Two-letter US state code (e.g. CA, NY, TX). Used with lastName for name-mode OR with address + city for address-mode.
  • address · string · optionnel
    Street address. Required for address-mode searches (must combine with city + state). Free-form line, no normalization needed.
  • lastName · string · optionnel
    Person's last name. Required for name-mode searches (must combine with city, state, or zip).
  • firstName · string · optionnel
    Person's first name. Optional but recommended for name-mode searches. Combines with lastName + locality (city/state/zip). Nickname expansion controlled by nicknameSearch.
  • middleName · string · optionnel
    Person's middle name. Optional. Tightens name-mode match precision; rarely required.
  • addressRecency · string · optionnel · all | current | lastOneYear | lastThreeYears | lastFiveYears | lastTenYears
    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 residence; `lastOneYear` / `lastThreeYears` / `lastFiveYears` / `lastTenYears` = include only people linked within the past 1 / 3 / 5 / 10 years. Only applies to address-based searches.
  • nicknameSearch · boolean · optionnel
    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` = narrower expansion — drops loose nickname variants but the dataset may still surface tight phonetic neighbors (observed: searching firstName=MEGAN with nicknameSearch=false still returned MEAGAN at rank 0 when she was the strongest local match). Pass `false` to reduce noise from long-form variants; do NOT rely on `false` for strict literal-spelling-only matching.

  Exemple d'appel

  {"name": "search_person_or_address", "arguments": {"zip": "texte", "city": "texte", "state": "texte", "address": "texte", "lastName": "texte", "firstName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "data": "texte", "meta": {}, "error": {}, "balance": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.skipshit.com/mcp