# ALK Compliance MCP (remote · alk-compliance-mcp.vercel.app)

Read-only, cited US compliance checks: product rules, Form 5500, federal award deadlines.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `alk-compliance-mcp.vercel.app`: 75/100 (this document), [markdown](https://verifymcp.io/servers/rpatel021-alk-compliance-mcp/alk-compliance-mcp.md), [page](https://verifymcp.io/servers/rpatel021-alk-compliance-mcp/alk-compliance-mcp)

## Channel facts

- Endpoint: `https://alk-compliance-mcp.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 723 tokens (~180/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ALK Compliance MCP server?

ALK Compliance MCP is a hosted endpoint at https://alk-compliance-mcp.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http rpatel021-alk-compliance-mcp 'https://alk-compliance-mcp.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "rpatel021-alk-compliance-mcp": {
      "url": "https://alk-compliance-mcp.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rpatel021-alk-compliance-mcp": {
      "type": "http",
      "url": "https://alk-compliance-mcp.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.rpatel021-alk-compliance-mcp]
url = "https://alk-compliance-mcp.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rpatel021-alk-compliance-mcp": {
      "type": "remote",
      "url": "https://alk-compliance-mcp.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rpatel021-alk-compliance-mcp --url 'https://alk-compliance-mcp.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rpatel021-alk-compliance-mcp:
    url: "https://alk-compliance-mcp.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "rpatel021-alk-compliance-mcp": {
      "Transport": "http",
      "Url": "https://alk-compliance-mcp.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add rpatel021-alk-compliance-mcp -t streamable-http -u 'https://alk-compliance-mcp.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "rpatel021-alk-compliance-mcp": {
      "type": "http",
      "url": "https://alk-compliance-mcp.vercel.app/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-11-04 (score 75, +1)

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

### 2026-11-02 (score 74, +1)

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

### 2026-10-31 (score 73, +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-10-28 (score 72, +1)

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

### 2026-10-26 (score 71, +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-10-24 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 69)

First indexed and scored.

## MCP tools (4)

### `product_compliance_requirements` (~216 tokens)

Product compliance requirements (US)

Likely US product compliance rules for a product sold into a US state or market: CPSIA children's product certificate vs general certificate, California Prop 65 warnings, Minnesota PFAS (Amara's Law), and state packaging EPR (Oregon, Colorado, California). Each item is a potential issue with an official source link and the ALK desk that fixes it. Read-only, not legal advice.

Input parameters:

- `contains_intentionally_added_pfas` (boolean): Known or suspected intentionally added PFAS
- `for_children_12_or_under` (boolean): Designed or intended primarily for children 12 or younger
- `imported` (boolean): You import the product into the US
- `product_type` (string, required): What the product is, e.g. 'kids toy', 'water bottle', 'rain jacket'
- `sold_in_packaging` (boolean): Ships in packaging or paper you supply (default true)
- `state` (string, required): US state (2-letter code or name) or 'US' for nationwide

### `form_5500_check` (~172 tokens)

Form 5500 filing check

Checks whether an employee benefit plan likely needs a Form 5500 and when it is due (last day of the 7th month after plan year end; Form 5558 extension), with the small unfunded/insured welfare plan exemption flag. Cites IRS and DOL rules and links the ALK Benefits Compliance Desk. Read-only, not legal advice.

Input parameters:

- `participants_at_start_of_year` (integer): Participants at the beginning of the plan year
- `plan_type` (string, required): retirement (401k, pension) or welfare (health, dental, life, disability)
- `plan_year_end` (string, required): Plan year end date YYYY-MM-DD (e.g. 2025-12-31)
- `welfare_funding` (string): Welfare plans only: how benefits are paid

### `federal_award_deadlines` (~218 tokens)

Federal award deadlines

Deadlines for a federal contractor or grant recipient from fiscal year end and award type: incurred cost submission (ICS) 6 months after FYE under FAR 52.216-7(d)(2); SF-425/financial report cadence and closeout under 2 CFR 200.328 and 200.344; single audit at $1,000,000+ federal expenditures under 2 CFR 200.501 with the 200.512 due date. Links the ALK Federal Funds Desk. Read-only, not legal advice.

Input parameters:

- `award_type` (string, required): Award type
- `federal_expenditures_this_fy` (number): Grants only: federal award dollars expended this fiscal year (for single audit)
- `fiscal_year_end` (string, required): Your fiscal year end YYYY-MM-DD
- `period_of_performance_end` (string): Grants only: award period of performance end YYYY-MM-DD (for closeout)
- `report_frequency` (string): Grants only: financial report frequency in your award terms

### `list_desks` (~32 tokens)

List ALK compliance desks

Lists the ALK Trading compliance desks that fix the issues these tools flag, with what each fixes and its URL.

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69

## Common questions

### What is the ALK Compliance MCP server?

ALK Compliance MCP is listed in the public MCP registry as io.github.rpatel021/alk-compliance-mcp. Read-only, cited US compliance checks: product rules, Form 5500, federal award deadlines. This page covers its hosted endpoint (https://alk-compliance-mcp.vercel.app/mcp).

### Is the ALK Compliance MCP server safe to use?

ALK Compliance MCP scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ALK Compliance MCP server expose?

ALK Compliance MCP exposes 4 tools: product_compliance_requirements, form_5500_check, federal_award_deadlines, list_desks. Their descriptions and schemas cost roughly 638 tokens of context every time the server is loaded.

### Does the ALK Compliance MCP server require authentication?

No. We connected to ALK Compliance MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ALK Compliance MCP server still maintained?

ALK Compliance MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the ALK Compliance MCP server?

VerifyMCP ran 13 checks on ALK Compliance MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://alk-compliance-mcp.vercel.app/mcp
- Website: https://alk-compliance-mcp.vercel.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/rpatel021-alk-compliance-mcp/alk-compliance-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/rpatel021-alk-compliance-mcp/alk-compliance-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/rpatel021-alk-compliance-mcp/alk-compliance-mcp.json
- HTML version of this page: https://verifymcp.io/servers/rpatel021-alk-compliance-mcp/alk-compliance-mcp