Skip to main content
Glama
Patents & Trademarks MCP

Patents & Trademarks MCP

by blen-labs

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
USPTO_IP_RPSNoPer-IP token bucket rate on the HTTP transport.5
USPTO_API_KEYNoODP API key, sent as X-API-KEY. Unset means the odp source is disabled.
USPTO_SANDBOXNoSandbox runner to use: auto, isolate, or deno.auto
USPTO_IP_BURSTNoPer-IP token bucket burst on the HTTP transport.20
USPTO_USER_AGENTNoUser agent used to identify your deployment.uspto-mcp-server/0.1 …
USPTO_AUTH_ISSUERNoOIDC issuer. Required for OIDC providers.
USPTO_AUTH_SCOPESNoComma-separated scopes every token must carry; advertised in resource metadata.
USPTO_CACHE_TTL_MSNoResponse cache TTL in milliseconds.600000
USPTO_TSDR_API_KEYNoTSDR API key, sent as USPTO-API-KEY. Unset means the tsdr source is disabled.
USPTO_ALLOWED_HOSTSNoExtra accepted Host values, comma-separated. A value of * disables the check (unsafe).
USPTO_AUTH_AUDIENCENoOIDC audience. Required for OIDC providers.
USPTO_AUTH_JWKS_URLNoOIDC JWKS URL over https (http only on loopback). Required for OIDC providers.
USPTO_AUTH_PROVIDERNoAuthentication provider: none (only with --insecure), generic-oidc, clerk, workos, auth0, or accounts. Unknown values stop startup.none
USPTO_PUBLIC_ORIGINNoPublic origin clients reach, used for OAuth metadata and trusted Host. Required for non-loopback HTTP unless USPTO_ALLOWED_HOSTS is set.
USPTO_ALLOWED_ORIGINSNoAllowed browser Origin values, comma-separated, in addition to the server's own and loopback origins.
USPTO_CACHE_MAX_ITEMSNoMaximum number of items in the response cache.1000
USPTO_ODP_CONCURRENCYNoNumber of ODP requests in flight per key. Keep at 1.1
USPTO_CLIENT_IP_HEADERNoHeader your proxy overwrites with the client address (for Railway: x-real-ip).
USPTO_ODP_RATE_PER_SECNoNumber of ODP requests started per second per key.4
USPTO_TSDR_CONCURRENCYNoNumber of TSDR requests in flight per key. Keep at 1.1
USPTO_ODP_RATE_PER_HOURNoHourly ODP attempts per configured key (per account in account mode). Must be at least 1.5000
USPTO_TSDR_RATE_PER_SECNoNumber of TSDR requests started per second per key.1
USPTO_MAX_RESPONSE_BYTESNoLargest upstream response body accepted.8388608
USPTO_TSDR_RATE_PER_HOURNoHourly TSDR attempts per configured key (per account in account mode). Must be at least 1.3000
USPTO_SUBJECT_DAILY_QUOTANoRequests per authenticated subject per UTC day.10000
USPTO_MAX_CONCURRENT_EXECUTIONSNoMaximum simultaneous executions per server. Beyond this returns Busy.8
USPTO_ODP_MAX_CALLS_PER_EXECUTENoMaximum upstream ODP calls per execute() call. Exceeding it returns CallBudgetExceeded.50
USPTO_ODP_SUBJECT_RATE_PER_HOURNoPer-authenticated-subject ODP requests per hour. HTTP only.1000
USPTO_MAX_EXECUTIONS_PER_SUBJECTNoMaximum simultaneous executions per authenticated subject. Beyond this returns Busy.2
USPTO_TSDR_MAX_CALLS_PER_EXECUTENoMaximum upstream TSDR calls per execute() call. Exceeding it returns CallBudgetExceeded.25
USPTO_TSDR_SUBJECT_RATE_PER_HOURNoPer-authenticated-subject TSDR requests per hour. HTTP only.600

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

USPTO data through code mode. Workflow: search_api (find the SDK method and field names) -> describe_schema (exact signature) -> execute (run plain JavaScript against the odp and tsdr globals). odp = USPTO Open Data Portal: odp.patents.* (patent applications/file wrapper), odp.ptab.* (IPR/PGR trials, appeals, interferences), odp.petitions., odp.officeActions., odp.oa.* (legacy office action datasets), odp.bulk.* (bulk dataset catalog). tsdr = trademark status by serial or registration number. USPTO allows one request at a time per API key and has weekly quotas: use one well-filtered search with fields and a sensible limit rather than many lookups, and return only the values you need. Application numbers (e.g. 17/248,024) differ from patent numbers (e.g. 11,646,472): resolve a patent number with odp.patents.byPatentNumber first.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_apiA

BM25 search over the SDK methods and response-field dictionary for all bound sources (odp, tsdr): patent applications (file wrapper), PTAB trials/appeals/interferences, petition decisions, office actions, bulk datasets, and trademark status. Returns method signatures and JavaScript examples for use in execute. Start here.

describe_schemaA

Look up an endpoint or field by exact dotted id (path) or by namespace prefix. Use to drill into the bound source surfaces (odp., tsdr.).

executeA

Run JavaScript inside a sandbox (no net, fs, env, or subprocess). Plain JS only — TypeScript type annotations are rejected. Globals: odp, tsdr. Top-level await is allowed; return the value you want as the result. USPTO serves one request at a time per API key, so calls are queued: prefer one well-filtered search (with fields to trim large records) over many lookups, and return only what you need.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation4/5

The three tools map to distinct phases: discovery by fuzzy search (search_api), exact/prefix schema lookup (describe_schema), and execution (execute). The overlap between search_api and describe_schema is real — both expose the same API surface — but the descriptions give clear routing cues ('Start here' vs 'drill into ... by exact dotted id'), so misselection is unlikely.

Naming Consistency4/5

Two tools follow a verb_noun pattern (search_api, describe_schema) and the third is a bare verb (execute), which is a minor but defensible deviation since it is the terminal action. All names are lowercase snake_case and readable; there is no mixing of camelCase or arbitrary styles.

Tool Count4/5

Three tools is at the low end of the ideal range but fits a code-execution gateway, where an entire SDK is reached through `execute` rather than one tool per endpoint. Splitting discovery into search and describe is justified by the breadth of the odp/tsdr surface; nothing feels padded.

Completeness4/5

The lifecycle of discover -> inspect -> call is fully covered, and arbitrary JS execution means no API operation is a dead end. Minor gaps exist: no dry-run or validation step before `execute`, and no way to inspect rate-limit/queue state despite the documented one-request-per-key constraint.

Maintenance

ActivityMaintained
ResponsivenessOutdated data