Skip to content
Motomarks logo

Motomarks MCP server

Which servers in the official MCP registry are Motomarks's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-16

← Back to Motomarks

Whose server it is
  • Registry nameio.motomarks/mcpverified in the MCP registry

The registry name sits under motomarks.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-16
  • Stateanswerschecked 2026-10-16
  • Tools8
  • Server calls itselfmotomarks
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-16 the server answered initialize and tools/list without a sign-in. First answer in 101 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-19
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer293 ms
  • Space in an agent's context≈ 1,309 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 8 of 8

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers8 tools · read 2026-10-16
  • sign_up

    Create a free Motomarks account or start sign-in for an existing email. Sends a six-digit verification code. No password or credit card. After the user reads the code, call complete_sign_up.

  • complete_sign_up

    Verify the six-digit email code from sign_up. Creates the account when the email is new, then returns API keys so the client can reconnect as that user.

  • search_brands

    Search published Motomarks brands by name, company, or slug. Optionally filter by vehicle type and include ready-to-use CDN image URLs.

  • get_brand

    Get full details for a published Motomarks brand by slug: description, colors, palette, social links, company facts, FAQs, and optionally its assets.

  • list_brand_assets

    List available Motomarks logo assets for a brand and optionally include generated CDN image URLs.

  • build_image_url

    Build a deterministic Motomarks image CDN URL authenticated with the caller's publishable key.

  • describe_api_endpoint

    Return the HTTP endpoint, auth mode, params, and example for a Motomarks REST operation.

  • get_account

    Get the authenticated caller's Motomarks account: plan, attribution status, today's API usage against the daily limit, and active API keys (secret keys masked).

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "motomarks": {
      "type": "http",
      "url": "https://motomarks.io/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http motomarks https://motomarks.io/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://motomarks.io/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.