Greener Ahead: CSRD and VSME rules
REMOTE · APP.GREENERAHEAD.COM
Check whether CSRD applies after the 2026 simplification; read official VSME and ESRS disclosures.
Available components
Last scanned (9 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 0
- Tool “check_reporting_obligation” rewrote its description, which is the text the model reads security
- Schema quality: 227 → 273 ▼ functional
- “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” cosmetic
- 26 Oct 26 +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.
- 25 Oct 26 0
- “check_reporting_obligation” reworded the description of “section” cosmetic
- “explain_disclosure” reworded the description of “section” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 24 Oct 26 0
- Schema quality: 163 → 227 ▼ functional
- “check_reporting_obligation” added an optional parameter “cursor” cosmetic
- “check_reporting_obligation” added an optional parameter “section” cosmetic
- “explain_disclosure” added an optional parameter “cursor” cosmetic
- “explain_disclosure” added an optional parameter “section” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://app.greenerahead.com/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.greenerahead.com | CN=YE2,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 55adc46ce6f4ee99da1a6e52b065e9910d7 |
| SANs: app.greenerahead.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of app.greenerahead.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| greenerahead.com. | DS published | 38272 | 13 | Verified |
| app.greenerahead.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; connect-src 'self' wss: https://greener-ahead-production-application-293843984323.s3.eu-central-1.amazonaws.com; font-src 'self' data:; form-action 'self'; frame-ancestors 'none'; img-src 'self' data: blob:; object-src 'none'; script-src 'self'; style-src 'self' 'unsafe-inline'; worker-src 'self' blob: |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), display-capture=(), geolocation=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.greenerahead.com/mcp/public | Verified | 200 | |
| http (plaintext) | http://app.greenerahead.com/mcp/public | HTTPS enforced | 308 | https://app.greenerahead.com/mcp/public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_reporting_obligation Check reporting obligations ~302
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Annual net turnover of the group in euros |
No output schema declared.
No examples provided.
explain_disclosure Read an official disclosure text ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 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 | yes | – |
No output schema declared.
No examples provided.
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.
remote · app.greenerahead.com
claude mcp add --transport http com-greenerahead-reporting-rules 'https://app.greenerahead.com/mcp/public'
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 5 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.