desenmascara.me
REMOTE · DESENMASCARA.ME
Is this website a scam? Dated, sourced fraud assessments of domains. Free, read-only, no key.
Available components
Last scanned (15 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 498 tokens (~249/item across 2 items; 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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://desenmascara.me/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=desenmascara.me | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 79f78ce9e69ca23f0e6c2ad187b069ad |
| SANs: desenmascara.me, *.desenmascara.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 desenmascara.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| me. | DS published | 45352 | 8 | Verified |
| desenmascara.me. | No DS | 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://desenmascara.me/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://desenmascara.me/mcp/v1 | HTTPS enforced | 301 | https://desenmascara.me/mcp/v1 |
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_before_payment Check a merchant before paying ~259
For an AI agent about to pay, or to submit card or account details, on a website: returns one action — 'do_not_pay', 'stop_and_ask_user' or 'no_fraud_found' — with the reason and the report link. 'do_not_pay' means the domain is published as fraudulent with evidence, or hides instructions aimed at AI agents. Anything not settled, including a domain never assessed, is 'stop_and_ask_user': hand the decision back to the person, never proceed on your own. 'no_fraud_found' is not a guarantee. Call it with the merchant's domain, not a payment page URL. desenmascara.me assesses whether a website domain is fraudulent, using evidence gathered at a point in time. It can and does decline to judge when the evidence is insufficient. It assesses domains, not URLs, and its assessment does not establish that a particular payment or action is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | – | Optional: the amount about to be paid. |
| category | – | – | Optional: what is being bought, such as footwear. |
| currency | – | – | Optional: ISO 4217 currency code, such as EUR. |
| domain | string | yes | The merchant's hostname, such as shop.example.com. |
No output schema declared.
No examples provided.
get_domain_report Get a domain's fraud assessment ~180
Return desenmascara.me's existing assessment of a domain: the verdict, when it was reached, the recorded findings and a link to the published report. Reads stored data only — it starts no new analysis. A domain with no report returns status 'not_found', which says nothing about the site. desenmascara.me assesses whether a website domain is fraudulent, using evidence gathered at a point in time. It can and does decline to judge when the evidence is insufficient. It assesses domains, not URLs, and its assessment does not establish that a particular payment or action is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A hostname such as example.com or shop.example.com. Not a URL: paths and query strings are not assessed. Subdomains are significant and are not collapsed to the parent domain. |
| language | string | – | Language for the explanation and findings. |
No output schema declared.
No examples provided.
How do I install the desenmascara.me MCP server?
desenmascara.me is a hosted endpoint at https://desenmascara.me/mcp/v1, 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 · desenmascara.me
claude mcp add --transport http me-desenmascara-desenmascara 'https://desenmascara.me/mcp/v1'
What is the desenmascara.me MCP server?
desenmascara.me is an MCP server listed in the public MCP registry as me.desenmascara/desenmascara. Is this website a scam? Dated, sourced fraud assessments of domains. Free, read-only, no key. This page covers its hosted endpoint (https://desenmascara.me/mcp/v1).
Is the desenmascara.me MCP server safe to use?
desenmascara.me scores 84 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 desenmascara.me MCP server expose?
desenmascara.me exposes 2 tools: get_domain_report, check_before_payment. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.
Does the desenmascara.me MCP server require authentication?
No. We connected to desenmascara.me without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the desenmascara.me MCP server still maintained?
desenmascara.me 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.
What did VerifyMCP test on the desenmascara.me MCP server?
VerifyMCP ran 13 checks on desenmascara.me, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.