Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

scan_b2b_trust_soc2

Read-onlyIdempotent

Audit B2B company domains for SOC 2/ISO 27001/HIPAA trust centers, security.txt, DMARC spoofing risk, and DNS SaaS stack via SPF/TXT/MX records.

Instructions

Audit B2B company domains for SOC 2 / ISO 27001 / HIPAA Trust Centers (Vanta, Drata, Sprinto, SafeBase, Conveyor), security.txt, DMARC email spoofing risk, and internal DNS SaaS stack via SPF/TXT/MX records (corridordata/b2b-trust-soc2-dns-stack-scanner).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domains": "<domains>"
    },
    "name": "scan_b2b_trust_soc2"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesCompany domains or URLs to audit in parallel (e.g. ['linear.app', 'resend.com', 'cal.com']).
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).
probeTrustSubdomainsNoProbe trust.<domain>, security.<domain>, /trust, /security, and /.well-known/security.txt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description only needs to add context. It does: it discloses that domains are audited in parallel, names the underlying Apify actor, and enumerates the concrete signals checked, which helps an agent predict what the audit covers. It still omits result shape and typical runtime.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the resource scope front-loaded and no filler. The long vendor parenthetical is informative rather than redundant, though it edges toward list-dumping.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry the return-value burden, and it only lists the checks performed rather than what a result record contains. For a 3-parameter scanner with PPV billing it is adequately complete on inputs but leaves the output shape to discovery.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with three well-documented parameters, so the schema carries the burden and baseline 3 applies. The description adds only indirect meaning, letting the agent connect 'probeTrustSubdomains' to the trust./security. paths it mentions; it adds nothing about maxTotalChargeUsd beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (audit) and a precise resource set: trust centers, security.txt, DMARC risk, and DNS SaaS stack. The parenthetical vendor and record-type lists make the scope unmistakable and clearly distinguish it from sibling search/extract tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scope implies when the tool applies (vetting B2B vendors/domains), but there is no explicit when-to-use guidance relative to the many search_* siblings, nor any stated prerequisites or exclusions. Usage must be inferred from the purpose statement alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.