ALK Compliance MCP
REMOTE · ALK-COMPLIANCE-MCP.VERCEL.APP
Read-only, cited US compliance checks: product rules, Form 5500, federal award deadlines.
Available components
Last scanned (15 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://alk-compliance-mcp.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of alk-compliance-mcp.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| vercel.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://alk-compliance-mcp.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://alk-compliance-mcp.vercel.app/mcp | HTTPS enforced | 308 | https://alk-compliance-mcp.vercel.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
federal_award_deadlines Federal award deadlines ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | string | yes | Award type |
| federal_expenditures_this_fy | number | – | Grants only: federal award dollars expended this fiscal year (for single audit) |
| fiscal_year_end | string | yes | 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 |
No output schema declared.
No examples provided.
form_5500_check Form 5500 filing check ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| participants_at_start_of_year | integer | – | Participants at the beginning of the plan year |
| plan_type | string | yes | retirement (401k, pension) or welfare (health, dental, life, disability) |
| plan_year_end | string | yes | Plan year end date YYYY-MM-DD (e.g. 2025-12-31) |
| welfare_funding | string | – | Welfare plans only: how benefits are paid |
No output schema declared.
No examples provided.
list_desks List ALK compliance desks ~32
Lists the ALK Trading compliance desks that fix the issues these tools flag, with what each fixes and its URL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
product_compliance_requirements Product compliance requirements (US) ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | US state (2-letter code or name) or 'US' for nationwide |
No output schema declared.
No examples provided.
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.
remote · alk-compliance-mcp.vercel.app
claude mcp add --transport http rpatel021-alk-compliance-mcp 'https://alk-compliance-mcp.vercel.app/mcp'
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.