Moha: hire in the UAE
REMOTE · EMPLOYEROFRECORD.AE
Hire in the UAE without a local company: guide, quotes and accounts via an Employer of Record.
Available components
Last scanned (18 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 929 tokens (~185/item across 5 items; 5 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 Management37
- Stability observed for 11 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 5 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 supported MCP spec version (2025-11-25); the latest is 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.
- 21 Nov 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.
- 19 Nov 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.
- 17 Nov 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.
- 14 Nov 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.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 74
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 21 Nov 2026 · Probed https://employerofrecord.ae/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=employerofrecord.ae | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | e2bed6978e2480e80ecf4d39a4f9c756 |
| SANs: employerofrecord.ae | ||||||
| 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 employerofrecord.ae. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ae. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; frame-src https://challenges.cloudflare.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://employerofrecord.ae/mcp | Verified | 200 | |
| http (plaintext) | http://employerofrecord.ae/mcp | HTTPS enforced | 301 | https://employerofrecord.ae/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 →
check_prepared_hire Check a prepared hire or account ~46
Whether the person opened the link from prepare_hire or prepare_account and created their account yet.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_id | string | yes | The draft_id that prepare_hire returned. |
No output schema declared.
No examples provided.
get_quote Price a hire in the UAE ~191
Monthly and upfront cost of employing one person in the UAE through Moha, an Employer of Record: salary split, employer costs, government fees, insurance, our fee and VAT, plus how long the visa takes. No account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| children | integer | – | Children moving with them on family visas. |
| emirate | string | – | Where they will work. Defaults to Dubai. |
| inside_uae | boolean | – | True if the person is already in the UAE. Defaults to false (coming from abroad). |
| insurance | string | – | Health insurance plan. Defaults to standard. |
| monthly_salary_aed | number | yes | Total monthly package in AED: basic salary plus allowances. Example: 20000. |
| nationality | string | yes | The employee’s nationality, as a country name. Example: India. |
| spouse | boolean | – | True if a spouse will move with them on a family visa. |
No output schema declared.
No examples provided.
how_to_hire_in_the_uae How to hire in the UAE without a local company ~70
How hiring in the UAE works through Moha, an Employer of Record, for a company with no UAE entity: when it fits, the information needed about the hire and the company, the employee's documents, the steps, the timeline and the prices. No account needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prepare_account Prepare a whole account for the person to confirm ~119
Prepares a Moha account without signing in: company profile, the person setting it up, one to ten hires and colleagues to invite. Returns the quotes and one link to confirm. Moha checks the company first; hires go ahead and colleagues are invited only once approved.
| Name | Type | Req | Description |
|---|---|---|---|
| company | object | yes | The hiring company. |
| hires | array | yes | The people to hire. |
| team | array | – | Colleagues to invite when the account is created, each with a role. |
| you | object | – | The person setting up the account. |
No output schema declared.
No examples provided.
prepare_hire Prepare a hire for the person to confirm ~371
Prepares one hire in the UAE without an account. Returns the quote and a link: the person opens it, checks the details and creates their Moha account. Moha checks the company before the hire goes ahead. Nothing is charged or sent to the employee before that.
| Name | Type | Req | Description |
|---|---|---|---|
| children | integer | – | Children moving with them on family visas. |
| company_name | string | – | The hiring company’s name, to prefill the account. |
| emirate | string | – | Where they will work. Defaults to Dubai. |
| employee_email | string | – | The employee’s personal email, if known. |
| first_name | string | yes | The employee’s first name. |
| inside_uae | boolean | – | True if the person is already in the UAE. Defaults to false (coming from abroad). |
| insurance | string | – | Health insurance plan. Defaults to standard. |
| job_title | string | yes | Their job title. It goes on the work permit, so use the real one. |
| last_name | string | yes | The employee’s last name. |
| monthly_salary_aed | number | yes | Total monthly package in AED: basic salary plus allowances. Example: 20000. |
| nationality | string | yes | The employee’s nationality, as a country name. Example: India. |
| spouse | boolean | – | True if a spouse will move with them on a family visa. |
| start_date | string | – | Wanted start date, YYYY-MM-DD. At least two weeks from today; earlier dates are moved to the earliest possible. |
| your_email | string | – | Their work email, on their company’s domain, to prefill the account. Personal, forwarding and throwaway addresses are refused. |
| your_name | string | – | The name of the person you are helping, to prefill the account. |
No output schema declared.
No examples provided.
How do I install the Moha: hire in the UAE MCP server?
Moha: hire in the UAE is a hosted endpoint at https://employerofrecord.ae/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 · employerofrecord.ae
claude mcp add --transport http ae-employerofrecord-moha 'https://employerofrecord.ae/mcp'
What is the Moha: hire in the UAE MCP server?
Moha: hire in the UAE is an MCP server listed in the public MCP registry as ae.employerofrecord/moha. Hire in the UAE without a local company: guide, quotes and accounts via an Employer of Record. This page covers its hosted endpoint (https://employerofrecord.ae/mcp).
Is the Moha: hire in the UAE MCP server safe to use?
Moha: hire in the UAE 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 Moha: hire in the UAE MCP server expose?
Moha: hire in the UAE exposes 5 tools: how_to_hire_in_the_uae, get_quote, prepare_hire, prepare_account, check_prepared_hire. Their descriptions and schemas cost roughly 797 tokens of context every time the server is loaded.
Does the Moha: hire in the UAE MCP server require authentication?
No. We connected to Moha: hire in the UAE without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Moha: hire in the UAE MCP server still maintained?
Moha: hire in the UAE is still listed as active in the MCP registry. We last reached this channel on 21 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 Moha: hire in the UAE MCP server?
VerifyMCP ran 13 checks on Moha: hire in the UAE, 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.