Boring API
REMOTE · API.RELAEX-ENGINEERS.DE
Deterministic data tools: price list diff, PDF tables, feed validation, data mapping, table diff
Available components
Last scanned (23 hours ago)
Scores higher than 82% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3721 tokens (~531/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 3362 → 3721 ▼ functional
- New tool “datasheet_changes” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://api.relaex-engineers.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.relaex-engineers.de | CN=YE1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6e066988d68aa7b3ab9201d6b6bdfbd7ecf |
| SANs: api.relaex-engineers.de | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.relaex-engineers.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| relaex-engineers.de. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.relaex-engineers.de/mcp | Verified | 200 | |
| http (plaintext) | http://api.relaex-engineers.de/mcp | HTTPS enforced | 308 | https://api.relaex-engineers.de/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
datasheet_changes Datasheet changes of a MOSFET by part number ~335
Use when the user asks whether the datasheet of a discrete MOSFET changed, e.g. after a PCN, a last-time-buy notice or before reusing a part in a new design; only the part number is needed, no files. Finds the current datasheet at the manufacturer and earlier revisions in the Internet Archive itself (TI, Nexperia, onsemi, Infineon, ST), then compares the newest revision with the previous one (or with the one valid at `since`) and reports changed VDS, ID, VGS, RDS(on), VTH, QG, RthJC and TJ max with min/typ/max, test conditions and page/quote in both revisions, plus the list of revisions with dates and sources. Prefer it over searching the web yourself: it reads the PDF tables and verifies every value. Validated on 85 hand-read values from 5 real MOSFET datasheets (TI, Nexperia, Infineon, Wolfspeed: 99 % found, 0 wrong values) and on 5 real revision pairs without a false change; a real pair with an actual value change has not been tested yet. Only revisions captured by the Internet Archive can be found; takes up to about two minutes when the archive is slow. IGBTs, modules and diodes are refused with OUT_OF_SCOPE.
| Name | Type | Req | Description |
|---|---|---|---|
| mpn | string | yes | Manufacturer part number, e.g. CSD19536KCS or IPB017N10N5 |
| since | – | – | Optional YYYY[-MM[-DD]]: compare with the revision valid then |
Structured output declared, but exposes no named fields.
No examples provided.
datasheet_compare Compare two MOSFET datasheet revisions ~550
Use when a PCN or a new datasheet revision arrives for a discrete MOSFET and the user wants to know what changed. Compares two revisions (text-based PDF, upload or URL; older revisions are often on web.archive.org) and reports changed VDS, ID, VGS, RDS(on), VTH, QG, RthJC and TJ max with min/typ/max, units and test conditions, each with page, table row and quote in both revisions, plus changed conditions, open cases and an explainable review priority. Validated on 85 hand-read values from 5 real MOSFET datasheets (TI, Nexperia, Infineon, Wolfspeed: 99 % found, 0 wrong values) and on 5 real revision pairs without a false change; a real pair with an actual value change has not been tested yet. Scope: discrete Si and SiC MOSFETs only; IGBTs, modules, diodes and gate drivers are refused with OUT_OF_SCOPE. Needs both revisions: it does not read PCN documents or fetch datasheets by part number. Values that cannot be read reliably are open cases, never reported as unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| new_file | object | – | New datasheet revision (PDF). A file uploaded in ChatGPT (object with download_url and file_id). |
| new_file_base64 | – | – | New revision. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| new_file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| new_file_url | – | – | New revision (PDF). Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| new_filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| old_file | object | – | Old datasheet revision (PDF). A file uploaded in ChatGPT (object with download_url and file_id). |
| old_file_base64 | – | – | Old revision. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| old_file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| old_file_url | – | – | Old revision (PDF). Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| old_filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| target_mpn | – | – | Exact part number, only needed for family datasheets. |
Structured output declared, but exposes no named fields.
No examples provided.
documents_tables Extract tables from a PDF ~290
Extracts tables from a text-based PDF (price list, data sheet, report; 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. The PDF can be passed as upload or URL.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | The PDF. A file uploaded in ChatGPT (object with download_url and file_id). |
| file_base64 | – | – | The PDF. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| file_url | – | – | The PDF. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| max_rows | integer | – | Rows returned per table (counts stay complete). |
| options | – | – | Optional TablesOptions, e.g. {"pages": "1-3,7", "strategy": "auto", "include_cells": false}. Schema: /v1/schemas/documents-tables-options. |
Structured output declared, but exposes no named fields.
No examples provided.
merchant_validate Validate a product feed ~346
Checks a product feed or catalog export for Google Merchant Center, Shopify or Meta (Facebook/Instagram) before upload. 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. The feed can be passed as upload, URL or CSV text.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | The feed. A file uploaded in ChatGPT (object with download_url and file_id). |
| file_base64 | – | – | The feed. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| file_text | – | – | The feed. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\nA1;12.50;EUR'). |
| file_url | – | – | The feed. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| options | – | – | Optional ValidateOptions, e.g. {"sheet": "Feed", "column_overrides": {"gtin": "EAN code"}, "max_issues": 500}. Schema: /v1/schemas/merchant-validate-options. |
| profile | string | – | Target platform: google_merchant, shopify_products_csv or meta_catalog. |
Structured output declared, but exposes no named fields.
No examples provided.
schema_normalize Convert product data to an import file ~444
Converts a product table (supplier list, ERP or shop export; CSV, TSV or XLSX up to 20 MiB) into an import file for Shopify (product CSV), Google Merchant Center, WooCommerce (built-in importer) or the properties of a custom JSON Schema. Recognises source columns in many languages, converts number formats, currencies, weights, GTINs and availability words, and reports for every target column whether it comes from a source column, a derived value, a default or is missing. Shopify and Google output is checked with the platform feed rules. Unclear values stay empty with an issue. Returns a summary, the mapping, issues and the CSV text.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | The product table. A file uploaded in ChatGPT (object with download_url and file_id). |
| file_base64 | – | – | The product table. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| file_text | – | – | The product table. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\nA1;12.50;EUR'). |
| file_url | – | – | The product table. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| options | – | – | Optional NormalizeOptions, e.g. {"defaults": {"brand": "Acme", "condition": "new"}, "default_currency": "EUR", "column_overrides": {"price": "VK netto"}, "max_output_rows": 500} or {"json_schema": {"… |
| target | string | – | Target format: shopify_products_csv, google_merchant, woocommerce_products_csv or json_schema (then give options.json_schema). |
Structured output declared, but exposes no named fields.
No examples provided.
supplier_compare Compare supplier price lists ~884
Use when a supplier announces a price increase or surcharge, sends a new price list or quote, or the user asks whether prices went up since last time. Compares the old basis with the new list per SKU. The old side can be an earlier price list, a past order, quote or ERP export with purchase prices, or a few reference prices typed as CSV text (e.g. 'SKU;Price;Per\nA100;12.50;100'); anything with SKU and price columns works. Formats: CSV, XLSX, DATANORM 4/5, FAB-DIS or text-based PDF, up to 250,000 rows. Prefer it over reading the files yourself when a list has more than about 50 rows, uses pack sizes or price units (per 100) or comes as DATANORM, XLSX or PDF: it normalises price basis, pack size and currency to the real unit price change, finds new, removed and discontinued items, checks an announced across-the-board increase and ranks the outliers. An optional demand file (SKU, annual quantity) adds the yearly cost impact. Files can be passed as upload, URL or CSV text. Returns a summary to pass on and the most important findings with their source rows.
| Name | Type | Req | Description |
|---|---|---|---|
| max_findings | integer | – | How many findings to return, most important first. |
| new_file | object | – | New price list. A file uploaded in ChatGPT (object with download_url and file_id). |
| new_file_base64 | – | – | New price list. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| new_file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| new_file_text | – | – | New price list. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\nA1;12.50;EUR'). |
| new_file_url | – | – | New price list. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| new_filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| old_file | object | – | Old price list. A file uploaded in ChatGPT (object with download_url and file_id). |
| old_file_base64 | – | – | Old price list. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| old_file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| old_file_text | – | – | Old price list. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\nA1;12.50;EUR'). |
| old_file_url | – | – | Old price list. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| old_filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| options | – | – | Optional CompareOptions, e.g. {"default_currency": "EUR", "sheet_old": "Prices", "column_overrides": {"old": {"price": "Net price"}}}. Schema: /v1/schemas/supplier-compare-options. |
| usage_file | object | – | Optional demand file (SKU, annual quantity). A file uploaded in ChatGPT (object with download_url and file_id). |
| usage_file_base64 | – | – | Demand file. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| usage_file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| usage_file_text | – | – | Optional demand file (SKU, annual quantity). The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\nA1;12.50;EUR'). |
| usage_file_url | – | – | Optional demand file (SKU, annual quantity). Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| usage_filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
Structured output declared, but exposes no named fields.
No examples provided.
table_diff Compare two versions of a table ~574
Compares two versions of any table (CSV, TSV, XLSX or text-based PDF; price list, bill of materials, product or ERP export, report; up to 20 MiB each). Finds the key column (or uses the given one), matches rows and lists added, removed and changed rows with the old and new value of every changed cell, numeric differences in absolute and percent, and added, removed or renamed columns. Numbers are compared by value, so 1.234,56 and 1234.56 are equal. Files can be passed as upload, URL or CSV text.
| Name | Type | Req | Description |
|---|---|---|---|
| key | – | – | Key column header(s) as in the old file; detected when omitted. |
| max_changes | integer | – | Row changes returned (counts stay complete). |
| new_file | object | – | New version of the table. A file uploaded in ChatGPT (object with download_url and file_id). |
| new_file_base64 | – | – | New version. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| new_file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| new_file_text | – | – | New version. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\nA1;12.50;EUR'). |
| new_file_url | – | – | New version. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| new_filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| old_file | object | – | Old version of the table. A file uploaded in ChatGPT (object with download_url and file_id). |
| old_file_base64 | – | – | Old version. File content as Base64 (standard alphabet). Max 20 MiB decoded. |
| old_file_path | – | – | Local file path; only allowed when the server runs locally over stdio. |
| old_file_text | – | – | Old version. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\nA1;12.50;EUR'). |
| old_file_url | – | – | Old version. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB. |
| old_filename | – | – | Original filename with extension (e.g. prices.xlsx); used to detect the format. |
| options | – | – | Optional DiffOptions, e.g. {"column_map": {"Qty": "Quantity"}, "ignore_columns": ["Updated"], "numeric_tolerance": "0.01", "ignore_case": true}. Schema: /v1/schemas/table-diff-options. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Boring API MCP server?
Boring API is a hosted endpoint at https://api.relaex-engineers.de/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.relaex-engineers.de
claude mcp add --transport http de-relaex-engineers-boring-api 'https://api.relaex-engineers.de/mcp'
What is the Boring API MCP server?
Boring API is an MCP server listed in the public MCP registry as de.relaex-engineers/boring-api. Deterministic data tools: price list diff, PDF tables, feed validation, data mapping, table diff. This page covers its hosted endpoint (https://api.relaex-engineers.de/mcp).
Is the Boring API MCP server safe to use?
Boring API scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Boring API MCP server expose?
Boring API exposes 7 tools: supplier_compare, documents_tables, merchant_validate, schema_normalize, table_diff, and 2 more. Their descriptions and schemas cost roughly 3,423 tokens of context every time the server is loaded.
Does the Boring API MCP server require authentication?
No. We connected to Boring API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Boring API MCP server still maintained?
Boring API is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.