ClaimHit
REMOTE · WWW.CLAIMHIT.COM · SCANNED AUG 3
Find products & standards using a patent - verified targets for licensing or enforcement.
Available components
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 →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 515 tokens (~85/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.claimhit.com
claude mcp add --transport http bikram2112-claimhit https://www.claimhit.com/api/mcp
[mcp_servers.bikram2112-claimhit] url = "https://www.claimhit.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bikram2112-claimhit": {
"type": "remote",
"url": "https://www.claimhit.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add bikram2112-claimhit --url https://www.claimhit.com/api/mcp --transport streamable-http
mcp_servers:
bikram2112-claimhit:
url: "https://www.claimhit.com/api/mcp" {
"mcpServers": {
"bikram2112-claimhit": {
"type": "http",
"url": "https://www.claimhit.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +5
- 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 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 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
- 26 Jul 26 71
First indexed and scored.
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 3 Aug 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=YR1,O=Let's Encrypt,C=US | 27 Jul 2026 | 25 Oct 2026 | RSA 2048 | SHA256-RSA | 61ce72b6cc66b736eb2bb3aed461062bf14 |
| SANs: www.claimhit.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 |
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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://www.claimhit.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://www.claimhit.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://www.claimhit.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.claimhit.com/api/mcp |
| Authorisation server | https://www.claimhit.com |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.claimhit.com/api/mcp | Verified | 200 | |
| 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.
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.