Skip to content

ClaimHit MCP server

io.github.Bikram2112/claimhitBikram2112streamable-httpv1.0.1Scanned

Find products & standards using a patent - verified targets for licensing or enforcement.

7 tools: 4 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 4 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ClaimHit MCP server can do

The ClaimHit MCP server is published by the GitHub account Bikram2112. It has 7 tools. It can create or change data (4 tools: claimhit_search, claimhit_generate_chart, claimhit_rerun_search and claimhit_refine_product), but cannot delete data. 3 tools only read.

4 tools bring in text other people can write (claimhit_search, claimhit_generate_chart, claimhit_rerun_search and 1 more).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 4Claude Code: ask
  • claimhit_generate_chartGenerate an AI Hit Chart for a specific target (product or standard) from a previous search.Reads text others writeNo findings

    Why it is in this group

    • The name "claimhit_generate_chart" says "generate": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Generate claim chart
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • claimhit_refine_productLook again at one target from a search.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look again at one target
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • claimhit_get_creditsCheck how many search credits and chart credits the user has remaining.No findings

    Why it is in this group

    • The name "claimhit_get_credits" says "get": a word for reading.
    Description, as the server wrote it
    Check how many search credits and chart credits the user has remaining.

    Annotations the server declares

    • title: Check ClaimHit credits
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • claimhit_get_historyGet the user's recent patent scans.No findings

    Why it is in this group

    • The name "claimhit_get_history" says "get": a word for reading.
    Description, as the server wrote it
    Get the user's recent patent scans. Returns patent numbers, dates, and top results from past searches.

    Annotations the server declares

    • title: Recent patent scans
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • claimhit_get_resultGet results from a previous ClaimHit search by search ID, and narrow, sort and page through them.No findings

    Why it is in this group

    • The name "claimhit_get_result" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get full search results
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:56 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.claimhit.com/api/mcp: tools/list returned 7 tools to an anonymous client, including claimhit_search (write), claimhit_generate_chart (write), claimhit_rerun_search (write), claimhit_refine_product (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "claimhit_search" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "claimhit_search" says "search": a word for reading.

    What this check looks for
  • The server marks "claimhit_rerun_search" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "claimhit_rerun_search" says "search": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http claimhit https://www.claimhit.com/api/mcp
claude mcp add --transport http claimhit https://www.claimhit.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__claimhit__claimhit_get_credits",
      "mcp__claimhit__claimhit_get_history",
      "mcp__claimhit__claimhit_get_result"
    ],
    "ask": [
      "mcp__claimhit__claimhit_search",
      "mcp__claimhit__claimhit_generate_chart",
      "mcp__claimhit__claimhit_rerun_search",
      "mcp__claimhit__claimhit_refine_product"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as claimhit. Review it before you use it.

Capability tags behind 4 rules
  • mcp__claimhit__claimhit_search untrusted-input
  • mcp__claimhit__claimhit_generate_chart untrusted-input
  • mcp__claimhit__claimhit_rerun_search untrusted-input
  • mcp__claimhit__claimhit_refine_product untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Bikram2112/claimhit/verify?hash=55da92f22ddf30c9d49da06228e7db67068573b09c295c9650a3251c7582cb7e" | jq -e '.changed == false'

Pinned hash 55da92f22ddf, from Nov 15, 2026, 18:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Bikram2112/claimhit/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Bikram2112/claimhit
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Bikram2112/claimhit.svg)](https://radar.anlyon.com/servers/io.github.Bikram2112/claimhit)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:14 UTC.

ClaimHit MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ClaimHit MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ClaimHit MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ClaimHit MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ClaimHit MCP server have?

7 tools: 4 write, 3 read. claimhit_search, claimhit_generate_chart, claimhit_rerun_search, claimhit_refine_product, claimhit_get_credits, claimhit_get_history and claimhit_get_result.

Does the ClaimHit MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ClaimHit MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ClaimHit MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.