# TheArtOfService Compliance Intelligence (remote · api.theartofservice.com)

Query 692+ compliance frameworks, 13,700+ controls, and 280K+ cross-framework mappings.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.theartofservice.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/gjb65-compliance-intelligence/api.md), [page](https://verifymcp.io/servers/gjb65-compliance-intelligence/api)

## Channel facts

- Endpoint: `https://api.theartofservice.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1076 tokens (~107/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http gjb65-compliance-intelligence https://api.theartofservice.com/mcp
```

### Codex

```toml
[mcp_servers.gjb65-compliance-intelligence]
url = "https://api.theartofservice.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gjb65-compliance-intelligence": {
      "type": "remote",
      "url": "https://api.theartofservice.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gjb65-compliance-intelligence --url https://api.theartofservice.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gjb65-compliance-intelligence:
    url: "https://api.theartofservice.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "gjb65-compliance-intelligence": {
      "type": "http",
      "url": "https://api.theartofservice.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (10)

### `agent_search_frameworks` (~162 tokens)

Search and list compliance frameworks

Search the compliance knowledge graph for frameworks by name, keyword, or jurisdiction.  Returns framework metadata including name, description, jurisdiction, domain count, control count, and mapping-partner count.  Without a query, returns all frameworks.  Use this as the starting point to discover available frameworks.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

Input parameters:

- `jurisdiction` (string): Filter by jurisdiction (e.g. 'International', 'Australia', 'United States', 'European Union')
- `limit` (integer): Maximum frameworks to return
- `q` (string): Search query to filter by name or keyword (e.g. 'ISO 27001', 'privacy', 'Australian')

### `agent_get_framework` (~83 tokens)

Get detailed information about a compliance framework

Returns comprehensive details about a specific compliance framework: description, jurisdiction, version, domains with control counts, and cross-framework mapping statistics.  Use the exact framework name as returned by agent_search_frameworks.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

Input parameters:

- `name` (string, required)

### `agent_get_framework_controls` (~110 tokens)

Get all controls for a compliance framework

Returns all controls belonging to a framework, optionally filtered by domain.  Each control includes: code, title, description, and domain.  For large frameworks (e.g. NIST SP 800-53 Rev 5), use the domain filter to narrow results.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

Input parameters:

- `domain` (string): Filter controls by domain name
- `name` (string, required)

### `agent_get_control` (~100 tokens)

Get detailed information about a specific control

Returns full details for a single control by its code identifier: title, description, domain, and framework.  Control codes are framework-specific (e.g. 'A.5.1' for ISO 27001, 'AC-1' for NIST 800-53).

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

Input parameters:

- `code` (string, required)

### `agent_get_control_cross_references` (~102 tokens)

Get cross-framework mappings for a control

Returns all controls in other frameworks that map to the given control via MAPS_TO relationships.  This is the core cross-framework mapping capability: use it to find equivalent controls across different compliance frameworks (e.g. NIST 800-53 equivalents of ISO 27001 controls).

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

Input parameters:

- `code` (string, required)

### `agent_cross_framework_map` (~140 tokens)

Map controls between two compliance frameworks

Returns the complete control-to-control mapping between a source and target framework.  Each mapping shows which source control maps to which target control(s).  This enables multi-framework compliance: satisfy one control to cover requirements in both frameworks.  Use exact framework names as returned by agent_search_frameworks.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

Input parameters:

- `source` (string, required): Source framework name (e.g. 'ISO 27001:2022')
- `target` (string, required): Target framework name (e.g. 'NIST Cybersecurity Framework 2.0')

### `agent_coverage_report` (~96 tokens)

Get cross-framework coverage report for a framework

Returns a coverage analysis showing how many controls in the given framework map to controls in every other framework.  Includes total controls, mapped control counts, and coverage percentages per target framework.  Use this to understand which frameworks overlap most and plan multi-framework strategies.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

Input parameters:

- `name` (string, required)

### `agent_search` (~157 tokens)

Full-text search across controls and frameworks

Search the compliance knowledge graph using full-text search.  Type 'controls' searches control titles and descriptions.  Type 'frameworks' searches framework names and descriptions.  Use specific compliance terms for best results (e.g. 'access control', 'encryption at rest', 'data breach notification').

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

Input parameters:

- `limit` (integer): Maximum results to return
- `query` (string, required): Search query (e.g. 'access control', 'encryption at rest')
- `type` (string): Search type: 'controls' for control titles/descriptions, 'frameworks' for framework names/descriptions

### `agent_platform_stats` (~58 tokens)

Get platform statistics

Returns current platform statistics: total framework count, control count, cross-framework mapping count, and domain count.  No authentication required.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

### `agent_pricing_info` (~68 tokens)

Get API pricing and rate limit information

Returns current API pricing tiers, monthly call limits, and (if authenticated) your current month's usage.  Use this to understand costs before making API calls.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gjb65-compliance-intelligence/api#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://api.theartofservice.com/mcp
- Repository: https://github.com/GJB65/compliance-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/gjb65-compliance-intelligence/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/gjb65-compliance-intelligence/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/gjb65-compliance-intelligence/api