Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Karandeepsingh Blog 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.
What it does
Search and read Karandeep Singh's DevOps and AWS blog: articles and cheatsheets.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http karandeepsingh-blog-mcp https://karandeepsingh.ca/mcp
# 2 — ask your agent for something these tools do
# search_posts, read_post, list_recent and 8 more
Karandeepsingh Blog costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. 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 karandeepsingh-blog-mcp https://karandeepsingh.ca/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search Karandeep Singh's blog (DevOps/AWS articles and cheatsheets). Returns ranked cards with title, URL, tags, date, reading time, and summary.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms, e.g. 'aurora failover' or 'lambda cold start'. |
| limit | number | no | Max results (default 8, cap 20). |
| section | string | no | Optional: restrict to 'posts' or 'cheatsheets'. |
Read a post's full text by URL, paginated. Returns a window of characters; call again with the returned next offset to continue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Post URL or path, e.g. /posts/aurora-postgresql-setup-guide/. |
| offset | number | no | Character offset to start from (default 0). |
List the most recently published posts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Default 8, cap 20. |
List posts with a given tag (e.g. aws, lambda, cost, aurora). Use list_topics to see all tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag | string | yes | A tag name. |
| limit | number | no | — |
List every tag on the blog with a post count, for discovering what's covered.
No parameter schema on file.
Given a post URL, find other posts that share the most tags with it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Post URL or path. |
| limit | number | no | — |
Return a random post from the blog — a surprise pick.
No parameter schema on file.
Jump straight to a cheatsheet by topic (docker, cloudformation, cost, aurora, kubernetes, …) and get its full text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Cheatsheet topic or name. |
List all cheatsheets (quick-reference guides) on the blog.
No parameter schema on file.
Test the user's knowledge with real multiple-choice questions written for the blog's articles. Returns questions, options, and an answers section with explanations. Ask the questions first, then reveal the answers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Topic to be quizzed on, e.g. aurora, lambda, docker. Omit for a random quiz. |
| count | number | no | How many questions (default 3, max 10). |
Return just the runnable commands and code blocks from the best-matching article or cheatsheet — no prose. Use when the user wants the command, not the explanation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic or tool, e.g. docker, kubectl, terraform, psql. |
| limit | number | no | Max code blocks to return (default 6, max 12). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — 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 Karandeepsingh Blog or to call it, at any volume.
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 an address its publisher runs, and you connect to it directly — this marketplace is not in the path. 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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 3.1.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Karandeepsingh Blog can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.