ClaimHit
io.github.Bikram2112/claimhitVersion 1.0.1Find products & standards using a patent - verified targets for licensing or enforcement.
Status
Responds1132 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:36 UTC
- Latency
- 1132 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://www.claimhit.com/api/mcpResponds1132 msNo sign-in
Claude Code
claude mcp add --transport http claimhit https://www.claimhit.com/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: claimhit
Remote MCP server URL: https://www.claimhit.com/api/mcpCursor
{
"mcpServers": {
"claimhit": {
"url": "https://www.claimhit.com/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"claimhit","type":"http","url":"https://www.claimhit.com/api/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
claimhit_generate_chartGenerate 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. | No | No | No | Yes |
claimhit_get_creditsCheck how many search credits and chart credits the user has remaining. | No | Yes | Yes | No |
claimhit_get_historyGet the user's recent patent scans. Returns patent numbers, dates, and top results from past searches. | No | Yes | Yes | No |
claimhit_get_resultGet 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. | No | Yes | Yes | No |
claimhit_refine_productLook 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. | No | Yes | No | Yes |
claimhit_rerun_searchRe-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. | No | No | No | Yes |
claimhit_searchSearch 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. | No | No | No | Yes |
Details
- Registry status
- Active
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Categories (suggested)
- Search and webSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared