Skip to content

Scout Packs MCP server

io.github.tigerops-win/scout-packstigerops-winstreamable-httpv1.0.0Scanned

B2B data for AI agents: lead lookup, deliverability scoring, domain intel. x402 $0.01-$0.03/call.

16 tools: 14 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 14 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

14 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Scout Packs MCP server can do

The Scout Packs MCP server is published by the GitHub account tigerops-win. It has 16 tools. It can create or change data (14 tools: buy_pack, tech_stack, email_pattern, ssl_check and 10 more), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Changes things 14Claude Code: ask
  • buy_packLead data — buy a Scout Pack of verified B2B leads (people search results with verified business emails, ready for outreach).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Lead data — buy a Scout Pack of verified B2B leads (people search results with verified business emails, ready for outreach). Get the exact x402 payment requirements and step-by-step buying flow. pack: "25", "50", or "100". Returns what the buying agent must do; the agent's own wallet executes the USDC payment against the endpoint.
  • contact_pageExtract a company's published contact surface from its own public website: emails (role vs personal), phone numbers, contact-form presence, address and social links.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Extract a company's published contact surface from its own public website: emails (role vs personal), phone numbers, contact-form presence, address and social links. $0.02 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: contact_page(domain="acme.com")
  • deliverabilityEmail verification — lead data: MX/SPF/DMARC checks, disposable-domain and role-account detection, bounce-risk score 0-100 with a send/caution/do_not_send verdict.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Email verification — lead data: MX/SPF/DMARC checks, disposable-domain and role-account detection, bounce-risk score 0-100 with a send/caution/do_not_send verdict. Email enrichment and validation. $0.03 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: deliverability(target="jane@acme.com") or deliverability(target="acme.com")
  • dnsDump a domain's DNS records (A, AAAA, MX, TXT, NS, CNAME) via DNS-over-HTTPS, plus SPF presence signal.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Dump a domain's DNS records (A, AAAA, MX, TXT, NS, CNAME) via DNS-over-HTTPS, plus SPF presence signal. $0.01 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: dns(domain="acme.com")
  • domain_intelCompany enrichment from domain — lead data: RDAP registration data (registrar, creation/expiry dates) plus DNS infrastructure signals for any domain.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Company enrichment from domain — lead data: RDAP registration data (registrar, creation/expiry dates) plus DNS infrastructure signals for any domain. $0.02 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: domain_intel(domain="acme.com")
  • dossierCompany enrichment from domain — lead data: composite domain dossier.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Company enrichment from domain — lead data: composite domain dossier. RDAP registration + DNS infrastructure signals, tech-stack detection, likely corporate email patterns + MX verification, and SSL/TLS certificate health for one domain, fused into a single response with an aggregated signals list. $0.05 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: dossier(domain="acme.com")
  • email_patternEmail enrichment and validation — lead data: the most likely corporate email address patterns for a domain (first.last@, first@, flast@, ...) plus MX verification that the domain c…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Email enrichment and validation — lead data: the most likely corporate email address patterns for a domain (first.last@, first@, flast@, ...) plus MX verification that the domain can receive mail. Apollo-style email verification. $0.01 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: email_pattern(domain="acme.com")
  • headersAudit a domain's HTTP security headers (HSTS, CSP, X-Frame-Options and more) with a 0-100 score and A-F grade.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Audit a domain's HTTP security headers (HSTS, CSP, X-Frame-Options and more) with a 0-100 score and A-F grade. $0.01 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: headers(domain="acme.com")
  • mail_providerIdentify a domain's email provider: mailbox host (Google Workspace, Microsoft 365, Zoho, Proton and more) plus gateway detection (Mimecast, Proofpoint, Barracuda) from MX records.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Identify a domain's email provider: mailbox host (Google Workspace, Microsoft 365, Zoho, Proton and more) plus gateway detection (Mimecast, Proofpoint, Barracuda) from MX records. $0.01 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: mail_provider(domain="acme.com")
  • packsizePack-size resolver: parse a product title (and optional package price) into pack count, unit size and unit price.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Pack-size resolver: parse a product title (and optional package price) into pack count, unit size and unit price. $0.02 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: packsize(title="Acme Protein Powder 2lb", price="$29.99")
  • repo_healthCheck a public GitHub repo's health: stars, forks, open issues, license, archive status and 90-day commit velocity.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check a public GitHub repo's health: stars, forks, open issues, license, archive status and 90-day commit velocity. $0.01 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: repo_health(repo="octocat/hello-world")
  • ssl_checkCompany enrichment from domain — lead data: SSL/TLS certificate check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Company enrichment from domain — lead data: SSL/TLS certificate check. Issuer, expiry date, days remaining, TLS version, and risk flags (expired, expiring soon, self-signed). $0.01 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: ssl_check(domain="acme.com")
  • subdomainsMap a domain's live subdomain footprint from Certificate Transparency logs, classified into intent categories (api/dev, commerce, careers, docs/support, marketing, status/infra, st…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Map a domain's live subdomain footprint from Certificate Transparency logs, classified into intent categories (api/dev, commerce, careers, docs/support, marketing, status/infra, staging/test). $0.02 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: subdomains(domain="acme.com")
  • tech_stackCompany enrichment from domain — lead data: tech-stack detection.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Company enrichment from domain — lead data: tech-stack detection. Identify the web technologies powering a domain (CMS, frameworks, analytics, CDNs) from HTTP headers and page markup, with per-technology confidence and evidence. $0.01 USDC per call. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: tech_stack(domain="acme.com")
Only reads 2Show 2 read-only tools
  • list_packsB2B lead packs for sale: sizes, prices, and a redacted sample.No findings

    Why it is in this group

    • The name "list_packs" says "list": a word for reading.
    Description, as the server wrote it
    B2B lead packs for sale: sizes, prices, and a redacted sample. Free. Verified business lead enrichment batches (company, contact, verified email).
  • lookup_leadLead data — people search: company enrichment by company name or domain.No findings

    Why it is in this group

    • The name "lookup_lead" says "lookup": a word for reading.
    Description, as the server wrote it
    Lead data — people search: company enrichment by company name or domain. Apollo-style email enrichment and validation: enrich one lead with a verified business email + source URL. $0.01 USDC per lookup. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: lookup_lead(query="Acme Corp") or lookup_lead(query="acme.com")

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
404
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 404.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 14 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 14 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 14 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http scout-packs https://scout-packs-production.up.railway.app/mcp
claude mcp add --transport http scout-packs https://scout-packs-production.up.railway.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__scout-packs__list_packs",
      "mcp__scout-packs__lookup_lead"
    ],
    "ask": [
      "mcp__scout-packs__buy_pack",
      "mcp__scout-packs__tech_stack",
      "mcp__scout-packs__email_pattern",
      "mcp__scout-packs__ssl_check",
      "mcp__scout-packs__headers",
      "mcp__scout-packs__dns",
      "mcp__scout-packs__subdomains",
      "mcp__scout-packs__contact_page",
      "mcp__scout-packs__mail_provider",
      "mcp__scout-packs__repo_health",
      "mcp__scout-packs__deliverability",
      "mcp__scout-packs__domain_intel",
      "mcp__scout-packs__dossier",
      "mcp__scout-packs__packsize"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as scout-packs. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.tigerops-win/scout-packs/verify?hash=413076c7bff2d6cad8266500ddf87d07371b23ddd179875a6a2fd882f8b9ebe5" | jq -e '.changed == false'

Pinned hash 413076c7bff2, from Oct 21, 2026, 19:28 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.tigerops-win/scout-packs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.tigerops-win/scout-packs
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.tigerops-win/scout-packs.svg)](https://radar.anlyon.com/servers/io.github.tigerops-win/scout-packs)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.

Scout Packs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Scout Packs MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 14 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Scout Packs MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Scout Packs MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Scout Packs MCP server have?

16 tools: 14 write, 2 read. buy_pack, tech_stack, email_pattern, ssl_check, headers, dns, subdomains, contact_page and 8 more.

Does the Scout Packs MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Scout Packs MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Scout Packs MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.