eVerbary MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVERBARY_API_KEY | No | An eVerbary API key: ev_live_... for your account, ev_test_... for the sandbox (pretend orders, nothing charged). Optional: without it, the first run opens your browser to sign in to eVerbary. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_languagesA | The languages eVerbary translates, with the codes the other tools take, the per-page price beside English and beside another language (surcharge flag), and which ones Expedited Plus (same day) covers. |
| list_document_typesA | Common document types eVerbary translates (birth and marriage certificates, diplomas, transcripts, court records...) with what to upload for each, plus the general requirements: accepted file types and sizes, what a page is, notarization, turnarounds. |
| get_quoteA | Price and delivery time for a certified translation, for this account (its team discount and included rush applied), with the other turnarounds for comparison and whether the key's spending limits allow it. Nothing is ordered. |
| upload_documentA | Send one source document (PDF, image, Word...) before ordering. Returns an upload_id for get_quote and create_order, and the pages counted in it. Files are kept 24 hours until used in an order; sending the same file again returns the same upload_id. |
| create_orderA | Place a certified translation order for this account with the uploaded files. Call first with confirm=false and show the preview (price, delivery, files) to the user; then call again with confirm=true and a request_id. The order is placed unpaid and enters the translation queue; pay it with pay_order or share the payment link. Refused when over the key's spending limits. |
| pay_orderA | Pay an order with the account's own means: its team's prepaid balance, its saved card (off-session; card numbers are never accepted), or - for teams with billing terms - its periodic invoice. Call with confirm=false first, show the user the amount and method, then confirm=true with the confirmation_id. If the card needs the cardholder's approval (3-D Secure) nothing is charged and a payment link is returned. Limited per order and per day for this key. |
| order_statusA | Status of one of this account's orders: progress, expected delivery, payment (paid / unpaid / on account, invoice) and, once delivered, links to the certified translation files. |
| list_my_ordersA | This account's most recent orders with status, price and payment state. |
| get_payment_linkA | The web link where anyone can pay an unpaid order by card or PayPal - to send to whoever pays (e.g. the firm's client), or when a card needs the cardholder's approval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| order_certified_translation | Walk through uploading, quoting, ordering and paying a certified translation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct step or resource in the translation workflow: reference listing (languages, document types), quoting, uploading, ordering, paying, and status checking. The closest pairs (order_status vs list_my_orders, pay_order vs get_payment_link) are clearly differentiated by their descriptions as single-order detail vs recent list, and account-means payment vs a shareable link.
Most tools follow a consistent verb_noun pattern (list_languages, get_quote, upload_document, create_order, pay_order, get_payment_link, list_my_orders). The exception is order_status, which drops the verb and breaks the pattern, though it remains understandable.
Nine tools is well-scoped for a translation ordering service, covering reference data, the quote/upload/order/pay/status lifecycle, and payment links. No tool feels redundant or out of place.
The core order lifecycle is well covered: reference info, quoting, document upload, order creation, payment (account or link), and status/listing with delivered file links. Possible minor gaps include canceling or modifying an order and retrieving file downloads via a dedicated tool, but agents can work around these.