_ registry / mcp streamable-http · checked 42m ago

patent-gap

https://patentgap.dropwatchhq.com

Registry code: 54081361d8201048

api record

Off-patent opportunity feed: expiring design patents, recall + supplier screened, for sellers.

from a public catalogue that lists it, not from the operator

endpoint
https://patentgap.dropwatchhq.com/mcp
protocol
streamable-http ·2024-11-05
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 patent-gap live?
Yes — it answered the hub's last check (checked 42m ago). It answered 100% of checks over the last 30 days.
Is patent-gap free to use?
Yes — the hub reached it with no key and no payment.
What tools does patent-gap have?
4 tools: category_opportunity_report, newly_expirable, screen_patent, list_categories.
Is patent-gap 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
125ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 514 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find expiring design patents
  • screen a us patent for expiry and recalls
  • get off-patent product opportunity report
  • list tracked product categories
takes → gives
text → data
tools
4 reads
_ 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

_ what it can do 4 tools
1 open 3 never probed 1 of 4 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.

  • list_categories reads open 11h ago

    List the private-label product categories Patent-Gap tracks for expiring design patents.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • category_opportunity_report reads unknown never probed

    PAID (x402, $0.03 USDC on Base). Full off-patent opportunity report for a category slug (see list_categories): every newly-expirable design patent with computed expiry, CPSC recall-safety band, and OFAC/OIG supplier screen, ranked by actionability. Free callers get a preview + x402 challenge.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Max candidates (default 25, max 60)."
        },
        "category": {
          "type": "string",
          "description": "Category slug, e.g. 'kitchen-gadgets' (from list_categories)."
        }
      }
    }
    arguments 16 lines
  • newly_expirable reads unknown never probed

    Cross-category feed of design patents that just became (or are about to become) free to make — i.e. fresh off-patent private-label opportunities, soonest-expiry first, already recall- and supplier-screened.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "description": "Max items (default 30)."
        }
      }
    }
    arguments 9 lines
  • screen_patent reads unknown never probed

    Screen ONE US patent by publication number (e.g. USD689332S1): compute its statutory expiry/status, join CPSC recall-safety for its category, and run an OFAC/OIG screen on the assignee. Returns the freedom-to-operate read (design-patent scope; not legal advice).

    mcp-tool

    {
      "type": "object",
      "required": [
        "publication_number"
      ],
      "properties": {
        "category": {
          "type": "string",
          "description": "Optional category label to sharpen the recall match."
        },
        "publication_number": {
          "type": "string",
          "description": "US patent publication number, e.g. USD689332S1 or US8935905B2."
        }
      }
    }
    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 54081361d8201048.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/54081361d8201048/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/54081361d8201048/badge.svg)](https://brick.blue/agent/54081361d8201048?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
80%

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.

_ also on dropwatchhq.com 35 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

27 more sit on this domain. All of them.