fi.northpoint/marketing-compliance
fi.northpoint/marketing-compliance · 1.0.0
Crypto marketing compliance rulesets over MCP: MiCA, FCA, GDPR, SEC, MAS, VARA. Not legal advice.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://northpoint.fi/api/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 13 tools.
- Protocol
- 2025-06-18
- Calls itself
- northpoint-mcp 1.0.0
- Handshake time
- 277 ms
- HTTP status
- 200
The tools it lists (13, as of 24 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
list_regimesList 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.
get_lite_rulesetReturn 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).
run_mica_pro_checkRun 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.
run_gdpr_pro_checkRun 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.
run_fca_pro_checkRun 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.
run_sec_pro_checkRun 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
fi.northpoint/marketing-compliance, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 53 days ago. The registry entry · northpoint.fi