Remoto interpreting (ProZ.com)
REMOTE · WWW.PROZ.COM
Find interpreters, quote per-minute prices and get start links on Remoto by ProZ.
Available components
Last scanned (8 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Security69
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability82
- 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 1964 tokens (~115/item across 17 items; 9 tools + 8 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
- 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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.
- 4 Nov 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.
- 2 Nov 26 +1
- Server version: 1.1.2 → 1.1.3 functional
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 70
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://www.proz.com/remoto/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=proz.com | CN=YE1,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 63975ffc46ae6e727a1b0315a5be1024393 |
| SANs: *.proz.com, proz.com, www.dev-ben.syr.proz.com | ||||||
| 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 www.proz.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| proz.com. | 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=15552000; includeSubDomains; preload |
| content-security-policy | img-src 'self' data: blob: https://*.proz.com https://proz.com https://*.stripe.com https://*.stripe.network https://*.cloudinary.com https://*.amazonaws.com https://*.cloudfront.net https://i.vimeocdn.com https://*.vimeocdn.com https://bzr.openai.com; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.proz.com/remoto/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.proz.com/remoto/api/mcp | Served over HTTP | 200 |
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_language_pair Check a language pair ~125
Whether Remoto covers a language pair and whether someone can connect now (available_now) or booking ahead is recommended (book_ahead). Never returns interpreter counts. For uncovered pairs it explains the hand-match and English-relay options.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | Source language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| target | string | yes | Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | object | – | – |
| availability | string | yes | available_now = interpreters online now; book_ahead = booking ahead recommended. Never a count. |
| links | object | yes | – |
| message | string | yes | – |
| source | object | yes | – |
| supported | boolean | yes | – |
| target | object | yes | – |
No examples provided.
find_interpreters Find interpreters ~294
Searches Remoto's public interpreter directory by language pair, specialty (medical, legal…), country, mode, online now and HIPAA agreement on file. Returns a short list of public profile fields: name, languages with per-minute price, specialties, rating, online now, profile link. Headlines are interpreter-written text (marked userWritten).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166 two-letter country where the interpreter is based, e.g. US, MX. |
| hipaa_only | boolean | – | Only interpreters with a HIPAA agreement on file. |
| interpreting_mode | string | – | – |
| limit | integer | – | Results per page (default 5, max 10). |
| online_only | boolean | – | Only interpreters online right now (for an immediate call). |
| page | integer | – | – |
| sort | string | – | – |
| source | string | – | Source language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| specialty | string | – | Subject area, e.g. medical, legal, mental health, immigration, education, business. |
| target | string | – | Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| verified_only | boolean | – | Only interpreters with identity/compliance checks on file. |
| Name | Type | Req | Description |
|---|---|---|---|
| directoryUrl | string | yes | – |
| hasMore | boolean | yes | – |
| interpreters | array | yes | – |
| page | number | yes | – |
No examples provided.
get_interpreter Get an interpreter's profile ~78
One interpreter's public profile: languages with per-minute prices, specialties, interpreting modes, rating, online now, experience and profile link. The headline and bio are interpreter-written text (marked userWritten).
| Name | Type | Req | Description |
|---|---|---|---|
| interpreter_id | string | yes | Interpreter id: the number in the public profile URL (/profile/<id>), or the profile URL itself. |
| Name | Type | Req | Description |
|---|---|---|---|
| avatarUrl | string|null | yes | – |
| callTypes | array | yes | – |
| country | string|null | yes | – |
| countryCode | string|null | yes | – |
| experienceYears | number|null | yes | – |
| id | string | yes | – |
| interpretingModes | array | yes | – |
| languagePairs | array | yes | – |
| name | string | yes | – |
| onlineNow | boolean | yes | – |
| proBonoAvailable | boolean | yes | – |
| profileUrl | string | yes | – |
| rating | – | yes | – |
| specialties | array | yes | – |
| userWritten | object | yes | Text the interpreter wrote for their public profile; not written or checked by Remoto. |
| verification | – | yes | – |
No examples provided.
get_open_slots Get bookable times ~201
Bookable times for one interpreter, using Remoto's booking calendar rules. Most interpreters take scheduled-call requests instead of fixed slots (bookingRoute = scheduled_request): the person proposes a date, time and length and the interpreter confirms.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day, YYYY-MM-DD (default today). |
| interpreter_id | string | yes | Interpreter id: the number in the public profile URL (/profile/<id>), or the profile URL itself. |
| source | string | – | Language pair being booked (prices the slot). |
| target | string | – | Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| timezone | string | – | IANA timezone for the returned times, e.g. America/New_York (default UTC). |
| to | string | – | Last day, YYYY-MM-DD (default from + 13 days, max 31 days). |
| Name | Type | Req | Description |
|---|---|---|---|
| bookingRoute | string | yes | – |
| bookingUrl | string | yes | – |
| from | string | yes | – |
| interpreterId | string | yes | – |
| message | string | yes | – |
| price | – | – | – |
| slotDurationMinutes | number | – | – |
| slots | array | yes | – |
| timezone | string | yes | – |
| to | string | yes | – |
| truncated | boolean | – | – |
No examples provided.
get_price_quote Get a price quote ~212
Client price for a language pair: per-minute USD with all platform fees included, billed per second after a one-minute minimum; scheduled calls are a fixed total (minutes × per-minute price). With interpreter_id the result is that interpreter's exact price; without it, the pair's typical price and range.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_minutes | integer | – | Scheduled: booked length (default 60). On demand: expected length for an estimate (default 10). |
| interpreter_id | string | – | Interpreter whose exact price is quoted. When absent, the quote is the pair's typical price and range. |
| mode | string | – | on_demand (default) or scheduled. |
| source | string | yes | Source language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| target | string | yes | Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| Name | Type | Req | Description |
|---|---|---|---|
| basis | string | yes | – |
| billing | object | yes | – |
| currency | string | yes | – |
| estimate | object | – | – |
| interpreterId | string | – | – |
| mode | string | yes | – |
| notes | array | yes | – |
| rangePerMinute | object | – | – |
| ratePerMinute | number | – | Exact client price per minute for the chosen interpreter, all platform fees included. |
| scheduledTotal | object | – | – |
| source | object | yes | – |
| startLink | object | yes | – |
| target | object | yes | – |
| typicalRatePerMinute | number | – | – |
No examples provided.
get_start_link Get a link to start or book ~252
A link the person opens to start an on-demand call or book a scheduled one, prefilled with the language pair and/or interpreter. Payment is entered on Remoto's page (card, Apple Pay, Google Pay, PayPal; guests need no account). This tool creates nothing and charges nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_minutes | integer | – | Scheduled only: booked length in minutes. |
| interpreter_id | string | – | Interpreter id: the number in the public profile URL (/profile/<id>), or the profile URL itself. |
| mode | string | yes | on_demand = connect now; scheduled = book a time. |
| source | string | – | Source language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| starts_at | string | – | Scheduled only: the chosen start time (ISO 8601 with offset, e.g. a bookable time's startsAt). With interpreter_id, source and target the link is a price-locked booking link. |
| target | string | – | Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase"). |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| expiresAt | string | – | – |
| lockedPrice | object | – | – |
| mode | string | yes | – |
| priceLocked | boolean | yes | – |
| url | string | yes | – |
No examples provided.
list_services List Remoto services ~70
Remoto's interpreting services — on-demand video/audio, Phone Line (dial-in OPI), scheduled calls, sign language, simultaneous interpreting (RSI) for events, business/agency portal, partner API, pro bono — with who each is for, how it works, how it's billed and a link.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| services | array | yes | – |
No examples provided.
resolve_language Resolve a language name ~125
Remoto's language code for a language name, including sign languages. Accepts informal names, aliases, dialects, countries/demonyms and codes ("Farsi", "Tagalog", "Brazilian Portuguese", "Afghan", "ASL", "es") and returns the best matches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most matches to return (default 5). |
| query | string | yes | Language name, alias, dialect, country/demonym or code, e.g. "Farsi", "Tagalog", "Afghan", "ASL", "es". |
| Name | Type | Req | Description |
|---|---|---|---|
| hint | string | – | – |
| matches | array | yes | – |
| query | string | yes | – |
No examples provided.
search_help Search Remoto help ~80
Search Remoto's support articles, FAQ and security/privacy/HIPAA facts (BAA on request, encryption, recordings, payments, GDPR). Returns snippets with source links.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Question or keywords, e.g. "HIPAA BAA", "how is billing calculated", "phone line PIN". |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the Remoto interpreting (ProZ.com) MCP server?
Remoto interpreting (ProZ.com) is a hosted endpoint at https://www.proz.com/remoto/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 · www.proz.com
claude mcp add --transport http com-proz-remoto 'https://www.proz.com/remoto/api/mcp'
What is the Remoto interpreting (ProZ.com) MCP server?
Remoto interpreting (ProZ.com) is an MCP server listed in the public MCP registry as com.proz/remoto. Find interpreters, quote per-minute prices and get start links on Remoto by ProZ. This page covers its hosted endpoint (https://www.proz.com/remoto/api/mcp).
Is the Remoto interpreting (ProZ.com) MCP server safe to use?
Remoto interpreting (ProZ.com) 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 Remoto interpreting (ProZ.com) MCP server expose?
Remoto interpreting (ProZ.com) exposes 9 tools: list_services, resolve_language, check_language_pair, get_price_quote, find_interpreters, and 4 more. Their descriptions and schemas cost roughly 1,437 tokens of context every time the server is loaded.
Does the Remoto interpreting (ProZ.com) MCP server require authentication?
No. We connected to Remoto interpreting (ProZ.com) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Remoto interpreting (ProZ.com) MCP server still maintained?
Remoto interpreting (ProZ.com) 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 Remoto interpreting (ProZ.com) MCP server?
VerifyMCP ran 14 checks on Remoto interpreting (ProZ.com), covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.