RFQdecoder
REMOTE · RFQDECODER.COM · 2 COMPONENTS
Should-cost of a machined, sheet metal or cast part from its PDF, DXF or STEP drawing, line by line.
Available components
Last scanned (19 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 23 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 Security71
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1223 tokens (~174/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 Management44
- Stability check failed: schema churn in the 16 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 38 to 41.
- 20 Oct 26 −4
- Stability: 0.40 → fail ▼ security
- Authorization: fail → partial ▲ security
- Tool “verifier_devis” rewrote its description, which is the text the model reads security
- “verifier_devis” reworded the description of “devis” cosmetic
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 13 to 17. That category is still filling its 30-day observation window: 4 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.
- 11 Oct 26 0
- Tool “recharger_credits” rewrote its description, which is the text the model reads security
- “recharger_credits” reworded the description of “offre” cosmetic
- 10 Oct 26 0
- Tool “calculer_taux_horaire” rewrote its description, which is the text the model reads security
- Tool “chiffrer_piece” rewrote its description, which is the text the model reads security
- Tool “comparer_quantites” rewrote its description, which is the text the model reads security
- Tool “consulter_usage” rewrote its description, which is the text the model reads security
- Tool “deposer_plan” rewrote its description, which is the text the model reads security
- Tool “recharger_credits” rewrote its description, which is the text the model reads security
- Tool “verifier_devis” rewrote its description, which is the text the model reads security
- Schema quality: 125 → 166 ▼ functional
- Stability: unverified → 0.10 ▲ functional
- Tool “calculer_taux_horaire” changed its title: Machine hourly rate cosmetic
- Tool “chiffrer_piece” changed its title: Estimate part cost cosmetic
- Tool “comparer_quantites” changed its title: Compare quantities cosmetic
- Tool “consulter_usage” changed its title: Check remaining credits cosmetic
- Tool “deposer_plan” changed its title: Upload a part drawing cosmetic
- Tool “recharger_credits” changed its title: Top up credits cosmetic
- Tool “verifier_devis” changed its title: Check a supplier quote cosmetic
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 23 Oct 2026 · Probed https://rfqdecoder.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rfqdecoder.com | CN=YE2,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5aebc7f319771aa26fb065b8ff2adca975e |
| SANs: rfqdecoder.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 secure
Validation of rfqdecoder.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rfqdecoder.com. | present | 46025 | 8 | Verified |
| rfqdecoder.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rfqdecoder.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://rfqdecoder.com/api/mcp | Inconclusive | 405 |
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 →
calculer_taux_horaire Machine hourly rate ~117
Use this when the user asks for the hourly rate of a machine or workstation (CNC, laser, press, welding cell...). Computes it from the user's values (price, utilisation, labour, energy) for free, or reads a reference rate from the database (1 credit). Do not use for labour-only salary questions.
| Name | Type | Req | Description |
|---|---|---|---|
| machine | object | – | OU vos propres valeurs : le taux est alors calculé (formule du site) |
| poste | string | – | Poste de la base (une valeur par appel) |
No output schema declared.
No examples provided.
chiffrer_piece Estimate part cost ~216
Use this when the user asks what a manufactured part should cost (should-cost, target price, quote check) and a plan_id is available. Returns the unit price broken down line by line: material, each operation with machine and time, setups, overheads, margin, and what is not included. Requires material and quantity; ask the user if they are missing. Do not use for general price questions without a drawing. 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| ajustements | object | – | Paramètres du modèle (voir ajustements_possibles dans la réponse) |
| epaisseur_mm | number | – | Pour la tôle si le plan ne la porte pas |
| lot_de_fabrication | – | – | Nombre de pièces par lot, ou « commande_entiere » |
| matiere | string | yes | Ex. aluminium, acier, inox, fonte, pa6 |
| nb_campagnes | integer | – | – |
| plan_id | string | yes | Identifiant rendu par POST /plans |
| quantite | integer | yes | – |
No output schema declared.
No examples provided.
comparer_quantites Compare quantities ~209
Use this when the user wants to see how the unit price of the same part changes with quantity (2 to 8 quantities, e.g. 50, 500, 5000). Returns one costed line per quantity. Do not use for a single quantity (use chiffrer_piece). 1 credit per quantity.
| Name | Type | Req | Description |
|---|---|---|---|
| ajustements | object | – | Paramètres du modèle (voir ajustements_possibles dans la réponse) |
| detail | boolean | – | Renvoyer toutes les lignes pour chaque quantité |
| epaisseur_mm | number | – | Pour la tôle si le plan ne la porte pas |
| lot_de_fabrication | – | – | Nombre de pièces par lot, ou « commande_entiere » |
| matiere | string | yes | Ex. aluminium, acier, inox, fonte, pa6 |
| nb_campagnes | integer | – | – |
| plan_id | string | yes | Identifiant rendu par POST /plans |
| quantites | array | yes | – |
No output schema declared.
No examples provided.
consulter_usage Check remaining credits ~40
Use this when the user asks how many estimates or credits remain, or what limits apply. Returns remaining credits, quotas and recent calls. Free, read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deposer_plan Upload a part drawing ~109
Use this when the user provides a technical drawing of a manufactured part (PDF, DXF or STEP, max 20 MB) that will be costed. Uploads the file (base64) and returns a plan_id plus the dimensions and features read from it. Do not use for photos, invoices or documents that are not part drawings. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| contenu_base64 | string | yes | Contenu du fichier en base64 |
| nom_fichier | string | yes | Ex. piece.pdf |
No output schema declared.
No examples provided.
recharger_credits Top up credits ~163
Use this only when the user asks to buy or top up estimates, or after an estimate failed because credits ran out and the user wants to continue. Returns a secure card payment page (Stripe) to give to the user: pack25 (25 estimates, EUR 15 excl. VAT), pack100 (100, EUR 50), illimite (unlimited, EUR 200 per month). No payment happens inside the conversation; credits are added as soon as payment is confirmed. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| offre | string | yes | pack25 (25 chiffrages, 15 EUR HT), pack100 (100, 50 EUR HT) ou illimite (abonnement mensuel 200 EUR HT, usage raisonnable 3 000 par jour) |
No output schema declared.
No examples provided.
verifier_devis Check a supplier quote ~271
Use this when the user has a supplier quote for a part and wants to know if the price is fair. Compares the quoted price with the price rebuilt from the drawing, line by line, and lists the questions to ask the supplier. Requires a plan_id and the quoted unit price. 1 credit. The quote can be passed either as its unit price (devis.prix_unitaire_eur) or as the PDF file (devis.pdf_base64); with the PDF, the price, quantity and supplier are read automatically and returned in devis_lu.
| Name | Type | Req | Description |
|---|---|---|---|
| ajustements | object | – | Paramètres du modèle (voir ajustements_possibles dans la réponse) |
| devis | object | yes | Supplier quote: give prix_unitaire_eur, or pdf_base64, or both (prix_unitaire_eur then wins). |
| epaisseur_mm | number | – | Pour la tôle si le plan ne la porte pas |
| lot_de_fabrication | – | – | Nombre de pièces par lot, ou « commande_entiere » |
| matiere | string | yes | Ex. aluminium, acier, inox, fonte, pa6 |
| nb_campagnes | integer | – | – |
| plan_id | string | yes | Identifiant rendu par POST /plans |
| quantite | integer | yes | – |
No output schema declared.
No examples provided.
How do I install the RFQdecoder MCP server?
RFQdecoder is a hosted endpoint at https://rfqdecoder.com/api/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 · rfqdecoder.com
claude mcp add --transport http mounirt879-rfqdecoder 'https://rfqdecoder.com/api/mcp'
What is the RFQdecoder MCP server?
RFQdecoder is an MCP server listed in the public MCP registry as io.github.Mounirt879/rfqdecoder. Should-cost of a machined, sheet metal or cast part from its PDF, DXF or STEP drawing, line by line. This page covers its hosted endpoint (https://rfqdecoder.com/api/mcp).
Is the RFQdecoder MCP server safe to use?
RFQdecoder scores 72 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 RFQdecoder MCP server expose?
RFQdecoder exposes 7 tools: deposer_plan, chiffrer_piece, comparer_quantites, calculer_taux_horaire, verifier_devis, and 2 more. Their descriptions and schemas cost roughly 1,125 tokens of context every time the server is loaded.
Does the RFQdecoder MCP server require authentication?
No. We connected to RFQdecoder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RFQdecoder MCP server still maintained?
RFQdecoder is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.