PlateQuery MCP — US License Plate & Vehicle Information

com.platequeryPublished by platequery.comOfficial publisherv1.0.0Updated Oct 24, 2026

License plate lookup for AI agents: plate messages and ALPR history via PlateQuery. OAuth 2.1.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant look up US license plates and vehicle information, including plate messages and ALPR history, via PlateQuery.

What you can do
  • Look up US license plates and the vehicle information tied to them.
  • Retrieve plate messages and ALPR (automated license plate reader) history through PlateQuery.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to resolve a US license plate to vehicle details or review ALPR history as part of an investigation, verification or research workflow.
Requirements
A remote streamable HTTP endpoint at api.platequery.com; no local package or runtime is needed. OAuth (OAuth 2.1 per the description) authentication is required, so an account with the provider is needed. No environment variables or headers are declared.
Before you install
Access is gated by OAuth, so you sign in with a PlateQuery account and grant the assistant access. License plate and ALPR data is personal and location-related; consider privacy, legal basis and retention before querying. Usage may be metered or billed by the provider, though the input does not state pricing.

Installation

In SourceWeft

  1. Open PlateQuery MCP — US License Plate & Vehicle Information in the dashboard and add it to a workspace.
  2. Connect the required 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.platequery%2Fplate-api/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "platequery-us-license-plate-vehicle-info": {
      "type": "http",
      "url": "https://api.platequery.com/mcp"
    }
  }
}

README

PlateQuery MCP — US License Plate & Vehicle Information

License plate lookup for AI agents, built on PlateQuery — the license plate lookup site people use to notify vehicle owners, report bad driving, or flag illegal parking. This Model Context Protocol server lets an agent read those same messages for any U.S. license plate, plus public ALPR (automated license plate reader) sighting history from the Flock Safety camera network, by state or region.

This repository holds public documentation for the server. The implementation lives in PlateQuery's main application repository, which is closed-source.

Tools

ToolCostDescription
check_creditsFreeCheck your account's remaining credit balance. Doesn't count against the rate limit.
lookup_plate1 creditQuick summary for one plate: privacy status, the latest 3 messages (plus a total count), and a count of ALPR mentions, if any are public.
list_plate_messages1 creditFull, paginated list of messages posted about a plate.
list_plate_alpr_mentions1 creditFull, paginated ALPR search history for a plate, including the searching agency and source.
post_plate_messageFreePost a new message about a plate -- e.g. "reported for speeding" -- optionally with vehicle make/model/year/color and an approximate location. Requires the write scope. See Posting messages below.

A plate marked private by its owner returns zeroed messages/mentions to everyone except that owner. Free plan grants a starting credit balance on signup; additional credits are purchased in bulk packages — see api-settings for current pricing. Paid tools are rate-limited per account; call check_credits as often as you like to check balance without spending a credit.

Posting messages

post_plate_message is free but deliberately conservative, since it's the only tool that writes anything:

  • Requires a PlateQuery account with a confirmed email.
  • Rate-limited: 2 posts/minute, 10 posts/day, 3 posts/day about the same plate.
  • Not published immediately. Every post goes into the same moderation queue a website submission does -- it's invisible (and the plate's followers aren't notified) until a human moderator approves it.
  • vehicle_make/vehicle_model/vehicle_year/vehicle_color and location are all optional free text -- location should be an approximate description (e.g. "Hwy 37 near Los Altos, CA" or a cross-street), never precise GPS coordinates.

Authentication

The server is OAuth 2.1 only — no manual API keys. It supports PKCE and dynamic client registration (DCR), so a compliant MCP client (Claude, or any client following the MCP authorization spec) can connect by:

  1. Pointing at https://api.platequery.com/mcp.
  2. Following the WWW-Authenticate challenge to discover https://platequery.com as the authorization server (RFC 9728 protected resource metadata).
  3. Registering itself dynamically (RFC 7591) and running the standard Authorization Code + PKCE flow.
  4. Signing in with (or creating) a PlateQuery account when prompted.

No client secret or pre-issued API key is needed — sign-in happens in the browser the first time an agent connects.

Two scopes exist: read (the default -- covers every tool except post_plate_message) and write (required for post_plate_message, opt-in only). A client must explicitly request write at connect time to be able to post; an existing read-only connection can't post without reconnecting.

Adding it to an MCP client

Most MCP clients (including Claude) let you add a remote server by URL. Add https://api.platequery.com/mcp as a Streamable HTTP connector and follow the sign-in prompt on first use.

Support

Questions or issues: https://platequery.com/contact/

Source: README.md at commit 16d6af4

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.