_ registry / mcp streamable-http · checked 56m ago

E-Invoice Map

https://einvoicemap.com

Registry code: 12fe878426ae01f8

api record

E-Invoice Map answers questions about e-invoicing mandates and the providers that serve them, from public data that anyone can read at the linked pages. All tools are read-only and free; nothing you send is stored.

- Mandate dates, validation-error explanations and foreign-supplier rules come from official sources; every answer lists its source_url and the date it was checked (captured_at / checked_on). Quote the source when you cite a date.

endpoint
https://einvoicemap.com/api/v1/mcp
protocol
streamable-http ·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 E-Invoice Map live?
Yes — it answered the hub's last check (checked 56m ago). It answered 100% of checks over the last 30 days.
Is E-Invoice Map free to use?
Yes — the hub reached it with no key and no payment.
What tools does E-Invoice Map have?
7 tools: providers, provider, lookup_access_point, explain_validation_error, foreign_supplier_scope, deadlines, directory_counts.
Is E-Invoice Map 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
322ms

last good check

priced tools
0

of 7 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

_ what it can do 7 tools
2 open 5 never probed 2 of 7 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.

  • deadlines open 56m ago

    Dates when e-invoicing becomes mandatory, per country (or all countries), each with its official source_url and the date it was checked. Country is a two-letter code such as 'be', 'de', 'ae' or a country name; leave it out for all countries.

    mcp-tool

    {
      "type": "object",
      "title": "deadlines_toolArguments",
      "properties": {
        "country": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Country",
          "default": null
        }
      }
    }
    arguments 18 lines
  • directory_counts open 56m ago

    How many businesses are listed in the Peppol network directory, per country, with the change since the last day (source: Peppol Directory (OpenPeppol AISBL)). Country is a two-letter code or 'all'; leave it out for every country.

    mcp-tool

    {
      "type": "object",
      "title": "counts_toolArguments",
      "properties": {
        "country": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Country",
          "default": null
        }
      }
    }
    arguments 18 lines
  • providers unknown never probed

    E-invoicing providers we track in a country (two-letter code), alphabetical by product name, with a link to each provider's page. The order never depends on payment; ads and affiliate links are not included.

    mcp-tool

    {
      "type": "object",
      "title": "providers_toolArguments",
      "required": [
        "country"
      ],
      "properties": {
        "country": {
          "type": "string",
          "title": "Country"
        }
      }
    }
    arguments 13 lines
  • provider unknown never probed

    Profile of one tracked provider by name or id (for example 'billit'): what it can do, formats, languages, free plan and prices, each price with its source and check date.

    mcp-tool

    {
      "type": "object",
      "title": "provider_toolArguments",
      "required": [
        "name_or_slug"
      ],
      "properties": {
        "name_or_slug": {
          "type": "string",
          "title": "Name Or Slug"
        }
      }
    }
    arguments 13 lines
  • lookup_access_point unknown never probed

    For a business identifier you give (for example a Belgian company number or a Peppol ID such as 0208:0521875440), find the access-point provider that receives its e-invoices on the Peppol network: provider organisation, SMP host, document types, certificate validity. Provider metadata only. Limited per day; when the limit is reached the answer points to the free lookup on the website. Country is an optional two-letter hint.

    mcp-tool

    {
      "type": "object",
      "title": "lookup_toolArguments",
      "required": [
        "identifier"
      ],
      "properties": {
        "country": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Country",
          "default": null
        },
        "identifier": {
          "type": "string",
          "title": "Identifier"
        }
      }
    }
    arguments 25 lines
  • explain_validation_error unknown 56m ago

    Plain-language explanation of a common e-invoice validation rule such as 'BR-CO-10' or 'PEPPOL-EN16931-R120': what it means, usual causes, how to fix it and who fixes it.

    mcp-tool

    {
      "type": "object",
      "title": "explain_toolArguments",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "title": "Code"
        }
      }
    }
    arguments 13 lines
  • foreign_supplier_scope unknown never probed

    Whether a supplier with no establishment in a country must e-invoice there, from our 47-country table: the system, the B2B status and what applies to foreign suppliers, with official sources. Country is a two-letter code or an English name.

    mcp-tool

    {
      "type": "object",
      "title": "foreign_toolArguments",
      "required": [
        "country"
      ],
      "properties": {
        "country": {
          "type": "string",
          "title": "Country"
        }
      }
    }
    arguments 13 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 12fe878426ae01f8.

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

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.