pulsenetwork

compliancepulse

CompliancePulse: The regulatory applicability layer. 14 endpoints: global LEI entity verification (GLEIF, $0.02), OFAC sanctions screening ($0.02), EU VAT validation ($0.01), deterministic deadline check (deferral-aware, tracks EU AI Act Official Journal status, $0.02), EU AI Act risk classification ($0.25), company applicability scan — which regimes bind this business, ranked ($1.50), plus data privacy law (145+ jurisdictions), KYC/AML, corporate, employment, sector, cyber (NIS2/DORA), ESG (CSRD/ISSB) briefs and regulatory news

Coverage: Global

Endpoints: • privacy ($0.15): Data privacy law by jurisdiction • kyc ($0.12): KYC/AML requirements by jurisdiction • corporate ($0.15): Corporate compliance and entity setup • employment ($0.15): Employment law and HR compliance • sector ($0.15): Industry-specific regulatory compliance • cyber ($0.12): Cybersecurity compliance requirements • esg ($0.12): ESG and sustainability reporting requirements • news ($0.08): Regulatory intelligence and enforcement news • deadlines ($0.02): Compliance deadline check — deterministic, deferral-aware • ai-act ($0.25): EU AI Act applicability check — risk class, obligations, current deadline state • scan ($1.50): Company regulatory applicability scan — which rules apply to this business • lei ($0.02): Global legal-entity (LEI) lookup and company search via GLEIF — deterministic • sanctions ($0.02): OFAC sanctions screening — deterministic, alias-aware • vat ($0.01): EU VAT number validation via VIES — deterministic • scan-lite ($0.25): Company regulatory applicability preview — agent-budget tier

Input Schema

TableJSON Schema

Name	Required	Description
`lei`	No	20-character LEI to look up. Checksum-verified (ISO 7064 mod-97-10) before any registry call — a malformed LEI never burns the lookup.
`vat`	No	Full EU VAT id, with or without the country prefix
`gpai`	No	true if you build or fine-tune a general-purpose model
`lang`	No	lang
`name`	No	Legal entity name to search. Used when lei is not provided; falls back to fuzzy matching for typos and transliterations. Provide lei OR name.
`role`	No	provider \| deployer \| importer \| distributor (default deployer)
`size`	No	micro \| small \| medium \| large \| listed
`type`	No	Narrow by entity type
`topic`	No	privacy \| kyc \| corporate \| employment \| sector \| cyber \| esg \| all
`action`	Yes	Which endpoint to call. Options: privacy \| kyc \| corporate \| employment \| sector \| cyber \| esg \| news \| deadlines \| ai-act \| scan \| lei \| sanctions \| vat \| scan-lite
`listed`	No	true \| false — listed companies have additional disclosure requirements
`sector`	No	fintech \| banking \| crypto \| real-estate \| legal \| accounting \| casino
`context`	No	Business context — e.g. SaaS company, healthcare, e-commerce, fintech
`country`	No	Country or jurisdiction — e.g. Germany, California, China, Brazil, Singapore. Also accepts 'jurisdiction'
`category`	No	ai \| privacy \| esg \| cyber \| financial \| supply-chain \| product \| corporate \| consumer
`use_case`	No	What the AI system does, in plain language
`framework`	No	NIS2 \| DORA \| NIST \| ISO27001 \| SOC2 \| CMMC — or omit for country-based analysis
`threshold`	No	Match score cutoff 0-100. Default 85. Lower = more (noisier) hits.
`activities`	No	CSV of: ai, personal-data, eu-sales, eu-operations, financial-services, crypto, listed, eu-imports, online-platform, us-operations, uk-operations, card-payments, products-eu, commodities
`entity_type`	No	Entity type — e.g. Ltd, GmbH, BV, SAS, Pvt Ltd, LLC
`within_days`	No	Only regimes with an upcoming date within N days
`worker_type`	No	contractor \| employee \| freelancer \| gig — focus the classification risk analysis. Also accepts 'type'
`company_size`	No	large \| medium \| small — determines which mandatory frameworks apply. Also accepts 'size'

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 25, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: privacy | kyc | corporate | employment | sector | cyber | esg | news | deadlines | ai-act | scan | lei | sanctions | vat"New value: +"Which endpoint to call. Options: privacy | kyc | corporate | employment | sector | cyber | esg | news | deadlines | ai-act | scan | lei | sanctions | vat | scan-lite"

changedInput schema / properties / action / enum

Previous value: -[
-  "privacy",
-  "kyc",
-  "corporate",
-  "employment",
-  "sector",
-  "cyber",
-  "esg",
-  "news",
-  "deadlines",
-  "ai-act",
-  "scan",
-  "lei",
-  "sanctions",
-  "vat"
-]New value: +[
+  "privacy",
+  "kyc",
+  "corporate",
+  "employment",
+  "sector",
+  "cyber",
+  "esg",
+  "news",
+  "deadlines",
+  "ai-act",
+  "scan",
+  "lei",
+  "sanctions",
+  "vat",
+  "scan-lite"
+]

Changed5 schema fields changedJul 21, 2026

changedInput schema / properties / lei / description

Previous value: -"20-character LEI to look up (provide lei OR name)"New value: +"20-character LEI to look up. Checksum-verified (ISO 7064 mod-97-10) before any registry call — a malformed LEI never burns the lookup."

changedInput schema / properties / name / description

Previous value: -"Legal entity name to search, fuzzy fallback for typos (provide lei OR name)"New value: +"Legal entity name to search. Used when lei is not provided; falls back to fuzzy matching for typos and transliterations. Provide lei OR name."

changedInput schema / properties / threshold / description

Previous value: -"Match threshold 0-100 (default 85)"New value: +"Match score cutoff 0-100. Default 85. Lower = more (noisier) hits."

changedInput schema / properties / type / description

Previous value: -"individual | entity | vessel | aircraft"New value: +"Narrow by entity type"

changedInput schema / properties / vat / description

Previous value: -"Full EU VAT id, with or without country prefix"New value: +"Full EU VAT id, with or without the country prefix"

Changed7 schema fields changedJul 14, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: privacy | kyc | corporate | employment | sector | cyber | esg | news | deadlines | ai-act | scan"New value: +"Which endpoint to call. Options: privacy | kyc | corporate | employment | sector | cyber | esg | news | deadlines | ai-act | scan | lei | sanctions | vat"

changedInput schema / properties / action / enum

Previous value: -[
-  "privacy",
-  "kyc",
-  "corporate",
-  "employment",
-  "sector",
-  "cyber",
-  "esg",
-  "news",
-  "deadlines",
-  "ai-act",
-  "scan"
-]New value: +[
+  "privacy",
+  "kyc",
+  "corporate",
+  "employment",
+  "sector",
+  "cyber",
+  "esg",
+  "news",
+  "deadlines",
+  "ai-act",
+  "scan",
+  "lei",
+  "sanctions",
+  "vat"
+]

addedInput schema / properties / lei

Added value: +{
+  "description": "20-character LEI to look up (provide lei OR name)",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Legal entity name to search, fuzzy fallback for typos (provide lei OR name)",
+  "type": "string"
+}

addedInput schema / properties / threshold

Added value: +{
+  "description": "Match threshold 0-100 (default 85)",
+  "type": "string"
+}

addedInput schema / properties / type

Added value: +{
+  "description": "individual | entity | vessel | aircraft",
+  "type": "string"
+}

addedInput schema / properties / vat

Added value: +{
+  "description": "Full EU VAT id, with or without country prefix",
+  "type": "string"
+}

Changed9 schema fields changedJul 10, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: privacy | kyc | corporate | employment | sector | cyber | esg | news"New value: +"Which endpoint to call. Options: privacy | kyc | corporate | employment | sector | cyber | esg | news | deadlines | ai-act | scan"

changedInput schema / properties / action / enum

Previous value: -[
-  "privacy",
-  "kyc",
-  "corporate",
-  "employment",
-  "sector",
-  "cyber",
-  "esg",
-  "news"
-]New value: +[
+  "privacy",
+  "kyc",
+  "corporate",
+  "employment",
+  "sector",
+  "cyber",
+  "esg",
+  "news",
+  "deadlines",
+  "ai-act",
+  "scan"
+]

addedInput schema / properties / activities

Added value: +{
+  "description": "CSV of: ai, personal-data, eu-sales, eu-operations, financial-services, crypto, listed, eu-imports, online-platform, us-operations, uk-operations, card-payments, products-eu, commodities",
+  "type": "string"
+}

addedInput schema / properties / category

Added value: +{
+  "description": "ai | privacy | esg | cyber | financial | supply-chain | product | corporate | consumer",
+  "type": "string"
+}

addedInput schema / properties / gpai

Added value: +{
+  "description": "true if you build or fine-tune a general-purpose model",
+  "type": "string"
+}

addedInput schema / properties / role

Added value: +{
+  "description": "provider | deployer | importer | distributor (default deployer)",
+  "type": "string"
+}

addedInput schema / properties / size

Added value: +{
+  "description": "micro | small | medium | large | listed",
+  "type": "string"
+}

addedInput schema / properties / use_case

Added value: +{
+  "description": "What the AI system does, in plain language",
+  "type": "string"
+}

addedInput schema / properties / within_days

Added value: +{
+  "description": "Only regimes with an upcoming date within N days",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

C2.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It does disclose some behavioral traits: several endpoints are labeled 'deterministic' (lei, deadlines, sanctions, vat), and it notes checksum verification for LEI and deferral-awareness for deadlines. However, it does not cover response format, error behavior, rate limits, or whether the tool is read-only. The price list adds cost context but not behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is an extensive catalog with prices, formatting, and a minor inconsistency ('14 endpoints' but 15 listed). It lacks a concise summary of the tool's core function and buries the essential 'regulatory applicability layer' behind a wall of endpoint listings. It is not front-loaded with the most decision-relevant information for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (15 endpoints, 23 params, no output schema), the description enumerates capabilities but fails to explain how the tool should be invoked holistically. It doesn't state that 'action' is required, how other parameters map to endpoints, or what the common response structure looks like. The endpoint blurbs provide partial return-value hints but leave the agent to guess how to combine parameters and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description's endpoint list adds context to the 'action' parameter, and some endpoint descriptions (e.g., 'scan' returns ranked regimes) hint at what parameters like 'company_size' or 'context' are for, but the description does not systematically explain parameter relationships. It mostly relies on the schema's already detailed parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'CompliancePulse: The regulatory applicability layer,' which is a vague abstraction rather than a concrete verb+resource. It then lists 15 endpoints with brief descriptions, which clarifies that this is a multi-endpoint compliance API, but the overall purpose remains diffuse and it doesn't clearly distinguish itself from other Pulse tools beyond the obvious compliance domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no explicit guidance on when to use this tool versus alternatives. It doesn't mention exclusions, prerequisites, or scenarios like 'use for regulatory checks.' The endpoint list implies various use cases, but there is no direct instruction on selecting compliancepulse over a sibling (e.g., taxpulse, esgpulse).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pulsenetwork tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation4/5

Each tool has a unique domain prefix (e.g., airdroppulse, alphapulse, arbipulse) making them mostly distinguishable at a glance. A few adjacent verticals like careerpulse vs talentpulse or marketpulse vs dealpulse have overlapping themes, but their descriptions clarify the distinct focus. The utility tools (catalog_search, discover, get_openapi_spec, x402_troubleshoot) are also clearly distinct in role. However, the sheer number of similar 'pulse' names could still cause misselection without reading descriptions.

Naming Consistency4/5

The dominant naming convention is `<domain>pulse` (e.g., climatepulse, cryptopulse, edupulse), which is highly consistent and predictable. Exceptions like catalog_search, discover, get_openapi_spec, x402_troubleshoot, and stateedge break the pattern, but these are few and serve obvious utility purposes. Overall, the convention is clear and easily learnable.

Tool Count2/5

With 80 tools, the server presents an extremely large and potentially overwhelming surface. While each tool represents a distinct intelligence vertical and navigation aids exist (catalog_search, discover, get_openapi_spec), the count far exceeds the typical 3-15 range for coherent agent use and even the 'heavy' 16-25 range. The burden of selecting the correct vertical from 80 options is significant, despite clear naming.

Completeness5/5

The server offers an exceptionally broad and deep coverage of domains, from finance and health to agriculture and gaming. Each vertical includes multiple endpoints that address core operations for its domain, such as search, analysis, comparisons, deterministic checks, and even action-oriented tools like letter generators and physical mail. The presence of free discovery and troubleshooting tools fills potential gaps, leaving no obvious dead ends in the overall tool surface.

compliancepulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources