RMCP.DEV
← Registry

Learning Resources

karandeepsingh.ca

Provides tools to search, read, and browse Karandeep Singh's DevOps/AWS blog posts and cheatsheets by tag or recency.

1 endpoint11 known toolsFirst detected September 11, 2026Last detected September 11, 2026

ENDPOINT 1

https://karandeepsingh.ca/mcp

No auth detected

MCP server metadata

Name
karandeepsingh-blog
Version
3.1.0
Capabilities
toolsresourcespromptscompletions
Server instructions

Karandeep Singh's DevOps/AWS blog — articles and cheatsheets, exposed as MCP tools, resources and prompts. Tools: start with search_posts or list_topics, then read_post for full text. Use get_cheatsheet for quick reference (docker, cloudformation, cost, aurora, …), list_cheatsheets for every reference, and related_posts / browse_by_tag to explore around a topic. quiz_me runs a real multiple-choice quiz from questions written for the articles (ask the questions before revealing answers); get_commands returns only the runnable commands from a page, with no prose. Resources: every article is also a resource addressed by its canonical URL, so one can be attached directly. Prompts: research_topic, quick_reference, compare_options and whats_new wrap the common workflows. Everything is public, read-only, and safe to call without confirmation. IMPORTANT when presenting results to the user: keep every markdown link exactly as returned, in the form [Title](https://karandeepsingh.ca/...), so titles stay clickable. Never strip a link, never replace it with a bare title, and never rewrite the URL.

Known tools 11

search_posts

Search Karandeep Singh's blog (DevOps/AWS articles and cheatsheets).

Inferred read-only
read_post

Read a post's full text by URL, paginated.

Potential side effects
list_recent

List the most recently published posts.

Inferred read-only
browse_by_tag

List posts with a given tag (e.

Inferred read-only
list_topics

List every tag on the blog with a post count, for discovering what's covered.

Potential side effects
related_posts

Given a post URL, find other posts that share the most tags with it.

Potential side effects
random_post

Return a random post from the blog — a surprise pick.

Potential side effects
get_cheatsheet

Jump straight to a cheatsheet by topic (docker, cloudformation, cost, aurora, kubernetes, …) and get its full text.

Inferred read-only
list_cheatsheets

List all cheatsheets (quick-reference guides) on the blog.

Inferred read-only
quiz_me

Test the user's knowledge with real multiple-choice questions written for the blog's articles.

Inferred read-only
get_commands

Return just the runnable commands and code blocks from the best-matching article or cheatsheet — no prose.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.karandeepsingh-blog]
url = "https://karandeepsingh.ca/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "karandeepsingh-blog": {
      "type": "http",
      "url": "https://karandeepsingh.ca/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: karandeepsingh-blog
Remote MCP URL: https://karandeepsingh.ca/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "karandeepsingh-blog": {
      "url": "https://karandeepsingh.ca/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "karandeepsingh-blog": {
      "type": "http",
      "url": "https://karandeepsingh.ca/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "karandeepsingh-blog",
  "transport": "streamable-http",
  "url": "https://karandeepsingh.ca/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.