# Greener Ahead: CSRD and VSME rules (remote · app.greenerahead.com)

Check whether CSRD applies after the 2026 simplification; read official VSME and ESRS disclosures.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `app.greenerahead.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-greenerahead-reporting-rules/mcp-public.md), [page](https://verifymcp.io/servers/com-greenerahead-reporting-rules/mcp-public)

## Channel facts

- Endpoint: `https://app.greenerahead.com/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 546 tokens (~273/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Greener Ahead: CSRD and VSME rules MCP server?

Greener Ahead: CSRD and VSME rules is a hosted endpoint at https://app.greenerahead.com/mcp/public, 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.

### Claude

```bash
claude mcp add --transport http com-greenerahead-reporting-rules 'https://app.greenerahead.com/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "com-greenerahead-reporting-rules": {
      "url": "https://app.greenerahead.com/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-greenerahead-reporting-rules": {
      "type": "http",
      "url": "https://app.greenerahead.com/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-greenerahead-reporting-rules]
url = "https://app.greenerahead.com/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-greenerahead-reporting-rules": {
      "type": "remote",
      "url": "https://app.greenerahead.com/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-greenerahead-reporting-rules --url 'https://app.greenerahead.com/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-greenerahead-reporting-rules:
    url: "https://app.greenerahead.com/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "com-greenerahead-reporting-rules": {
      "Transport": "http",
      "Url": "https://app.greenerahead.com/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-greenerahead-reporting-rules -t streamable-http -u 'https://app.greenerahead.com/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "com-greenerahead-reporting-rules": {
      "type": "http",
      "url": "https://app.greenerahead.com/mcp/public"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 79, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 79, +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.

### 2026-11-03 (score 78, +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.

### 2026-11-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 75, 0)

- [security] Tool “check_reporting_obligation” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 227 → 273
- [cosmetic] “check_reporting_obligation” added an optional parameter “balance_sheet_eur”
- [cosmetic] “check_reporting_obligation” added an optional parameter “employees_basis”
- [cosmetic] “check_reporting_obligation” added an optional parameter “listed”

### 2026-10-26 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 74, 0)

- [cosmetic] “check_reporting_obligation” reworded the description of “section”
- [cosmetic] “explain_disclosure” reworded the description of “section”

## MCP tools (2)

### `check_reporting_obligation` (~302 tokens)

Check reporting obligations

Checks whether CSRD reporting applies to a company after the 2026 EU simplification (or, for a company in France, under French law in force, with the French greenhouse gas report BEGES), whether the voluntary VSME standard and the value-chain cap are relevant, and whether the Dutch CO2-Prestatieladder matters. Uses headcount and turnover; no account needed.

Input parameters:

- `asked_by` (string): Who is asking for sustainability information
- `balance_sheet_eur` (number): Balance-sheet total in euros (used by the French size test)
- `country` (string): Two-letter country code, for example NL
- `cursor` (string): nextCursor from an earlier result of this tool.
- `employees` (integer, required): Average number of employees of the group
- `employees_basis` (string): How employees was counted (the French BEGES threshold counts full-time equivalents under C. trav. L1111-2)
- `eu_parent` (boolean): True when the group is headed in the EU (default true)
- `listed` (boolean): True when listed on an EU regulated market
- `section` (string): One part of a shortened result: a "$section" path from an earlier result of this tool, for example items/0/adoption. The other arguments stay as before, and cursor pages a long part.
- `turnover_eur` (number, required): Annual net turnover of the group in euros

### `explain_disclosure` (~210 tokens)

Read an official disclosure text

Returns the official text of a disclosure in the EU voluntary standard for SMEs (VSME, B1-B11 and C1-C9) or in the ESRS (2026 edition, for example E1-8 or S1-5), with its EUR-Lex link. ESRS text is available in English, Dutch, German, French, Italian, Spanish and Polish.

Input parameters:

- `code` (string, required): Disclosure code, for example B3 or E1-8
- `cursor` (string): nextCursor from an earlier result of this tool.
- `language` (string): The language the person writes in, for labels and headings, for example nl. Defaults to the AI app's locale, else English.
- `section` (string): One part of a shortened result: a "$section" path from an earlier result of this tool, for example items/0/adoption. The other arguments stay as before, and cursor pages a long part.
- `standard` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-greenerahead-reporting-rules/mcp-public#diagnostics

## Score history

- 2026-11-06: 79
- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 73
- 2026-10-19: 73

## Common questions

### What is the Greener Ahead: CSRD and VSME rules MCP server?

Greener Ahead: CSRD and VSME rules is an MCP server listed in the public MCP registry as com.greenerahead/reporting-rules. Check whether CSRD applies after the 2026 simplification; read official VSME and ESRS disclosures. This page covers its hosted endpoint (https://app.greenerahead.com/mcp/public).

### Is the Greener Ahead: CSRD and VSME rules MCP server safe to use?

Greener Ahead: CSRD and VSME rules scores 79 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 Greener Ahead: CSRD and VSME rules MCP server expose?

Greener Ahead: CSRD and VSME rules exposes 2 tools: check_reporting_obligation, explain_disclosure. Their descriptions and schemas cost roughly 512 tokens of context every time the server is loaded.

### Does the Greener Ahead: CSRD and VSME rules MCP server require authentication?

No. We connected to Greener Ahead: CSRD and VSME rules without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Greener Ahead: CSRD and VSME rules MCP server still maintained?

Greener Ahead: CSRD and VSME rules is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Greener Ahead: CSRD and VSME rules MCP server?

VerifyMCP ran 13 checks on Greener Ahead: CSRD and VSME rules, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://app.greenerahead.com/mcp/public
- Website: https://greenerahead.com/ai-assistants
- Changelog RSS feed: https://verifymcp.io/servers/com-greenerahead-reporting-rules/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-greenerahead-reporting-rules/mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-greenerahead-reporting-rules/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/com-greenerahead-reporting-rules/mcp-public