_ registry / mcp http-sse · checked 5h ago

Pentonym

https://mcp.pentonym.com

Registry code: 2518ee7f88de2f8b

api record

Pentonym screens brand and product names against the US and EU trademark registers and returns a signed three-state verdict — PROCEED, DO_NOT_PROCEED or CANNOT_DETERMINE — with the evidence behind it. There is no score and no way to produce one.

Screening a name before offering it to a user avoids proposing one that is already registered. Always pass `goods`, the field of use: trademark conflict is decided by what the name is for, so without it no verdict is possible.

endpoint
https://mcp.pentonym.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Pentonym live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is Pentonym free to use?
Yes — the hub reached it with no key and no payment.
What tools does Pentonym have?
7 tools: get_screening_result, open_filing_matter, connect_account, suggest_names, screen_names, watch_name, classify_goods.
Is Pentonym safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
485ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 316 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • screen brand names against trademarks
  • suggest available brand names
  • classify goods into nice classes
  • watch a trademark for conflicts
takes → gives
text → data
tools
4 reads3 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_screening_result reads unknown 5h ago

    Fetch the full result for an id from screen_names. A verdict_id returns the complete signed dossier and re-checks its Ed25519 signature against the published key. A job_id returns a deep-clearance job: running, done with the verdict, or failed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "A verdict_id or a job_id."
        }
      }
    }
    arguments 12 lines
  • open_filing_matter changes data unknown never probed

    Open a US trademark filing matter for a name that returned PROCEED, using its verdict_id. Pentonym is a technology platform, not a law firm: an independent licensed attorney becomes counsel of record and bills the legal fee directly; USPTO fees pass through at cost. Requires a Pentonym account.

    mcp-tool

    {
      "type": "object",
      "required": [
        "verdict_id"
      ],
      "properties": {
        "goods": {
          "type": "string"
        },
        "classes": {
          "type": "array",
          "items": {
            "type": "integer"
          },
          "description": "Nice classes, e.g. [9,42]."
        },
        "verdict_id": {
          "type": "string"
        }
      }
    }
    arguments 21 lines
  • connect_account changes data unknown never probed

    Start connecting a Pentonym account for the current session, so account features work and the free allowance increases. Returns a link for the user to open; when they finish, this same session is authenticated with no key to copy anywhere. Applies when a call returned auth_required or the free allowance is spent.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "email": {
          "type": "string",
          "description": "The user's email, if they have given it. Optional — the link asks otherwise."
        }
      }
    }
    arguments 9 lines
  • suggest_names reads unknown 5h ago

    Generate candidate names for a brief and screen each one, returning a shortlist with a three-state verdict per name. Applies when a user needs new options rather than a check on names they already have. Claimability is a ceiling, not a promise: the best measured case is about 43%, against the US register and .com alone.

    mcp-tool

    {
      "type": "object",
      "required": [
        "brief"
      ],
      "properties": {
        "brief": {
          "type": "string",
          "description": "What the name is for."
        },
        "count": {
          "type": "integer",
          "description": "Default 3."
        }
      }
    }
    arguments 16 lines
  • screen_names reads unknown 17h ago

    Screen 1-5 brand or product names against the US and EU trademark registers. Returns a signed three-state verdict per name — PROCEED, DO_NOT_PROCEED or CANNOT_DETERMINE — with its evidence, never a score. US covers likelihood of confusion; EU covers live EUIPO exact wordmarks. Not worldwide, and not legal advice. `goods` is required: trademark conflict is decided by field of use.

    mcp-tool

    {
      "type": "object",
      "required": [
        "names",
        "goods"
      ],
      "properties": {
        "deep": {
          "type": "boolean",
          "description": "Also check domains, handles, web use; returns a job_id."
        },
        "goods": {
          "type": "string",
          "description": "Field of use, e.g. 'project-management software'."
        },
        "names": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 60
          },
          "maxItems": 5,
          "minItems": 1
        },
        "classes": {
          "type": "array",
          "items": {
            "type": "integer"
          },
          "description": "Nice classes, e.g. [9,42]."
        }
      }
    }
    arguments 33 lines
  • watch_name changes data unknown never probed

    Monitor a filed or registered name on the US register and report new confusingly-similar filings as typed changes. Pass registration_date to also get the section 8 and section 9 maintenance deadlines that keep a registration from lapsing. Requires a Pentonym account.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string"
        },
        "classes": {
          "type": "array",
          "items": {
            "type": "integer"
          },
          "description": "Nice classes, e.g. [9,42]."
        },
        "registration_date": {
          "type": "string",
          "description": "ISO date, if registered."
        }
      }
    }
    arguments 22 lines
  • classify_goods reads unknown 5h ago

    Map a plain-English product or service description to its Nice trademark class(es) and the verbatim USPTO ID Manual identification wording. The exact ID Manual wording holds the USPTO fee at the $350/class floor; free text costs $200/class more.

    mcp-tool

    {
      "type": "object",
      "required": [
        "description"
      ],
      "properties": {
        "description": {
          "type": "string",
          "description": "e.g. 'a productivity app'."
        },
        "jurisdiction": {
          "type": "string",
          "description": "Default US."
        }
      }
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2518ee7f88de2f8b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2518ee7f88de2f8b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2518ee7f88de2f8b/badge.svg)](https://brick.blue/agent/2518ee7f88de2f8b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.