_ registry / mcp http-sse · checked 1h ago

greener-ahead

https://app.greenerahead.com

Registry code: 6de4ea39a67289d2

api record

Public Greener Ahead tools: check which sustainability reporting rules apply to a company, and read the official text of a VSME or ESRS disclosure.

endpoint
https://app.greenerahead.com/mcp/public
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is greener-ahead live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is greener-ahead free to use?
Yes — the hub reached it with no key and no payment.
What tools does greener-ahead have?
2 tools: check_reporting_obligation, explain_disclosure.
Is greener-ahead safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
83ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_reporting_obligation unknown 1h ago

    Checks whether CSRD reporting applies to a company after the 2026 EU simplification, 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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "employees",
        "turnover_eur"
      ],
      "properties": {
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter country code, for example NL"
        },
        "asked_by": {
          "enum": [
            "bank",
            "customer",
            "tender",
            "investor",
            "none"
          ],
          "type": "string",
          "description": "Who is asking for sustainability information"
        },
        "employees": {
          "type": "integer",
          "maximum": 10000000,
          "minimum": 0,
          "description": "Average number of employees of the group"
        },
        "eu_parent": {
          "type": "boolean",
          "description": "True when the group is headed in the EU (default true)"
        },
        "turnover_eur": {
          "type": "number",
          "maximum": 10000000000000,
          "minimum": 0,
          "description": "Annual net turnover of the group in euros"
        }
      }
    }
    arguments 43 lines
  • explain_disclosure unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "standard",
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "maxLength": 12,
          "minLength": 2,
          "description": "Disclosure code, for example B3 or E1-8"
        },
        "language": {
          "enum": [
            "en",
            "nl",
            "de",
            "fr",
            "it",
            "es",
            "pl"
          ],
          "type": "string",
          "description": "The language the person writes in, for labels and headings, for example nl. Defaults to the AI app's locale, else English."
        },
        "standard": {
          "enum": [
            "vsme",
            "esrs"
          ],
          "type": "string"
        }
      }
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6de4ea39a67289d2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6de4ea39a67289d2/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6de4ea39a67289d2/badge.svg)](https://brick.blue/agent/6de4ea39a67289d2?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.