# Delta Registry — Regulatory & Compliance Monitoring (28 tools)

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/stefanoseggio/delta-registry-website  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/delta-registry-regulatory-compliance-monitoring-28-tools

## Description
28 pay-per-event tools for regulatory, sanctions, procurement, and corporate-registry monitoring.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "delta-registry-regulatory-compliance-monitoring-28-tools": {
    "command": "npx",
    "args": ["-y","delta-registry-regulatory-compliance-monitoring-28-tools"]
  }
}
```

## Documentation & README

# Delta Registry — Marketing Website

[![Next.js](https://img.shields.io/badge/Next.js-14.2.5-000000?logo=next.js&logoColor=white)](https://nextjs.org/)
[![TypeScript](https://img.shields.io/badge/TypeScript-5.4.5-3178C6?logo=typescript&logoColor=white)](https://www.typescriptlang.org/)
[![Tailwind CSS](https://img.shields.io/badge/Tailwind%20CSS-3.4.4-38B2AC?logo=tailwind-css&logoColor=white)](https://tailwindcss.com/)
[![Deployed on Vercel](https://img.shields.io/badge/Deployed%20on-Vercel-000000?logo=vercel&logoColor=white)](https://vercel.com)

The public marketing site for **Delta Registry** — architecture explainer, pricing overview, and delta-engine internals for the full fleet of pay-per-event Apify Actors. Built with the Next.js App Router, React 18, and Tailwind CSS.

## Run it locally

```bash
npm install
npm run dev
```

Then open [http://localhost:3000](http://localhost:3000). `npm run build && npm run start` runs the production build; `npm run typecheck` and `npm run lint` run TypeScript and ESLint respectively.

## What's here

- `app/` — Next.js App Router pages and layouts. `app/page.tsx` composes every section
  (`Header`, `Hero`, `ArchitectureMatrix`, `HowItWorks`, `EconomicEngine`, `IntegrationTerminal`,
  `DeltaEngineDocs`, `FaqAccordion`, `Footer`) in render order; there is no other route.
- `components/` — one React component per site section. Sections that need interactivity
  (the fleet filter, the JSON delta-viewer playground, the accordion, the code-language tabs)
  are client components (`'use client'`); everything else renders on the server.
- `lib/` — the site's data contract. `lib/types.ts` defines the `Actor` shape; `lib/actors.ts`
  exports the real `ACTORS` array plus derived constants (`ACTOR_COUNT`, `DOMAINS`,
  `GITHUB_REPO_COUNT`).
- `middleware.ts` — edge middleware for the deployed site.

## Architecture: `lib/actors.ts` as the single source of truth

Every number, price, badge, and filter option rendered anywhere on this site — the hero stat
counters, the fleet catalog cards, the pricing comparison table, the BYOK disclosure, the
integration workbench's actor tabs, the FAQ's live counts — is read from the same `ACTORS` array
in `lib/actors.ts`, never hand-typed a second time in a component. Each `Actor` record carries
`slug`, `title`, `domain`, `jurisdiction`, `dataSource`, `pricing[]` (per-event-type price and
unit), `deltaEvents[]`, `storeUrl`, `githubUrl`, `byok` (`'required' | 'optional' | 'none'`, plus
`byokDetail` when applicable), `updateFrequency`, and `isPublic`.

This is deliberate, not incidental: it means a component can never drift out of sync with the
real fleet, and every price or claim on this marketing site traces back to one file that's
independently re-verified against each actor's own Apify Store listing and README whenever the
fleet changes. When an actor's price changes or a new actor launches, updating `lib/actors.ts` is
the only change needed — every section that references it (filters, cards, comparison tables,
code snippets) updates automatically.

## Security headers & CSP model

`next.config.js` sets standard hardening headers (`X-Frame-Options: DENY`,
`X-Content-Type-Options: nosniff`, `Strict-Transport-Security`, a restrictive
`Permissions-Policy`) globally. The Content-Security-Policy is set separately, per-request, in
`middleware.ts` — not as a static header — because a static `script-src 'self'` blocks Next.js's
own inline hydration/bootstrap scripts and breaks the app at runtime. Instead, `middleware.ts`
generates a fresh nonce on every request, threads it to Next.js via the `x-nonce` request header
(read in `app/layout.tsx`), and scopes the CSP to that nonce (`script-src 'self'
'nonce-<value>' 'strict-dynamic'`) rather than falling back to `'unsafe-inline'`, which would
defeat the policy's purpose. `'unsafe-eval'` is included only when `NODE_ENV === 'development'`
(webpack's Fast Refresh needs it) and is never present in the production CSP.

No compliance badges (SOC 2, ISO 27001, etc.) are displayed anywhere on this site — Delta
Registry holds no such certification, and the headers above are genuine engineering hardening,
not a marketing trust signal standing in for one.

## Environment variables

**None required.** This is a fully static-data marketing site — it reads `lib/actors.ts` at
build time and calls no external API, database, or authenticated service at runtime or during
the build. `npm install && npm run dev` (or `npm run build`) works with no `.env` file. The
`APIFY_TOKEN` references visible in this repo are inside display-only code-snippet strings in
`components/IntegrationTerminal.tsx` — example commands shown to site visitors for calling the
Apify API themselves, not a variable this app reads.

Deployed continuously on Vercel from the `main` branch.

## Quick Start for Enterprise

Every actor in this fleet is callable today from Claude Code, Claude Desktop, or Cursor via
Apify's own hosted MCP server — no custom integration, no SDK to install, no infrastructure to
run. The full closed-scope endpoint (all 28 actors, none of Apify's other 70,000+ Store actors in
scope), the exact verified client config for each tool, and the real per-tool BYOK/pricing/routing
notes are in [`MCP_INTEGRATION.md`](https://github.com/stefanoseggio/delta-registry-website/blob/HEAD/MCP_INTEGRATION.md).

To connect your own Claude Code or Cursor installation in one step, run the onboarding script for
your platform — each one prompts you for your own Apify API token (never logged, never written in
plaintext) and configures whichever client it finds installed:

```bash
# macOS / Linux / Git Bash on Windows
./connect_mcp.sh
```

```powershell
# Windows PowerShell
.\connect_mcp.ps1
```

This exact end-to-end path — real config injection, then a real live tool call through the actual
MCP wire protocol — was independently validated against a live actor run; see
[`LOCAL_MCP_VALIDATION_REPORT.md`](https://github.com/stefanoseggio/delta-registry-website/blob/HEAD/LOCAL_MCP_VALIDATION_REPORT.md) for the real run ID, latency,
and returned data from that test.

## About Delta Registry

Delta Registry is a pay-per-event regulatory and compliance data infrastructure operation built and operated by **Stefano Seggio** — 28 Apify Actors spanning government procurement, regulatory enforcement, patent/trademark monitoring, sanctions/compliance screening, corporate registries, and sovereign debt markets. Browse the full Actor catalog on the [Apify Store](https://apify.com/stefano_seggio) or [GitHub](https://github.com/stefanoseggio). For enterprise licensing or a custom monitor, connect on [LinkedIn](https://www.linkedin.com/in/stefanoseggio-deltaregistry).