SOC 2 Compared

Look up year-one SOC 2 platform prices at 25 employees and the audit firms that issue reports.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
98%
Integridad del esquema
91%
Calidad de los nombres
96%
Riesgo de envenenamiento
60%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainen submit_listing
  • MEDIUMTool description contains URL to non-standard domainen my_listings

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,809Tokens (definiciones de herramientas)
~611 BTamaño de respuesta típico
Impacto moderado en la atención (1.41% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "mcp": {
      "url": "https://soc2compared.com/mcp"
    }
  }
}

Puntos de conexión remotos

https://soc2compared.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (9)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢search_listings(query, limit)

Full-text search over SOC 2 Compared's Published providers. Returns compact records (name, slug, tagline, url). Fetch depth with get_listing.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "What to search for."
    },
    "limit": {
      "type": "number",
      "description": "Max results (default 10, cap 25)."
    }
  },
  "required": [
    "query"
  ]
}
🟢get_listing(slug)

One provider in full, as answer-first markdown: the summary, then every question on the sheet with its answer, the vendor's own words for it and the URL that proves it. Identical to /{slug}.md and to the HTML page.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "The listing slug (from search_listings or the URL)."
    }
  },
  "required": [
    "slug"
  ]
}
🟢list_categories

SOC 2 Compared's categories with their live listing counts, 0 for one with none yet.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢compare_listings(a, b)

Two providers side by side, as markdown: taglines, pricing, API availability, tags — the researched compare facts, honest about unknowns.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "a": {
      "type": "string",
      "description": "First listing slug."
    },
    "b": {
      "type": "string",
      "description": "Second listing slug."
    }
  },
  "required": [
    "a",
    "b"
  ]
}
🟢get_best_of(category)

The Published providers in one category, in the order its category page prints (ranked by what we can confirm: a public price, an API and docs, independent sources, stated limits), as a markdown answer sheet. Payment never moves a row.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "description": "The category slug (from list_categories)."
    }
  },
  "required": [
    "category"
  ]
}
🟡submit_listing(url)

Submit a provider to SOC 2 Compared: the url alone; we write its name and description from its own pages. Requires an existing signed-in account with verified email; send its session Cookie header on the MCP request, or an agent key the account made at https://soc2compared.com/dashboard/agents as Authorization: Bearer. Identity and email come only from that session or key. Sign in or explicitly create an account at https://soc2compared.com/login?next=%2Fsubmit and verify its email before retrying. This tool creates no account and sends no verification email. Returns {httpStatus:201, id, slug, status:'Draft'}; research + the quality gate decide publication. Your own (url, session email) replay within 24h returns httpStatus:200. The fit check starts at once and usually answers within a minute: poll GET https://soc2compared.com/api/submissions/{id} and wait the Retry-After seconds it sends while fit is "checking". fit then reads "accepted" (it goes live, and the account is mailed), "rejected" (mailed with the reason) or "undecided" (a person looks within 2 days). No session: {httpStatus:401, error:'sign_in_required', message, loginUrl}. Unverified session: {httpStatus:403, error:'email_unverified', message, email, remediation}. Company gate: the account's address, or an address it proved with a code, must be on the submitted website's domain; otherwise {httpStatus:403, error:'domain_unverified', message, domain, remediation, ownerUrl, skip} — POST /api/domain-proof/start {url, email} mails a 6-digit code to an address at that domain, POST /api/domain-proof/verify {proofId, code} redeems it, then submit again. Submitting for someone with no mailbox of your own at the domain? Give the owner ownerUrl (the submit page with the site filled in): they prove it there with a code, or skip the proof as skip says. Personal mailboxes (gmail, outlook…) never prove a domain. No refusal creates a listing. Validation returns 400; duplicate/claim responses return 409. Read tools remain keyless.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The website being submitted (https)."
    }
  },
  "required": [
    "url"
  ]
}
🟡send_lead(name, email, message, consent, listingSlug, ...)

Send a buyer-intent enquiry (lead) to a provider or a whole category on SOC 2 Compared. Keyless. Requires consent:true, a real name, a permanent (non-disposable) email, a message of at least 20 chars, and a target (listingSlug OR categorySlug). Returns { ok, delivered }. Idempotent by (email, target) within 7 days. Nothing here changes a listing's rank, tier or copy.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Your name."
    },
    "email": {
      "type": "string",
      "description": "A permanent contact email (non-disposable)."
    },
    "message": {
      "type": "string",
      "description": "The enquiry — real demand, at least 20 chars."
    },
    "consent": {
      "type": "boolean",
      "description": "Must be true — you agree your details go to the provider(s)."
    },
    "listingSlug": {
      "type": "string",
      "description": "Target listing slug (this OR categorySlug)."
    },
    "categorySlug": {
      "type": "string",
      "description": "Target category slug (this OR listingSlug)."
    },
    "company": {
      "type": "string",
      "description": "Optional company name."
    }
  },
  "required": [
    "name",
    "email",
    "message",
    "consent"
  ]
}
🟢my_listings(slug)

What the SOC 2 Compared owner dashboard shows about the listings an account owns: each one's status (`status.kind`: review with the expected date, accepted with `liveOn` and `paid` ('express' | 'featured' | null: the paid way that releases it, Featured including Express review), live, refused with the reason, or archived), the listing as it shows, 30 days of real numbers with the 30 before, where AI answers named the product or cited its page, and what it can buy here at this site's prices. Only for the account itself: send its session Cookie header, or its agent key with "Read your listings" as Authorization: Bearer. Same answer as GET https://soc2compared.com/api/owner/listings. Read-only: corrections go through the dashboard's request form.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Optional: one listing, by its slug. Without it, every listing the account owns."
    }
  }
}
🟢subscribe_newsletter(email, source)

Subscribe an email to the SOC 2 Compared digest of new and freshly re-verified providers. Provide an email; returns { ok }. The address is on the list at once and gets one welcome mail. Every mail carries a one-click unsubscribe.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "The email to subscribe."
    },
    "source": {
      "type": "string",
      "description": "Optional: where the subscribe came from."
    }
  },
  "required": [
    "email"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada9 herramientas