What this connects to

Five things, each of which was tested before it was written on this page.

There is no logo strip. Putting a GRC platform's name here because it would look good next to ours, when nothing connects to it, is the same trick as promising adocument will be 100% compliant. The second half of this page is the list of things we do not integrate with, which is usually the half you came for.

Works today

Claude Code, Claude Desktop, Cursor, Windsurf

MCP

One endpoint, no key for the research tools. The client configs are on the MCP page, including the Windsurf one that takes serverUrl rather than url.

https://api.theartofservice.com/mcp
Get the config

GitHub Actions

CI

Run a coverage check during a build and fail the pull request on a gap, with the reasoning written into the step summary. The action reads its attribution from the API response rather than printing numbers typed in at authoring time.

packages/github-action/action.yml
See the developer surface

Python, via LangChain

SDK

theartofservice-compliance on PyPI. Tools over the same graph, for an agent you are already building rather than one of ours.

pip install theartofservice-compliance
View on PyPI

Node

SDK

@theartofservice/compliance-mcp on npm. Runs the MCP server as a local stdio process for clients that prefer one to an HTTP endpoint.

npx -y @theartofservice/compliance-mcp
View on npm

Zapier, Make, n8n, or anything that speaks HTTP

Automation

The research endpoints are public and need no key, so a generic HTTP step is a working integration with no connector required. Point it at a URL, read JSON back.

GET /api/agent/crosswalk/pair?source=…&target=…
See the endpoints

Does not integrate

Vanta, Drata, Sprinto, Secureframe

No integration of any kind. They collect evidence out of your systems and we do not touch your systems, so there is nothing to sync. Use the graph to decide what to pursue and them to collect against it.

Jira, ServiceNow, Linear

No connector. You can create issues from our output with a generic HTTP step in an automation tool, but that is you wiring it, not us shipping it.

Slack, Teams

No app and no bot. An incoming webhook plus an automation step works and is worth ten minutes; there is nothing to install from us.

AWS, GCP, Azure, Okta, your HRIS

Nothing, deliberately. Continuous evidence collection is a maintenance treadmill that only makes sense with a team to maintain it, and it is the one thing the funded platforms genuinely do better.

A working example, end to end

Every coverage figure on this site comes from a call like this one. It needs no key, so it works from a Zapier step, a shell script, a cron job or an agent without anything being installed:

curl -sG "https://api.theartofservice.com/api/agent/crosswalk/pair" \
  --data-urlencode "source=SOC 2" \
  --data-urlencode "target=ISO 27001:2022" \
  | jq '{coverage: .coverage_percent, gaps: .gap_controls}'

# {"coverage": 48.4, "gaps": 48}

Anonymous callers get ten requests a day per IP. A free account raises it and the paid tier raises it again. The full tool list is here.