mcpbeat

Findinfringement MCP Server

io.github.Bikram2112/findinfringement
answering

Findinfringement is answering right now. Last checked 9 min ago. It exposes 6 tools.

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

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
16.5%
Uptime 24h
15 of 91 checks
6
Tools
read from the server
907 ms
Response time
average over 24h
open, no key
Access
sse

Connect this server

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

run in your terminal
claude mcp add findinfringement --transport http https://claimhit.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "findinfringement": {
      "url": "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
{
  "mcpServers": {
    "findinfringement": {
      "url": "https://claimhit.com/api/mcp"
    }
  }
}

Available tools 6

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. Requires a search_id and target name. 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 full results from a previous ClaimHit search by search ID.
claimhit_rerun_search
Re-run a previous patent search to get fresh results. Free within 6 months of the original search. Use when the user wants to refresh results or check if new infringers have appeared.
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 820 ms 9 min ago

Findinfringement — questions

Answers built from our own checks of this server.

What can Findinfringement do?
It exposes 6 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_rerun_search, claimhit_search. 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 15 of 91 checks got a reply (16.5%), average response time 907 ms. The bar chart above shows every period we have measured.
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 with the file path 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 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Findinfringement?
It answers our handshake in 907 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.