Greener Ahead: CSRD and VSME rules MCP server
com.greenerahead/reporting-rulesgreenerahead.comstreamable-httpv1.1.0Scanned
Check whether CSRD applies after the 2026 simplification; read official VSME and ESRS disclosures.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Greener Ahead: CSRD and VSME rules MCP server can do
The Greener Ahead: CSRD and VSME rules MCP server is published by greenerahead.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: check_reporting_obligation and explain_disclosure), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
check_reporting_obligationChecks 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 B…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check reporting obligations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
explain_disclosureReturns 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 l…1 finding
Why it is in this group
- The name "explain_disclosure" says "explain": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "explain_disclosure" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_disclosure" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read an official disclosure text
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:39 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://app.greenerahead.com/.well-known/oauth-protected-resource/mcp/public
- Authorization servers
- https://humorous-curve-85.authkit.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.greenerahead.com/mcp/public: tools/list returned 2 tools to an anonymous client, including check_reporting_obligation (write), explain_disclosure (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "explain_disclosure" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_disclosure" says "explain": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:check_reporting_obligationChanges thingsdescriptioninputSchema
- Changed:explain_disclosureChanges thingsinputSchema
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http reporting-rules https://app.greenerahead.com/mcp/publicclaude mcp add --transport http reporting-rules https://app.greenerahead.com/mcp/publicRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__reporting-rules__check_reporting_obligation",
"mcp__reporting-rules__explain_disclosure"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as reporting-rules. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.greenerahead/reporting-rules/verify?hash=4b99a93f1eba6d46d53f64765dcff7cc30754e318d7d92339b942714e6f46848" | jq -e '.changed == false'Pinned hash 4b99a93f1eba, from Nov 13, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.greenerahead/reporting-rules/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.greenerahead/reporting-rules)Source: MCP Registry. Synced Oct 21, 2026, 17:56 UTC.
Greener Ahead: CSRD and VSME rules MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Greener Ahead: CSRD and VSME rules MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Greener Ahead: CSRD and VSME rules MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Greener Ahead: CSRD and VSME rules MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Greener Ahead: CSRD and VSME rules MCP server have?
- 2 tools: 2 write. check_reporting_obligation and explain_disclosure.
Does the Greener Ahead: CSRD and VSME rules MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Greener Ahead: CSRD and VSME rules MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Greener Ahead: CSRD and VSME rules MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.