mcpbeat Sign in

Findinfringement MCP Server

not responding

Findinfringement is listed as active in the registry but did not answer our last check. It exposes 7 tools.

Find patent infringers with 9 AI models. Search products & standards from your AI client.

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 92 checks
7
Tools
read from the server
65 ms
Response time
average over 24h
open, no key
Access
sse

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 October 2026. No other catalogue keeps this.

7 Nov a tool changed the parameters it asks for claimhit_get_result
22 Oct a tool changed the parameters it asks for claimhit_get_result
18 Oct 3 tool descriptions were rewritten claimhit_generate_chart, claimhit_get_result, claimhit_rerun_search
18 Oct 3 tools changed the parameters they ask for claimhit_generate_chart, claimhit_get_result, claimhit_rerun_search
18 Oct a tool appeared claimhit_refine_product
13 Oct a tool description was rewritten claimhit_get_result

Findinfringement does not always answer

Over the last week it answered 3.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add findinfringement --transport sse https://claimhit.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://claimhit.com/api/mcp
~/.codex/config.toml
[mcp_servers.findinfringement]
url = "https://claimhit.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "findinfringement": {
      "url": "https://claimhit.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "findinfringement": {
      "type": "sse",
      "url": "https://claimhit.com/api/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

claimhit
claimhit_generate_chart
Generate an AI Hit Chart for a specific target (product or standard) from a previous search. A Hit Chart maps patent claim elements to product features element-by-element with evidence. SPENDS 1 CHART CREDIT and asks first: the initial call returns a quote naming the target it matched and runs nothing, and the chart is generated only when you call again with confirm: true after the user agrees. Use this when the user asks to chart, map claims, or analyse a specific target in detail.
claimhit_get_credits
Check how many search credits and chart credits the user has remaining.
claimhit_get_history
Get the user's recent patent scans. Returns patent numbers, dates, and top results from past searches.
claimhit_get_result
Get results from a previous ClaimHit search by search ID, and narrow, sort and page through them. FREE and unlimited: every call is a view over results already paid for, so filter and re-read as much as the conversation needs. A search completes in phases: check the returned `status` field and call again if it is RUNNING, because background enrichment keeps finding additional implementers for several minutes after the first results appear. Only present results as final when status is COMPLETE. Results are paged — if the response carries a `more` field, there are further matches and you must not present the page you have as the complete list.
claimhit_refine_product
Look again at one target from a search. Given a vague or wrong target and what the user wants instead — a specific model ("the S25 Ultra"), a version ("the latest one"), or a capability or market ("one with hardware AV1 encode", "a Chinese vendor doing the same thing") — returns up to 5 real, current products with a reason for each, grounded in a live web search. FREE: no credit is taken. Use it before charting, to chart the right thing. It refines one row; to screen a whole market for a patent, use claimhit_search.
claimhit_rerun_search
Re-run a previous patent search to get fresh results, repeating the inputs that steered it — the company scope, the hint, named products, markets, company sizes and the named standard. Free within 6 months of the original search, 1 search credit after that. Asks first either way: the initial call returns a quote listing the inputs it will repeat and whether it is free, and runs nothing until you call again with confirm: true. To narrow or re-read the results you already have, use claimhit_get_result instead — that is free and does not start a new search.
claimhit_search
Search for products or technical standards that potentially infringe a given patent. Runs multiple AI models in parallel and returns ranked results with Hit Scores. Use this when asked to find infringers, check infringement, or screen a patent.

Endpoints

URLTransportStateLatencyChecked
https://claimhit.com/api/mcp sse answering 65 ms 8 min ago

Alternatives to Findinfringement

same job, measured the same way
ProjectSend
by projectsend

Share files with your clients from your AI assistant. Free and paid ProjectSend Cloud accounts.

answering
Cloudlabels
by cloudlabels

Turn your product list into print-ready label PDFs with barcodes, from your AI assistant.

answering
Dualtran MCP
by seigwen

Translate text with Google or your own AI model (BYOK, 20+ providers) from any MCP client.

70 installs/wk local only
Readdit Later
by sanjhaiprakash18

Search, organize, and chat with your saved Reddit posts from Claude, Cursor, and any MCP client.

66 installs/wk answering
Orinami
by orinami

Mind maps with a full document in every node. Read, search and edit your maps from AI tools.

answering
Jumpseller
by jumpseller

Manage your Jumpseller store with AI. Products, orders, customers, and more.

answering
Conceptio Search
by 0x923041-dotcom

Search 1M+ open-access papers, standards, and case law from an AI agent.

377 installs/wk local only
Nimbus
by nimbus-agent

Search your local Nimbus index and run its built-in agents from any MCP client.

55 installs/wk local only

Findinfringement — questions

Answers built from our own checks of this server.

What can Findinfringement do?
It exposes 7 tools, read directly from the server on our last check. Among them: claimhit_generate_chart, claimhit_get_credits, claimhit_get_history, claimhit_get_result, claimhit_refine_product, claimhit_rerun_search and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Findinfringement working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 65 ms. The bar chart above shows every period we have measured.
The registry lists Findinfringement as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Findinfringement?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Findinfringement need an API key?
No. Findinfringement completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.