Sviluppo · Server MCP locale

Consent Proof Record Lint

Reads the consent record your code stored and names every proof field GDPR Article 7(1) needs and yo.

Cosa indica il MCP Registry

La voce come pubblicata nel MCP Registry ufficiale (consultazione: 4 ottobre 2026), ultima versione.

Nome nel registro: io.github.jmshinhwa/consent-proof-record-lint
Versione: 1.0.1
Stato: Attivo
Categoria: sviluppo
Trasporto: stdio (processo locale)
Pacchetto: npm
Pubblicato: 19 settembre 2026
Aggiornato: 19 settembre 2026
Editore: jmshinhwa (GitHub) · 144 server con una pagina qui
Namespace: Namespace verificato dal MCP Registry tramite GitHub (github.com/jmshinhwa) · come funziona
Repository: github.com/jmshinhwa/readystack-themes
Fonte: Voce nell’API del registro

Pacchetti

Registro	Pacchetto	Versione	Trasporto	Variabili d’ambiente
npmruntime: npx	@readystack/consent-proof-record-lint	1.0.1	stdio	Nessuna dichiarata

Come collegare Consent Proof Record Lint

Consent Proof Record Lint viene eseguito in locale a partire da un pacchetto Node.js pubblicato nel registro npm: @readystack/consent-proof-record-lint, versione 1.0.1. Comunica via MCP su stdio, quindi il client lo avvia come programma e dialoga con esso tramite standard input e standard output. Richiede Node.js; i client in genere lo avviano con npx - il comando abituale è npx -y @readystack/consent-proof-record-lint@1.0.1.

Nel formato JSON mcpServers, letto da molti client MCP desktop e per editor di codice, la voce si presenta così (segnaposto tra parentesi angolari):

{
  "mcpServers": {
    "consent-proof-record-lint": {
      "command": "npx",
      "args": [
        "-y",
        "@readystack/consent-proof-record-lint@1.0.1"
      ]
    }
  }
}

Ricavato dalla voce del registro, non testato qui. Cosa fa il server, e a quali condizioni, lo stabilisce il suo editore; prima di concedergli l’accesso ai propri account o file conviene consultarne il repository o il sito web. Come aggiungere un server MCP a un assistente · Prima di collegare un server

Altri server di jmshinhwa (GitHub)

Tutti e 144 →

Server	Esecuzione	Endpoint o pacchetto
Cloud Cost Landmine LintNames every line in the file you have open that starts a recurring cloud charge, with the published.	Locale · stdio	npm: @readystack/cloud-cost-landmine-lint
Cloud Manifest Audit KitFor platform engineers on AKS: 28 rules naming every removed apiVersion, literal credential and:lat.	Locale · stdio	npm: @readystack/cloud-manifest-audit-kit
Cms 0057 Api Gate14 rules read a FHIR CapabilityStatement against CMS-0057-F. A 2021 payer statement returned 6 block.	Locale · stdio	npm: @readystack/cms-0057-api-gate
Config Dsl Lint Snippet PackYour config files are never compiled - nothing fails until deploy. 36 snippets and 28 lint rules for.	Locale · stdio	npm: @readystack/config-dsl-lint-snippet-pack
Connection String Secret Audit26 rules and 32 safe-replacement snippets for hardcoded connection strings, keys and kubeconfigs acr.	Locale · stdio	npm: @readystack/connection-string-secret-audit
Consent Audit EuFinds the analytics, pixels, fonts and embeds that fire before your cookie banner is answered - in t.	Locale · stdio	npm: @readystack/consent-audit-eu
Container Hardening 800 190Reads a Dockerfile or compose file and names the hardening controls it fails, with the NIST SP 800-1.	Locale · stdio	npm: @readystack/container-hardening-800-190
Coverage Gate LintFinds the coverage gates in your repo that can never fail a build.	Locale · stdio	npm: @readystack/coverage-gate-lint
Cra 24 72 14 Reporting LintReads your SECURITY.md against the EU Cyber Resilience Act reporting clock that started on 11 Septem.	Locale · stdio	npm: @readystack/cra-24-72-14-reporting-lint
Cra Annex Ii Docs Lint19 rules over the user documentation that ships with your product: support-period end date, vulnerab.	Locale · stdio	npm: @readystack/cra-annex-ii-docs-lint
Cra Readiness AuditFlags the lines in your repo that break the EU Cyber Resilience Act - default passwords, disabled TL.	Locale · stdio	npm: @readystack/cra-readiness-audit
Cron Schedule LintNames every schedule line in the file you have open that fires at the wrong hour, twice, or never at.	Locale · stdio	npm: @readystack/cron-schedule-lint

Altri server della categoria sviluppo

Tutti e 5152 →

Server	Esecuzione	Endpoint o pacchetto
ConnectionsAWS, GitHub and connected services from your agent, no keys to paste, plus local shell and browser.	Locale · stdio	npm: connections-mcp
Connectivity IndexMachine-readable FCC pre-diligence corpus for multifamily broadband infrastructure scenarios.	Remoto · HTTPVerifica live: ✗ nessun handshake	connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev
ConnectWise Control MCPManage ConnectWise Control (ScreenConnect) remote support and access sessions from one CLI or agent.	Locale · stdio	MCP Bundle (.mcpb): Servosity/msp-skills/releases/download/connectwi
ConsensusCoordination for AI coding agents: declare plans, catch design conflicts early, share team memory.	Remoto · HTTPVerifica live: ✗ nessun handshake	consensus-production-aed6.up.railway.app
ConsentLayerCookie consent for GDPR/CCPA: scan sites for trackers, configure consent banners, get install code.	Remoto · HTTPVerifica live: accesso richiesto	api.consentlayer.com
Constitution LintStatic linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks.	Remoto · HTTPVerifica live: ✓ handshake	agentopskit.dev
Constitution LintStatic linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks.	Remoto · HTTPVerifica live: ✓ handshake	agentopskit.dev
Constraints RegistryPolicy-as-code guardrails for AI coding agents, validated via OPA, Conftest, Checkov & Semgrep.	Locale · stdio	PyPI: constraints-registry