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

boring-api

https://api.relaex-engineers.de

Registry code: 270a932d4e9c8d49

api record

Boring API: small, deterministic analysis tools for business tables. supplier_compare compares an old and a new supplier price list (CSV, XLSX, DATANORM or PDF) and returns real unit price changes, new and removed items and review priorities. documents_tables extracts tables from a text-based PDF with page and bounding box. merchant_validate checks a product feed for Google Merchant Center, Shopify or Meta and returns issues with fix hints. Pass files as Base64 with their filename (local stdio also accepts paths). Column headers are recognised in many languages; responses are English and…

endpoint
https://api.relaex-engineers.de/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 boring-api live?
Yes — it answered the hub's last check (checked 32m ago). It answered 100% of checks over the last 30 days.
Is boring-api free to use?
Not measured yet.
What tools does boring-api have?
3 tools: merchant_validate, documents_tables, supplier_compare.
Is boring-api 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
627ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • merchant_validate unknown 32m ago

    Use when a user wants to check a product feed or catalog export before uploading it to Google Merchant Center, Shopify or Meta (Facebook/Instagram). Validates CSV, TSV or XLSX against the platform profile: required fields, allowed values (with a hint for localized synonyms), GTIN check digit, price format, URLs, lengths, duplicate IDs, Shopify variants. Every issue names row, column, rule code and a fix hint; nothing is changed automatically.

    mcp-tool

    {
      "type": "object",
      "title": "merchant_validateArguments",
      "properties": {
        "options": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Options",
          "default": null,
          "description": "Optional ValidateOptions, e.g. {\"sheet\": \"Feed\", \"column_overrides\": {\"gtin\": \"EAN code\"}, \"max_issues\": 500}. Schema: /v1/schemas/merchant-validate-options."
        },
        "profile": {
          "type": "string",
          "title": "Profile",
          "default": "google_merchant",
          "description": "Target platform: google_merchant, shopify_products_csv or meta_catalog."
        },
        "filename": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Filename",
          "default": null,
          "description": "Original filename including extension (e.g. prices.xlsx); used to detect the format."
        },
        "file_path": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "File Path",
          "default": null,
          "description": "Local file path; only allowed when the server runs locally over stdio."
        },
        "file_base64": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "File Base64",
          "default": null,
          "description": "The feed file. File content encoded as Base64 (standard alphabet). Max 20 MiB decoded."
        }
      }
    }
    arguments 65 lines
  • documents_tables unknown 32m ago

    Use when a user has a PDF (price list, data sheet, report, invoice annex) and needs its tables as data. Extracts tables from a text-based PDF (up to 20 MiB, 60 pages) with page, bounding box and a quality level per table; detects header rows, titles and footnotes and merges tables continued across pages only with evidence. Scanned pages are reported as OCR_REQUIRED, nothing is guessed. Works with any language embedded in the PDF. To compare two PDF price lists, call supplier_compare directly.

    mcp-tool

    {
      "type": "object",
      "title": "documents_tablesArguments",
      "properties": {
        "options": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Options",
          "default": null,
          "description": "Optional TablesOptions, e.g. {\"pages\": \"1-3,7\", \"strategy\": \"auto\", \"include_cells\": false}. Schema: /v1/schemas/documents-tables-options."
        },
        "filename": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Filename",
          "default": null,
          "description": "Original filename including extension (e.g. prices.xlsx); used to detect the format."
        },
        "file_path": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "File Path",
          "default": null,
          "description": "Local file path; only allowed when the server runs locally over stdio."
        },
        "file_base64": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "File Base64",
          "default": null,
          "description": "The PDF. File content encoded as Base64 (standard alphabet). Max 20 MiB decoded."
        }
      }
    }
    arguments 59 lines
  • supplier_compare unknown 32m ago

    Use when a user has two versions of a supplier or manufacturer price list and wants to know what changed. Compares old vs. new (CSV, XLSX, DATANORM 4/5 or text-based PDF; up to 20 MiB and 250,000 rows each): detects columns in many languages, normalises price, currency, pack size and price basis, computes the real unit price change per SKU, finds new and removed items and availability changes, detects across-the-board increases and ranks outliers for review. Optional demand file (SKU, annual quantity) adds cost impact. Returns `summary` plus the full result with source row for every finding.

    mcp-tool

    {
      "type": "object",
      "title": "supplier_compareArguments",
      "properties": {
        "options": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Options",
          "default": null,
          "description": "Optional CompareOptions, e.g. {\"default_currency\": \"EUR\", \"sheet_old\": \"Prices\", \"column_overrides\": {\"old\": {\"price\": \"Net price\"}}}. Schema: /v1/schemas/supplier-compare-options."
        },
        "new_filename": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "New Filename",
          "default": null,
          "description": "Original filename including extension (e.g. prices.xlsx); used to detect the format."
        },
        "old_filename": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Old Filename",
          "default": null,
          "description": "Original filename including extension (e.g. prices.xlsx); used to detect the format."
        },
        "new_file_path": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "New File Path",
          "default": null,
          "description": "Local file path; only allowed when the server runs locally over stdio."
        },
        "old_file_path": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Old File Path",
          "default": null,
          "description": "Local file path; only allowed when the server runs locally over stdio."
        },
        "usage_filename": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Usage Filename",
          "default": null,
          "description": "Original filename including extension (e.g. prices.xlsx); used to detect the format."
        },
        "new_file_base64": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "New File Base64",
          "default": null,
          "description": "New price list. File content encoded as Base64 (standard alphabet). Max 20 MiB decoded."
        },
        "old_file_base64": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Old File Base64",
          "default": null,
          "description": "Old price list. File content encoded as Base64 (standard alphabet). Max 20 MiB decoded."
        },
        "usage_file_path": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Usage File Path",
          "default": null,
          "description": "Local file path; only allowed when the server runs locally over stdio."
        },
        "usage_file_base64": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Usage File Base64",
          "default": null,
          "description": "Optional demand file (SKU, annual quantity). File content encoded as Base64 (standard alphabet). Max 20 MiB decoded."
        }
      }
    }
    arguments 137 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 270a932d4e9c8d49.

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

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.