ClaimHit
REMOTE · WWW.CLAIMHIT.COM
Find products & standards using a patent - verified targets for licensing or enforcement.
Available components
Last scanned (8 hours ago)
Scores higher than 9% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://www.claimhit.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.claimhit.com | CN=YR2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 6036595f2ac3f2f1cd4369e2b7b3ac4fde1 |
| SANs: www.claimhit.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.claimhit.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| claimhit.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 308 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.claimhit.com/api/mcp | Redirected | 308 | https://app.claimhit.com/api/mcp |
| http (plaintext) | http://www.claimhit.com/api/mcp | HTTPS enforced | 308 | https://www.claimhit.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
claimhit_generate_chart Generate claim chart ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | The search ID from a previous claimhit_search |
| target_name | string | yes | The exact name of the product or standard to chart e.g. "Samsung Galaxy S25" or "5G NR Release 17" |
No output schema declared.
No examples provided.
claimhit_get_credits Check ClaimHit credits ~24
Check how many search credits and chart credits the user has remaining.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
claimhit_get_history Recent patent scans ~51
Get the user's recent patent scans. Returns patent numbers, dates, and top results from past searches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of recent searches to return (default 5, max 20) |
No output schema declared.
No examples provided.
claimhit_get_result Get full search results ~44
Get full results from a previous ClaimHit search by search ID.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | The search ID returned from claimhit_search or claimhit_get_history |
No output schema declared.
No examples provided.
claimhit_rerun_search Re-run patent search ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | The search ID of the previous search to re-run |
No output schema declared.
No examples provided.
claimhit_search Search patent for infringers ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | What to search: products (default), standards (SEP/FRAND analysis), or both |
| patent_number | string | yes | Patent number with kind code. Example: US10123456B2 or EP3456789B1 or WO2020123456A1 |
| target_standard | string | – | Optional: specific standard to focus on e.g. "5G NR", "Wi-Fi 6", "HEVC" |
| user_context | string | – | Optional: additional hints to guide the search. E.g. "focus on automotive camera systems", "look for semiconductor companies", "prioritise claim 3 which covers the image stabilization feature". Passe… |
No output schema declared.
No examples provided.
How do I install the ClaimHit MCP server?
ClaimHit is a hosted endpoint at https://www.claimhit.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.claimhit.com
claude mcp add --transport http bikram2112-claimhit 'https://www.claimhit.com/api/mcp'
What is the ClaimHit MCP server?
ClaimHit is an MCP server listed in the public MCP registry as io.github.Bikram2112/claimhit. Find products & standards using a patent - verified targets for licensing or enforcement. This page covers its hosted endpoint (https://www.claimhit.com/api/mcp).
Is the ClaimHit MCP server safe to use?
ClaimHit scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ClaimHit MCP server expose?
ClaimHit exposes 6 tools: claimhit_search, claimhit_get_credits, claimhit_get_history, claimhit_get_result, claimhit_generate_chart, claimhit_rerun_search. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.
Does the ClaimHit MCP server require authentication?
Its publisher declares no required credentials for ClaimHit. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ClaimHit MCP server still maintained?
ClaimHit is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.