Remite
REMOTE · BUROFAX.ONMAX.ME
Send a burofax or certified letter to a Spanish address, with proof of delivery and content.
Available components
Last scanned (5 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security63
- 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
- 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 Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1210 tokens (~242/item across 5 items; 4 tools + 1 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 Management43
- Stability observed for 13 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
- Supports UI / widget rendering.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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 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.
- 31 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.
- 29 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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 67
First indexed and scored.
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 5 Nov 2026 · Probed https://burofax.onmax.me/mcp/claude
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onmax.me | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b3de7356aad38531139eaf06cd7dd38d |
| SANs: onmax.me, burofax.onmax.me, *.burofax.onmax.me | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of burofax.onmax.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| onmax.me. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://burofax.onmax.me/mcp/claude | Verified | 200 | |
| http (plaintext) | http://burofax.onmax.me/mcp/claude | 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 →
check_spanish_address Check a Spanish postal address ~189
Use this when the user gives a recipient (or sender) postal address in Spain, before creating a burofax, to catch mistakes that would stop delivery. Checks offline: required fields (name, street, postcode, city), the 5-digit código postal in range 01000–52999, and that the province matches the postcode's first two digits. Returns normalised fields (with the official province) and a list of problems with messages for the user. It does not confirm that the street or person exists. Do not use for addresses outside Spain.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Town or city. |
| name | string | – | Recipient's full name or company name. |
| postal_code | string | – | Código postal, 5 digits. |
| province | string | – | Province, if the user gave one. |
| street | string | – | Street, number, floor and door. |
No output schema declared.
No examples provided.
create_burofax_draft Create a burofax draft for review ~424
Use this when the user has approved the final text of a letter to send as a burofax to an address in Spain and has given both postal addresses. The user writes or approves the text; this service does not give legal advice, so pass the body exactly as approved, without adding legal claims. Show the full text to the user and get approval before calling. Renders the exact A4 letter (sender, recipient, place and date, subject, body, signature line) as a PDF in Spanish, stores it as a draft and returns the page count, the price of each option and a review_url. Nothing is sent and nothing is charged by this tool: after calling it, show the review_url and tell the user that the letter goes out only after they pay on that page. Never ask for or include DNI/NIE/NIF or other ID numbers. Do not use to check prices (use quote_burofax) or to track a paid letter (use get_burofax_status).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The full letter body exactly as the user approved it, in Spanish (or bilingual). Separate paragraphs with a blank line. No address blocks, date or signature: those are added automatically. |
| city | string | – | City for the dateline "En <city>, a <date>". Defaults to the sender's city. |
| option | string | – | Delivery option: "correos" (Burofax de Correos) or "notificados" (certified notification by a trusted third party, not Correos). Use the user's choice; if they have none, use "correos". They can swit… |
| recipient | object | yes | Who receives it. Must be a postal address in Spain. |
| sender | object | yes | Who sends the letter. Printed top left and on the signature line. |
| subject | string | yes | Short subject line, in Spanish, printed as "Asunto: …", e.g. "Reclamación de la fianza del contrato de alquiler". |
No output schema declared.
No examples provided.
get_burofax_status Get burofax status ~146
Use this when the user asks whether their burofax was paid, sent or delivered, or wants the certificate. Takes the reference the user has: the order reference (BFX-XXXX-XXXX-XXXX-XXXX, from the receipt email) or the draft reference / review link returned by create_burofax_draft. Returns the current status and a dated timeline (draft created, paid, accepted by the operator, delivered, certificate available) and a link to the status page. Read-only. Do not use to create or change a letter.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Order reference (BFX-…) or draft reference, or the full review/status link. |
No output schema declared.
No examples provided.
quote_burofax Quote a burofax ~250
Use this when the user asks how much it costs to send a burofax or a certified letter to an address in Spain, or wants to compare delivery options before writing it. Returns the all-in price in EUR of both options for the given length, and what each includes: (1) Burofax de Correos with acuse de recibo and copia certificada; (2) a certified notification by Notificados, a trusted third party (tercero de confianza) that is NOT a Correos burofax. Always pass that distinction on to the user. Give pages if known, otherwise text_length (characters of the letter body) for an estimate; with neither, quotes one page. Does not send or reserve anything. Do not use it to create the letter; use create_burofax_draft once the text and addresses are approved.
| Name | Type | Req | Description |
|---|---|---|---|
| option | string | – | Option the user asked about, if any. Both options are always returned. |
| pages | integer | – | Number of A4 pages, 1–10, if already known. |
| text_length | integer | – | Length of the letter body in characters, to estimate pages when the page count is unknown. |
No output schema declared.
No examples provided.
How do I install the Remite MCP server?
Remite is a hosted endpoint at https://burofax.onmax.me/mcp/claude, 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 · burofax.onmax.me
claude mcp add --transport http me-onmax-remite 'https://burofax.onmax.me/mcp/claude'
What is the Remite MCP server?
Remite is an MCP server listed in the public MCP registry as me.onmax/remite. Send a burofax or certified letter to a Spanish address, with proof of delivery and content. This page covers its hosted endpoint (https://burofax.onmax.me/mcp/claude).
Is the Remite MCP server safe to use?
Remite scores 73 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 Remite MCP server expose?
Remite exposes 4 tools: quote_burofax, check_spanish_address, create_burofax_draft, get_burofax_status. Their descriptions and schemas cost roughly 1,009 tokens of context every time the server is loaded.
Does the Remite MCP server require authentication?
No. We connected to Remite without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Remite MCP server still maintained?
Remite is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.