Verdacert

com.verdacertPublished by verdacert.comOfficial publisherv1.0.0Updated Oct 31, 2026

Certified translations for USCIS, courts and universities: quote, order, track and verify them.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for certified translations for USCIS, courts and universities: get quotes, place and track orders, and verify translations.

What you can do
  • Quote, order, track and verify certified translations for USCIS, courts and universities.
  • No tool list is published, so the exact actions available to an assistant are not documented here.
When to use it
When someone needs certified document translations for immigration filings, court proceedings or university applications and wants an assistant to handle quoting, ordering, tracking or verification.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's site. A bearer token is required in the Authorization header; sandbox keys are offered free through the provider's onboarding, and live keys use a separate prefix.
Before you install
The Authorization header carries a secret API key, so keep it out of shared logs and chats. Ordering translations is a paid service, and sandbox keys are separate from live ones. Documents submitted for translation may contain personal or legal information sent to a third party.

Installation

In SourceWeft

  1. Open Verdacert in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.verdacert%2Fverdacert/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "verdacert": {
      "type": "http",
      "url": "https://www.verdacert.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 31, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.