Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CheckMyPayRate

REMOTE · CHECKMYPAYRATE.COM

Salary benchmarks for 20 countries and 13 sectors from OECD and Eurostat data.

+2 this week 82 Trust /100

Last scanned (1 hour ago)

Scores higher than 85% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 265 tokens (~88/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://checkmypayrate.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=checkmypayrate.com CN=WE1,O=Google Trust Services,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA256 4e518e5fba31065c0eca43acd60bd2d2
SANs: checkmypayrate.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of checkmypayrate.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
checkmypayrate.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://checkmypayrate.com/mcp Verified 200
http (plaintext) http://checkmypayrate.com/mcp HTTPS enforced 301 https://checkmypayrate.com/mcp
MCP tools · 3 exposed · ~201 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_salary ~98

Compare a gross annual salary with the country and sector benchmark, returning whether it is below, near, or above the benchmark and by what percentage.

NameTypeReqDescription
countrystringyesCountry code, e.g. USA, UK, DE, EE (see list_options)
salarynumberyesGross annual salary in the country's local currency
sectorstringyesSector code, e.g. it, finance, national (see list_options)
NameTypeReqDescription
averagenumberyes–
currencystringyes–
differencePercentnumberyes–
salarynumberyes–
verdictstringyes–
yearnumberyes–

No examples provided.

get_salary_benchmark ~77

Get the gross average annual salary for a country and sector, based on OECD and Eurostat public data.

NameTypeReqDescription
countrystringyesCountry code, e.g. USA, UK, DE, EE (see list_options)
sectorstringyesSector code, e.g. it, finance, national (see list_options)
NameTypeReqDescription
averagenumberyes–
countrystringyes–
currencystringyes–
sectorstringyes–
yearnumberyes–

No examples provided.

list_options ~26

List the country codes and sector codes supported by the salary benchmarks, with each country's currency.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the CheckMyPayRate MCP server?

CheckMyPayRate is a hosted endpoint at https://checkmypayrate.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · checkmypayrate.com

# add to Claude Code
claude mcp add --transport http markopints34-tech-checkmypayrate 'https://checkmypayrate.com/mcp'
Common questions

What is the CheckMyPayRate MCP server?

CheckMyPayRate is an MCP server listed in the public MCP registry as io.github.markopints34-tech/checkmypayrate. Salary benchmarks for 20 countries and 13 sectors from OECD and Eurostat data. This page covers its hosted endpoint (https://checkmypayrate.com/mcp).

Is the CheckMyPayRate MCP server safe to use?

CheckMyPayRate scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the CheckMyPayRate MCP server expose?

CheckMyPayRate exposes 3 tools: list_options, get_salary_benchmark, compare_salary. Their descriptions and schemas cost roughly 201 tokens of context every time the server is loaded.

Does the CheckMyPayRate MCP server require authentication?

No. We connected to CheckMyPayRate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CheckMyPayRate MCP server still maintained?

CheckMyPayRate is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.