Model Context Protocol server for Rollbar
Nothing to run from here
HitKeep is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
—
trust score
—
calls last 7d
remote
at its publisher
—
p95 latency
What it does
Stateless 2026-07-28 read-only MCP server for aggregate HitKeep analytics and official docs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hitkeep-mcp 'https://{hitkeep_host}/mcp'
The address is a placeholder from the publisher’s own docs: put the address of your own deployment in its place before you run this.
HitKeep costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PAAll 1 server
PascaleBeier1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. The address on this listing is a placeholder from its publisher’s own docs, not a live endpoint: you run HitKeep yourself and put the address of your own deployment in its place — this marketplace is not in the path.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. The address is a placeholder from the publisher’s own docs: put the address of your own deployment in its place before you run this. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http hitkeep-mcp 'https://{hitkeep_host}/mcp'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at your own deployment of it: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it writes
One config entry pointing at the address of your own deployment — this marketplace is not in the path, and the server runs wherever you deploy it.
What you approve
This listing has not published its tool surface here yet, so what a client will ask you to approve is whatever the manifest declares at install time.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No tool surface on file
This listing has not published its tool list here yet. Nothing is shown here rather than another listing’s tools, which is what this page used to do.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs at your own deployment of it — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install HitKeep or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is a server you deploy yourself: its address is a placeholder for your own deployment. The scanner reads packages and public source, and an address is neither, so there is no grade — not a withheld one, an unmeasured one.
Release history
It answers at your own deployment of it, running whatever release you deployed there — so a release cannot be chosen from here. The history below is for reading; the current release on file is 2.14.1.
2.14.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish HitKeep can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.