fi.northpoint/marketing-compliance
REMOTE · NORTHPOINT.FI · SCANNED SEP 20
Crypto marketing compliance rulesets over MCP: MiCA, FCA, GDPR, SEC, MAS, VARA. Not legal advice.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1897 tokens (~145/item across 13 items; 13 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
How do I install the fi.northpoint/marketing-compliance MCP server?
fi.northpoint/marketing-compliance is a hosted endpoint at https://northpoint.fi/api/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 · northpoint.fi
claude mcp add --transport http fi-northpoint-marketing-compliance 'https://northpoint.fi/api/mcp'
{
"mcpServers": {
"fi-northpoint-marketing-compliance": {
"url": "https://northpoint.fi/api/mcp"
}
}
} {
"servers": {
"fi-northpoint-marketing-compliance": {
"type": "http",
"url": "https://northpoint.fi/api/mcp"
}
}
} [mcp_servers.fi-northpoint-marketing-compliance] url = "https://northpoint.fi/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fi-northpoint-marketing-compliance": {
"type": "remote",
"url": "https://northpoint.fi/api/mcp",
"enabled": true
}
}
} openclaw mcp add fi-northpoint-marketing-compliance --url 'https://northpoint.fi/api/mcp' --transport streamable-http
mcp_servers:
fi-northpoint-marketing-compliance:
url: "https://northpoint.fi/api/mcp" {
"McpServers": {
"fi-northpoint-marketing-compliance": {
"Transport": "http",
"Url": "https://northpoint.fi/api/mcp"
}
}
} assistant mcp add fi-northpoint-marketing-compliance -t streamable-http -u 'https://northpoint.fi/api/mcp'
{
"mcpServers": {
"fi-northpoint-marketing-compliance": {
"type": "http",
"url": "https://northpoint.fi/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://northpoint.fi/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=northpoint.fi | CN=YR1,O=Let's Encrypt,C=US | 5 Aug 2026 | 3 Nov 2026 | RSA 2048 | SHA256-RSA | 522d548679f4a97969316748bc4bb2e3a70 |
| SANs: northpoint.fi | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of northpoint.fi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fi. | present | 18073 | 13 | Verified |
| northpoint.fi. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://northpoint.fi/api/mcp | Verified | 200 | |
| http (plaintext) | http://northpoint.fi/api/mcp | HTTPS enforced | 308 | https://northpoint.fi/api/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 →
get_latest_signal ~59
Return the last N days of NorthPoint's competitor + regulatory + narrative signal feed. Daily-rebuilt digest of what moved in crypto marketing/regulation.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (default 7, max 90). |
No output schema declared.
No examples provided.
get_lite_ruleset ~121
Return the FREE lite ruleset for one regime as markdown, so YOU (the calling model) can audit a marketing asset against it directly — no NorthPoint API key needed and no round trip. Use this to check crypto/fintech marketing copy against real regulatory rules before it is published. For the full 25-40 rule audit run by NorthPoint's own model, with a citable verdict, use the corresponding run_*_pro_check tool (subscriber key required).
| Name | Type | Req | Description |
|---|---|---|---|
| regime | string | yes | Which regime's free ruleset to return. |
No output schema declared.
No examples provided.
list_regimes ~71
List every marketing-compliance regime NorthPoint can check (MiCA, FCA financial promotions, GDPR/ePrivacy, SEC, MAS, VARA, TGE launch readiness, AEO visibility), with the free and subscriber rule counts for each. No API key required. Call this first to discover what is available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_ad_creative_check ~177
Cross-jurisdiction ad-creative compliance scan (~30 rules). Pass an image URL, base64 image, or just a landing-page URL plus caption — the scanner extracts on-image text, evaluates prominence/contrast/dark patterns/disclosures, and returns a full audit.
| Name | Type | Req | Description |
|---|---|---|---|
| caption | string | – | Optional caption text shown with the creative on social. |
| image_b64 | string | – | Base64-encoded image bytes (or data: URL). Use this if the image is not publicly hosted. |
| image_url | string | – | HTTPS URL of the ad creative image (jpeg/png/gif/webp, <= 5 MB). |
| text | string | – | Optional text accompanying the ad creative (caption or alt copy). |
| url | string | – | Public URL of a landing page connected to the creative — fetched server-side. |
No output schema declared.
No examples provided.
run_aeo_visibility_check ~197
Run the AEO / GEO (Answer Engine / Generative Engine Optimization) visibility audit (12 rules). Analyses whether AI answer engines (ChatGPT, Perplexity, Claude, Gemini) will cite the project for its category, and the gaps stopping it. Returns a 0–100 citeability score, per-engine read, per-rule analysis, and a ranked fix list. The 2026 successor to SEO.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Optional hint to the auditor about asset type: landing_page | ad | email | x_post | kol_contract | whitepaper | press_release. |
| text | string | – | The marketing asset text to audit (landing-page copy, ad text, email body, X post, KOL contract, whitepaper excerpt, press release, etc.). |
| url | string | – | Public URL to fetch and audit instead of pasting text. Server-side fetched with SSRF guards. |
No output schema declared.
No examples provided.
run_fca_pro_check ~172
Run the full FCA UK financial-promotions self-audit for cryptoasset marketing (~25 rules). Section 21 FSMA, COBS 4.12A, PERG 8, the October 2023 cryptoasset regime, HTX precedent. Returns verdict + per-rule analysis + rewrite suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Optional hint to the auditor about asset type: landing_page | ad | email | x_post | kol_contract | whitepaper | press_release. |
| text | string | – | The marketing asset text to audit (landing-page copy, ad text, email body, X post, KOL contract, whitepaper excerpt, press release, etc.). |
| url | string | – | Public URL to fetch and audit instead of pasting text. Server-side fetched with SSRF guards. |
No output schema declared.
No examples provided.
run_gdpr_pro_check ~161
Run the full GDPR + ePrivacy marketing self-audit (~30 rules). Cookie banners, email/SMS opt-in, signup forms, privacy notices, marketing automation, ad-pixel placement. Returns verdict, per-rule analysis, and rewrite suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Optional hint to the auditor about asset type: landing_page | ad | email | x_post | kol_contract | whitepaper | press_release. |
| text | string | – | The marketing asset text to audit (landing-page copy, ad text, email body, X post, KOL contract, whitepaper excerpt, press release, etc.). |
| url | string | – | Public URL to fetch and audit instead of pasting text. Server-side fetched with SSRF guards. |
No output schema declared.
No examples provided.
run_mas_pro_check ~154
Run the full MAS Singapore DPT marketing self-audit (~35–40 rules). PS Act, Notice PSN02, January 2022 prohibition on public-space DPT advertising, AML/CFT communications requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Optional hint to the auditor about asset type: landing_page | ad | email | x_post | kol_contract | whitepaper | press_release. |
| text | string | – | The marketing asset text to audit (landing-page copy, ad text, email body, X post, KOL contract, whitepaper excerpt, press release, etc.). |
| url | string | – | Public URL to fetch and audit instead of pasting text. Server-side fetched with SSRF guards. |
No output schema declared.
No examples provided.
run_mica_pro_check ~161
Run the full MiCA (EU cryptoasset marketing) self-audit on a marketing asset. ~40 rules covering Title II–IV, ESMA guidance, and operator-grade interpretive notes. Returns verdict, per-rule analysis, and rewrite suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Optional hint to the auditor about asset type: landing_page | ad | email | x_post | kol_contract | whitepaper | press_release. |
| text | string | – | The marketing asset text to audit (landing-page copy, ad text, email body, X post, KOL contract, whitepaper excerpt, press release, etc.). |
| url | string | – | Public URL to fetch and audit instead of pasting text. Server-side fetched with SSRF guards. |
No output schema declared.
No examples provided.
run_sec_pro_check ~153
Run the SEC retail communications self-audit (~25 rules) for US-touching crypto marketing. FINRA Rule 2210, anti-fraud, Reg BI, finfluencer compensation disclosures, securities-status framing.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Optional hint to the auditor about asset type: landing_page | ad | email | x_post | kol_contract | whitepaper | press_release. |
| text | string | – | The marketing asset text to audit (landing-page copy, ad text, email body, X post, KOL contract, whitepaper excerpt, press release, etc.). |
| url | string | – | Public URL to fetch and audit instead of pasting text. Server-side fetched with SSRF guards. |
No output schema declared.
No examples provided.
run_tge_readiness_check ~205
Run the full TGE / token-launch marketing readiness audit (28 rules) across MiCA offer-to-public + Article 88, FCA financial promotions, SEC/Howey, MAS and VARA — in one multi-jurisdiction pass. For launch surfaces: landing page, airdrop/points page, staking copy, announcement thread, launch deck, KOL brief. Returns a per-market launch-readiness verdict, per-rule analysis, and concrete rewrites.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Optional hint to the auditor about asset type: landing_page | ad | email | x_post | kol_contract | whitepaper | press_release. |
| text | string | – | The marketing asset text to audit (landing-page copy, ad text, email body, X post, KOL contract, whitepaper excerpt, press release, etc.). |
| url | string | – | Public URL to fetch and audit instead of pasting text. Server-side fetched with SSRF guards. |
No output schema declared.
No examples provided.
run_vara_pro_check ~148
Run the full VARA Dubai marketing self-audit (~35–40 rules). Marketing & Promotions Rulebook, pre-approval requirements, KOL contracts, risk warnings, prohibited content.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Optional hint to the auditor about asset type: landing_page | ad | email | x_post | kol_contract | whitepaper | press_release. |
| text | string | – | The marketing asset text to audit (landing-page copy, ad text, email body, X post, KOL contract, whitepaper excerpt, press release, etc.). |
| url | string | – | Public URL to fetch and audit instead of pasting text. Server-side fetched with SSRF guards. |
No output schema declared.
No examples provided.
search_signals ~69
Text-search NorthPoint's signal feed for a keyword or phrase across competitor/regulatory/narrative entries.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (default 30, max 365). |
| query | string | yes | Free-text query — matches title, body, subject, tags. |
No output schema declared.
No examples provided.
What is the fi.northpoint/marketing-compliance MCP server?
fi.northpoint/marketing-compliance is an MCP server listed in the public MCP registry as fi.northpoint/marketing-compliance. Crypto marketing compliance rulesets over MCP: MiCA, FCA, GDPR, SEC, MAS, VARA. Not legal advice. This page covers its hosted endpoint (https://northpoint.fi/api/mcp).
Is the fi.northpoint/marketing-compliance MCP server safe to use?
fi.northpoint/marketing-compliance scores 89 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 fi.northpoint/marketing-compliance MCP server expose?
fi.northpoint/marketing-compliance exposes 13 tools: list_regimes, get_lite_ruleset, run_mica_pro_check, run_gdpr_pro_check, run_fca_pro_check, and 8 more. Their descriptions and schemas cost roughly 1,848 tokens of context every time the server is loaded.
Does the fi.northpoint/marketing-compliance MCP server require authentication?
Yes. fi.northpoint/marketing-compliance asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the fi.northpoint/marketing-compliance MCP server still maintained?
fi.northpoint/marketing-compliance is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.