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

aether-layer-agent-service-gateway

https://aether-layer.com

Registry code: 1253f86e67c43b38

api record

Main tool: validate_vat (EU VAT number: local format/checksum for 27 member states + XI, then a live VIES check; never reports invalid because VIES is down). tools/list needs no key; tools/call needs an API key. Free key: POST https://aether-layer.com/api/v0/keys with body {} (no email); the key is shown once. Send it as Authorization: Bearer <key> or X-Api-Key. Free quota: 20 validate_vat calls per day (Europe/Rome); over quota the tools return payment_required. Docs: https://aether-layer.com/en/vat-api

endpoint
https://aether-layer.com/api/mcp?src=mcpreg
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 aether-layer-agent-service-gateway live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is aether-layer-agent-service-gateway free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does aether-layer-agent-service-gateway have?
2 tools: agent_readiness_check, validate_vat.
Is aether-layer-agent-service-gateway 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
424ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 2 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

_ what it can do 2 tools
2 auth-required 2 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.

  • agent_readiness_check auth-required 14h ago

    Deterministically grade an MCP tool catalog or a third-party x402 endpoint. Provide exactly one of: mcp_url (public https MCP server; initialize + tools/list), x402_url (public https resource; the gateway requests it WITHOUT an X-PAYMENT header and reads the 402), or tools (a JSON tool manifest). Never pays or signs a payment. No LLM is used. Requires an API key in Authorization: Bearer or X-Api-Key.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "tools": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string"
              },
              "annotations": {
                "type": "object",
                "properties": {
                  "title": {
                    "type": "string"
                  },
                  "readOnlyHint": {
                    "type": "boolean"
                  },
                  "openWorldHint": {
                    "type": "boolean"
                  },
                  "idempotentHint": {
                    "type": "boolean"
                  },
                  "destructiveHint": {
                    "type": "boolean"
                  }
                }
              },
              "description": {
                "type": "string"
              },
              "inputSchema": {}
            }
          },
          "description": "Tool manifest, as returned by tools/list."
        },
        "mcp_url": {
          "type": "string",
          "format": "uri",
          "description": "Public https URL of a remote MCP server (Streamable HTTP)."
        },
        "x402_url": {
          "type": "string",
          "format": "uri",
          "description": "Public https URL of a third-party x402 resource. The gateway never sends X-PAYMENT."
        }
      }
    }
    arguments 55 lines
  • validate_vat auth-required 14h ago

    Validate an EU VAT number (27 member states + XI Northern Ireland). Normalizes the input, checks the national format and checksum locally, then queries VIES (European Commission) live with limited retries. status: valid | invalid (local checksum/format failed, or VIES answered valid=false) | unverified_ms_down (the member state system is down) | unverified. Results are cached across instances to respect VIES rules: valid/invalid 24 h, unverified 10 min; checked_at = time of the original VIES check, cache_age_s = its age in seconds. Never returns invalid because VIES is unavailable. The VIES name/address are never returned: pass your own name and/or address to get name_match / address_match booleans, computed locally (not sent to VIES; null when VIES has no data). Requires an API key in Authorization: Bearer or X-Api-Key. Controllo automatico: regole locali di formato e checksum più una consultazione live del VIES (Commissione europea). Non è un'attestazione fiscale né una consulenza legale; i dati VIES provengono dalle banche dati degli Stati membri. Conserva una tua traccia della consultazione VIES. / Automated check: local format/checksum rules plus a live query of VIES (European Commission). Not a tax attestation and not legal advice; VIES data come from the member states' databases. Keep your own record of the VIES consultation. / Automatische Prüfung: lokale Format- und Prüfziffernregeln plus eine Live-Abfrage von VIES (Europäische Kommission). Keine steuerliche Bescheinigung und keine Rechtsberatung; die VIES-Daten stammen aus den Datenbanken der Mitgliedstaaten. Bewahren Sie einen eigenen Nachweis der VIES-Abfrage auf.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vat_id"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional company name to compare with the VIES record (local match, not sent to VIES, not stored). Returns name_match."
        },
        "client": {
          "type": "string",
          "maxLength": 48,
          "description": "Optional integration id <name>/<version>, e.g. shopware-plugin/0.1. Adoption metric only."
        },
        "vat_id": {
          "type": "string",
          "maxLength": 64,
          "description": "VAT number with country prefix, e.g. IT00905811006, DE143454214, EL094014201 (GR accepted), XI…; spaces, dots and dashes are ignored."
        },
        "address": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional address to compare with the VIES record (local match, not sent to VIES, not stored). Returns address_match."
        },
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Optional ISO prefix when vat_id has none (e.g. IT)."
        }
      }
    }
    arguments 35 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 1253f86e67c43b38.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1253f86e67c43b38/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/1253f86e67c43b38/badge.svg)](https://brick.blue/agent/1253f86e67c43b38?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.