dev.stackscope/stackscope

Est-ce que dev.stackscope/stackscope est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.stackscope/stackscope » 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 11 outils

• account_status≈ 125 tokens

  What this connection can do and how much allowance is left: the plan, the permissions granted, and how many more distinct sites may be returned before the monthly allowance is used up. Calls themselves are not capped. Free. Worth calling before a large query.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "account_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_watch≈ 987 tokens

  Set up a standing watch that delivers newly discovered matching sites on a schedule. Narrow it by technology, keyword, category, country, distance from a place or whether the site publishes a contact route; a completely unfiltered watch needs a plan that allows the every-site stream. Free to create, but delivered sites count against the monthly site allowance, and plans limit how many watches, technologies and keywords you may have. A webhook watch returns its signing secret exactly once when it is created.

  Paramètres, retour & exemple (15)

  Paramètres

  • near · string|null · optionnel
    Only sites near a place: a town or city, a postcode, or 'lat,lng', e.g. Bristol. Use with radius. Sites we could not place never match.
  • radius · string|null · optionnel
    How far from near, e.g. 30mi or 50km (a bare number is km). From 5 to 248 miles (8 to 400 km).
  • cadence · string|null · optionnel
    How often to deliver: instant, daily or weekly. Defaults to daily for email and instant for webhook or slack; portal stores the value but does not deliver.
  • channel · string|null · optionnel
    Delivery channel: email, webhook, slack, or portal for no outbound delivery. Default email.
  • country · string|null · optionnel
    Restrict to a country, ISO 3166-1 alpha-2 or a name. For several, use countries.
  • category · string|null · optionnel
    Restrict to a product category. For several, use categories.
  • keywords · array|null · optionnel
    Whole words to look for in a site's name, title or description, e.g. photogrammetry. Matches ANY of them; a multi-word entry is a phrase. Three characters or more. A common word is refused as too broad, with an estimate of what it would deliver. Combines with a technology: 'Stripe and photogrammetry' fits on every plan.
  • countries · array|null · optionnel
    Restrict to several countries, each an ISO 3166-1 alpha-2 code or a name, e.g. ["GB", "Ireland"]. A site matches if it is in ANY of them.
  • categories · array|null · optionnel
    Restrict to several product categories. A site matches if it is in ANY of them.
  • webhookUrl · string|null · optionnel
    Full HTTPS delivery URL, required for webhook or slack. It is stored encrypted; list_watches later returns only its host, never its path or query.
  • technologies · array|null · optionnel
    Technologies to watch, by name. A site matches if it uses ANY of them.
  • hasContactPage · boolean|null · optionnel
    Only sites that have a published contact page (true), or only those that do not (false). Omit for no filter; set both to require both. Needs the 'contacts' permission.
  • hasContactEmail · boolean|null · optionnel
    Only sites that have a published contact email (true), or only those that do not (false). Omit for no filter. Needs the 'contacts' permission.
  • technologiesAll · array|null · optionnel
    Also require ALL of these technologies.
  • technologiesExcluding · array|null · optionnel
    Exclude sites using any of these technologies.

  Exemple d'appel

  {"name": "create_watch", "arguments": {"near": "texte", "radius": "texte", "cadence": "texte", "channel": "texte", "country": "texte", "category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_watch≈ 108 tokens

  Delete one of the customer's watches by id, from list_watches. Deliveries stop immediately. Free.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    The watch id, from list_watches.

  Exemple d'appel

  {"name": "delete_watch", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• export_sites≈ 815 tokens

  A bulk export of matching sites, up to 5,000 at once, for building a list or loading into a spreadsheet. Same filters as find_sites. Ask for csv output if the result is going into a file. For counts, shares or 'which X do these sites use', call stack_breakdown instead; it answers in one call and needs no export. Counts one site from the monthly allowance for each site not already returned to you this period, so this is the call most likely to ask you to confirm first.

  Paramètres, retour & exemple (15)

  Paramètres

  • csv · boolean · optionnel
    Also return the rows as CSV text, ready to save as a file.
  • near · string|null · optionnel
    Only sites near a place: a town or city, a postcode, or 'lat,lng', e.g. Bristol. Use with radius. Sites we could not place are left out.
  • limit · integer · optionnel
    How many sites to export, 1-5000. Default 1000.
  • since · string|null · optionnel
    Earliest launch date, YYYY-MM-DD.
  • until · string|null · optionnel
    Latest launch date, YYYY-MM-DD. Inclusive of the whole day.
  • radius · string|null · optionnel
    How far from near, e.g. 30mi or 50km (a bare number is km). From 5 to 248 miles (8 to 400 km).
  • confirm · boolean · optionnel
    Set true to skip the cost confirmation and return the data immediately.
  • country · string|null · optionnel
    Country as an ISO 3166-1 alpha-2 code, e.g. GB. Names are accepted too.
  • category · string|null · optionnel
    Product category, e.g. ecommerce.
  • keywords · array|null · optionnel
    Whole words to look for in a site's name, title or description, e.g. photogrammetry. Matches ANY of them; a multi-word entry is a phrase. Three characters or more, up to ten words. Combines with every other filter, so 'Stripe sites that mention photogrammetry' is technology plus keywords. The same rule create_watch uses, so a word that filters here is the word a watch would fire on.
  • technology · string|null · optionnel
    Technology name, exactly as returned by list_technologies.
  • observedSince · string|null · optionnel
    Earliest date we first recorded the site, YYYY-MM-DD. Use this rather than 'since' when building an incremental export on a schedule.
  • hasContactPage · boolean|null · optionnel
    Only sites that have a published contact page. Needs the 'contacts' permission.
  • includeQuality · boolean · optionnel
    Include quality bands for each site.
  • hasContactEmail · boolean|null · optionnel
    Only sites that have a published contact email. Needs the 'contacts' permission.

  Exemple d'appel

  {"name": "export_sites", "arguments": {"csv": true, "near": "texte", "limit": 1, "since": "texte", "until": "texte", "radius": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_sites≈ 1101 tokens

  Find newly launched sites matching any combination of technology, category, country, distance from a place, date range and contact availability. This is the main search tool. For example: sites in the UK built with WordPress that launched this week and have a contact email, or Shopify shops within 30 miles of Bristol. Each site carries its town, and its distance when near is given. For counts, shares or 'which X do these sites use', call stack_breakdown instead; it answers in one call. Counts one site from the monthly allowance for each site not already returned to you this period; you may be asked to confirm before a large result is returned.

  Paramètres, retour & exemple (16)

  Paramètres

  • near · string|null · optionnel
    Only sites near a place: a town or city, a postcode, or 'lat,lng', e.g. Bristol. Use with radius. Sites we could not place are left out.
  • limit · integer · optionnel
    How many sites to return, 1-100. Default 50.
  • since · string|null · optionnel
    Earliest LAUNCH date, YYYY-MM-DD. Use this for questions about when products launched, e.g. 'launched this week'.
  • until · string|null · optionnel
    Latest LAUNCH date, YYYY-MM-DD. Inclusive: the whole of that day is included, so since and until set to the same date returns that one day.
  • cursor · string|null · optionnel
    Paging token from a previous call's nextCursor. Repeat every other filter exactly as it was when the token was issued.
  • radius · string|null · optionnel
    How far from near, e.g. 30mi or 50km (a bare number is km). From 5 to 248 miles (8 to 400 km).
  • confirm · boolean · optionnel
    Set true to skip the cost confirmation and return the data immediately.
  • country · string|null · optionnel
    Country as an ISO 3166-1 alpha-2 code, e.g. GB for the United Kingdom, US, DE. Country names such as 'United Kingdom' are also accepted. Country is an ESTIMATE with a confidence score, so see minCountryConfidence.
  • category · string|null · optionnel
    Product category, e.g. ecommerce.
  • keywords · array|null · optionnel
    Whole words to look for in a site's name, title or description, e.g. photogrammetry. Matches ANY of them; a multi-word entry is a phrase. Three characters or more, up to ten words. Combines with every other filter, so 'Stripe sites that mention photogrammetry' is technology plus keywords. The same rule create_watch uses, so a word that filters here is the word a watch would fire on.
  • technology · string|null · optionnel
    Technology name, exactly as returned by list_technologies, e.g. wordpress.
  • observedSince · string|null · optionnel
    Earliest date we first recorded the site, YYYY-MM-DD. Use this instead of 'since' when polling for new rows on a schedule: sites are discovered a median of 2 days (and up to about a week) after they launch, so a poller tracking 'since' never learns about them.
  • hasContactPage · boolean|null · optionnel
    Only sites that have a published contact page. Needs the 'contacts' permission.
  • includeQuality · boolean · optionnel
    Include quality bands for each site.
  • hasContactEmail · boolean|null · optionnel
    Only sites that have a published contact email. Needs the 'contacts' permission.
  • minCountryConfidence · number|null · optionnel
    Least country confidence to accept, 0 to 1. Country is estimated from the site, and scores near the 0.45 floor are weak guesses: a site whose own title says it is in Bangladesh can score 0.48 for the UK. Genuine matches usually score 0.6 or better, so pass 0.6 when the country needs to be right rather than merely likely. Every row carries its own countryConfidence too.

  Exemple d'appel

  {"name": "find_sites", "arguments": {"near": "texte", "limit": 1, "since": "texte", "until": "texte", "cursor": "texte", "radius": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_technologies≈ 203 tokens

  The catalogue of technologies we track, with how many sites use each. Use this to find the exact technology name to pass to the other tools. Counts no site allowance.

  Paramètres, retour & exemple (3)

  Paramètres

  • to · string|null · optionnel
    Only count sites that launched on or before this date (YYYY-MM-DD).
  • from · string|null · optionnel
    Only count sites that launched on or after this date (YYYY-MM-DD).
  • limit · integer · optionnel
    How many to return, 1-500. Default 100, busiest first.

  Exemple d'appel

  {"name": "list_technologies", "arguments": {"to": "texte", "from": "texte", "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_watches≈ 112 tokens

  The customer's watches, including inactive watches and their current status. A watch can deliver new matching sites by email, Slack or webhook as they are discovered, or keep matches in the account portal. Free.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_watches", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_site≈ 272 tokens

  Everything known about one website: when it launched, what it is, and the technologies detected on it. Give a domain such as example.com (a full URL works too). Returns found: false if the site is not in the corpus. When found, counts one site from the monthly allowance.

  Paramètres, retour & exemple (4)

  Paramètres

  • domain · string · requis
    Domain to look up, e.g. example.com
  • includeContact · boolean · optionnel
    Include the site's published contact route (role mailbox and/or contact page) when available. Needs the 'contacts' permission.
  • includeQuality · boolean · optionnel
    Include quality bands and whether the site is green hosted.
  • includeInfrastructure · boolean · optionnel
    Include hosting, DNS and email-security details.

  Exemple d'appel

  {"name": "lookup_site", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stack_breakdown≈ 782 tokens

  Counts and shares, not a list: for the sites matching a filter, how many use each technology, grouped by kind (payments, analytics, hosting, cms...). Answers any question of the form 'how many', 'what share', or 'which X do sites using Y use' in one call, for example 'what payment providers do Ghost sites use'. Use this BEFORE find_sites or export_sites for those questions; exporting rows and counting them costs hundreds of lookups for the same answer. Same filters as find_sites. Counts one Explore slice and no site allowance.

  Paramètres, retour & exemple (11)

  Paramètres

  • near · string|null · optionnel
    Only sites near a place: a town or city, a postcode, or 'lat,lng', e.g. Bristol. Use with radius. Sites we could not place are left out.
  • since · string|null · optionnel
    Earliest LAUNCH date, YYYY-MM-DD.
  • until · string|null · optionnel
    Latest LAUNCH date, YYYY-MM-DD. Inclusive of the whole day.
  • radius · string|null · optionnel
    How far from near, e.g. 30mi or 50km (a bare number is km). From 5 to 248 miles (8 to 400 km).
  • country · string|null · optionnel
    Country as an ISO 3166-1 alpha-2 code, e.g. GB. Names are accepted too. Country is an ESTIMATE with a confidence score, so see minCountryConfidence.
  • category · string|null · optionnel
    Product category of the SITES, e.g. ecommerce. Not a kind of technology; for that see technologyCategory.
  • keywords · array|null · optionnel
    Whole words to look for in a site's name, title or description, e.g. photogrammetry. Matches ANY of them; a multi-word entry is a phrase. Three characters or more, up to ten words. Combines with every other filter, so 'Stripe sites that mention photogrammetry' is technology plus keywords. The same rule create_watch uses, so a word that filters here is the word a watch would fire on.
  • technology · string|null · optionnel
    Technology name, exactly as returned by list_technologies, e.g. ghost. The sites using it are the population; it is left out of its own breakdown.
  • observedSince · string|null · optionnel
    Earliest date we first recorded the site, YYYY-MM-DD.
  • technologyCategory · string|null · optionnel
    One kind of technology to report on, e.g. payments, analytics, cms, hosting. Leave unset for every kind. list_technologies shows each technology's kind under 'category'.
  • minCountryConfidence · number|null · optionnel
    Least country confidence to accept, 0 to 1. Pass 0.6 when the country needs to be right rather than merely likely.

  Exemple d'appel

  {"name": "stack_breakdown", "arguments": {"near": "texte", "since": "texte", "until": "texte", "radius": "texte", "country": "texte", "category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• technology_sites≈ 458 tokens

  Sites detected using one specific technology, newest first. Use find_sites instead when combining a technology with a country, category or contact filter. For counts, shares or 'which X do these sites use', call stack_breakdown instead; it answers in one call. Counts one site from the monthly allowance for each site not already returned to you this period.

  Paramètres, retour & exemple (9)

  Paramètres

  • near · string|null · optionnel
    Only sites near a place: a town or city, a postcode, or 'lat,lng', e.g. Bristol. Use with radius. Sites we could not place are left out.
  • limit · integer · optionnel
    How many sites to return, 1-100. Default 50.
  • since · string|null · optionnel
    Earliest launch date, YYYY-MM-DD.
  • until · string|null · optionnel
    Latest launch date, YYYY-MM-DD. Inclusive of the whole day.
  • offset · integer · optionnel
    How many to skip, for paging.
  • radius · string|null · optionnel
    How far from near, e.g. 30mi or 50km (a bare number is km). From 5 to 248 miles (8 to 400 km).
  • confirm · boolean · optionnel
    Set true to skip the cost confirmation and return the data immediately.
  • technology · string · requis
    Technology name, exactly as returned by list_technologies.
  • includeQuality · boolean · optionnel
    Include quality bands for each site.

  Exemple d'appel

  {"name": "technology_sites", "arguments": {"technology": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• technology_trend≈ 170 tokens

  Weekly adoption of one technology over the whole period we have data for, counted across every site in the corpus, with notes marking anything that changed how it is measured. Same population as list_technologies, so the two can be compared. Counts no site allowance.

  Paramètres, retour & exemple (1)

  Paramètres

  • technology · string · requis
    Technology name, exactly as returned by list_technologies.

  Exemple d'appel

  {"name": "technology_trend", "arguments": {"technology": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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.stackscope.dev