Skip to main content
Glama
fischperson0000000

GetMyCert

by fischperson0000000
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

GetMyCert MCP Server

A Model Context Protocol server that gives any MCP-compatible AI agent (Claude Desktop, Claude Code, Cursor, Windsurf, Continue, Zed, etc.) live access to 13,072 IT certification practice questions across 27 certifications on GetMyCert.com.

Pay-per-call via x402 micropayments (USDC on Base, no signup) — or use a traditional prepaid API key.

Tools exposed

Tool

Description

get_cert_questions

Fetch 1-25 multiple-choice questions for a certification, optionally filtered by difficulty.

list_certifications

List all 27 available certifications and their question counts.

Covered certifications

AWS (SAA, SysOps, Developer, Cloud Practitioner, Solutions Architect Pro), CompTIA (A+, Network+, Security+, CySA+, CASP+, PenTest+, Cloud+, Data+, Linux+, Server+), Google Cloud (ACE, PCA), Azure (Fundamentals, Administrator, Developer, Security), Cisco CCNA, Kubernetes CKAD, PMP, CISSP, CEH, ITIL 4.

Related MCP server: x402tools MCP Server

Install

From npm (recommended)

npm install -g @getmycert/mcp-server

From source

git clone https://github.com/getmycert/mcp-server.git
cd mcp-server
npm install
npm run build

The build emits an executable at dist/index.js.

Configure

You need one of the two payment methods.

Option 1 — x402 micropayments (recommended)

  1. Generate a hot wallet private key:

    openssl rand -hex 32

  2. Fund the wallet's Base-mainnet address with a few dollars of USDC. Each batch of questions costs ~$0.01.

  3. Set GETMYCERT_WALLET_PRIVATE_KEY=0x<your_key> in your agent's MCP config (see snippets below).

Option 2 — Prepaid API key

  1. Get an API key at https://getmycert.com/dashboard/api-keys.

  2. Set GETMYCERT_API_KEY=<your_key> in the MCP config.

If both are configured, the server prefers x402 and falls back to the API key on failure.

All available env vars are documented in .env.example.

Add to your agent

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "getmycert": {
      "command": "npx",
      "args": ["-y", "@getmycert/mcp-server"],
      "env": {
        "GETMYCERT_WALLET_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY_HERE"
      }
    }
  }
}

Restart Claude Desktop. You should see the GetMyCert tools listed under the hammer icon.

Claude Code

Add to ~/.claude.json (global) or .claude.json in your project:

{
  "mcpServers": {
    "getmycert": {
      "command": "npx",
      "args": ["-y", "@getmycert/mcp-server"],
      "env": {
        "GETMYCERT_API_KEY": "gmc_live_..."
      }
    }
  }
}

Or one-liner:

claude mcp add getmycert -- npx -y @getmycert/mcp-server

Cursor

Edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "getmycert": {
      "command": "npx",
      "args": ["-y", "@getmycert/mcp-server"],
      "env": {
        "GETMYCERT_WALLET_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY_HERE"
      }
    }
  }
}

Windsurf / Continue / Zed

These all use the same stdio-MCP shape. Point them at npx -y @getmycert/mcp-server with the same env block.

Local dev build

If you cloned from source, replace the command/args with your built path:

{
  "mcpServers": {
    "getmycert": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server/dist/index.js"],
      "env": {
        "GETMYCERT_WALLET_PRIVATE_KEY": "0x..."
      }
    }
  }
}

Usage examples

Once installed, your agent can call the tools directly. Example prompts:

"Give me 5 hard CISSP practice questions."

"Quiz me on AWS SAA — 10 medium-difficulty questions, hide answers until I respond."

"List every CompTIA certification on GetMyCert with question counts."

How x402 payment works

  1. Agent calls get_cert_questions.

  2. The MCP server hits https://getmycert.com/api/v1/x402.

  3. Server replies HTTP 402 Payment Required with the cost (e.g. 10000 micro-USDC = $0.01), recipient address, and USDC contract.

  4. The MCP server signs an EIP-3009 transferWithAuthorization from the configured wallet and retries with X-PAYMENT: <base64-payload>.

  5. The facilitator settles on-chain; GetMyCert returns the questions.

The GETMYCERT_MAX_PAYMENT env var caps how much any single call may charge (default 100000 = $0.10).

Environment variables

Variable

Required

Default

Purpose

GETMYCERT_WALLET_PRIVATE_KEY

one of

—

32-byte hex private key for the Base wallet that pays the x402 endpoint.

GETMYCERT_API_KEY

one of

—

Prepaid API key fallback.

GETMYCERT_RPC_URL

no

https://mainnet.base.org

Base RPC endpoint.

GETMYCERT_X402_URL

no

https://getmycert.com/api/v1/x402

x402 endpoint override.

GETMYCERT_API_URL

no

Supabase edge function

API-key endpoint override.

GETMYCERT_CERTS_URL

no

https://getmycert.com/api/v1/certifications

Public catalog endpoint override.

GETMYCERT_MAX_PAYMENT

no

100000

Max micro-USDC any one call may pay.

Hosted / remote MCP

The package also exports createServer() so you can host it behind an HTTP transport (SSE or Streamable HTTP) without modifying the tool code:

import { createServer } from "@getmycert/mcp-server";
import { SSEServerTransport } from "@modelcontextprotocol/sdk/server/sse.js";

const server = createServer();
// wire SSEServerTransport into your HTTP framework of choice

Submit to registries

This server is designed to be listed on community MCP registries.

License

MIT — see LICENSE.

Available Tools

2 tools
get_cert_questionsA

Get IT certification practice questions from GetMyCert.com. Supports 27 major IT certifications including AWS, CompTIA, Google Cloud, Azure, and Cisco. Returns multiple-choice questions with options and explanations.

ParametersJSON Schema
NameRequiredDescriptionDefault
certificationYesCert slug e.g. 'aws-saa', 'comptia-security-plus'. Call list_certifications for all options.
countNoNumber of questions to return (1-25, default 10).
difficultyNoOptional difficulty filter.
include_answersNoInclude correct answer and explanation (default true).

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden. It discloses the return format (multiple-choice questions with explanations) and coverage (27 certifications). However, it does not mention side effects (likely none), rate limits, authentication requirements, or data freshness, leaving gaps for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose, followed by supported certifications and output format. No superfluous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given moderate complexity (4 parameters, no output schema), the description covers purpose, supported inputs, and output nature. It references the sibling tool but lacks error handling or authentication context. Still, it is complete enough for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the description adds limited value beyond the schema. It mentions supported certifications and output format but does not provide additional meaning for individual parameters beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves IT certification practice questions from GetMyCert.com, lists supported certifications (AWS, CompTIA, etc.), and specifies the return format (multiple-choice questions with options and explanations). It distinguishes itself from the sibling tool list_certifications.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description guides use by mentioning the need to call list_certifications for available certification options, indicating when to use this tool and when to use the sibling. However, it lacks explicit when-not scenarios or prerequisites like authentication.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_certificationsA

List all available IT certifications on GetMyCert.com with question counts. Use this to discover valid certification slugs for get_cert_questions.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions output includes question counts, but does not disclose any potential side effects (none expected), rate limits, or authentication needs. Adequate for a simple read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no redundancy. First sentence states action and output, second provides usage guidance. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, no-output-schema tool, the description covers the purpose and usage adequately. Could explicitly mention the return format, but the mention of 'question counts' gives sufficient clue. Not missing critical information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters (0 params, schema coverage 100%), so baseline is 4. The description does not need to add parameter info; it instead adds value by stating the output content (question counts) and usage context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') and resource ('certifications'), includes the context of question counts, and explicitly ties to discovering slugs for the sibling tool get_cert_questions, clearly distinguishing it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool ('discover valid certification slugs for get_cert_questions'), implying it should be called before the sibling. Does not cover when not to use, but the single sibling makes it clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedget_cert_questions
    • First observedlist_certifications
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one lists available certifications, the other retrieves practice questions for a given certification. No overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern in snake_case: 'list_certifications' and 'get_cert_questions'. The naming is predictable and uniform.

Tool Count3/5

With only 2 tools, the server is minimal. For a focused domain of retrieving practice questions, this might be sufficient, but it borders on too few for a more comprehensive toolkit.

Completeness5/5

The server covers the essential workflow: discover certifications and retrieve questions with explanations. No obvious missing operations for the stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • x402tools MCP Server

    acrylicfiddle
    A
    license
    A
    quality
    C
    maintenance
    Provides AI agents with 10 pay-per-call utility tools (QR generation, DNS lookup, OCR, etc.) using USDC on Base via the x402 protocol, with agent's private key never leaving the agent.
    11
    67
    MIT
  • oom-x402-mcp by OrdersOfMagnitudeLLC

    oom-x402-mcpofficial

    OrdersOfMagnitudeLLC
    F
    license
    Not graded
    quality
    B
    maintenance
    MCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.
    -