Skip to main content

mcp-issuer-check

See which OAuth server your MCP servers send your login to, verify it isn't being impersonated, and get alerted if it changes.

CI License: MIT Python 3.11+ Zero dependencies

When you connect Claude, Cursor, VS Code or another client to a remote MCP server, the server tells the client which authorization server to log you in with. The client then sends your authorization code, PKCE verifier, client secret or refresh token there.

mcp-issuer-check reads your MCP client configs, finds each remote server's login server the same way a client does, and:

  • verifies the metadata: the RFC 8414 issuer must match the authorization server URL, the RFC 9728 resource must match the server you configured, and everything must use HTTPS;
  • pins the login servers you've approved (trust on first use) and flags any later change (PIN-CHANGED);
  • guards against SSRF: it won't follow an authorization server that points at a private or internal address.

It sends no credentials and reads no secrets from your configs, only server names and URLs.

mcp-issuer-check output

Why this exists

In 2026 the official MCP SDKs shipped fixes for OAuth clients that sent credentials to whichever authorization server the MCP server named (GHSA-6qxp-vccf-f47h, GHSA-qx49-fqc8-xw99). A malicious or compromised MCP server could name its own authorization server. Or it could publish no metadata and serve some that presents your real provider as the issuer.

The SDK fixes bind stored credentials to an issuer. Everything else rests on the client trusting what the server advertises the first time. The Cloud Security Alliance's November 2026 note recommends keeping an allowlist that maps each MCP server to the authorization servers it may name. No tool did that, so this one does, from your existing client configs.

Install

pipx install mcp-issuer-check

Python 3.11+, no third-party dependencies.

Usage

mcp-issuer-check                 # discover servers in your client configs and check them
mcp-issuer-check list            # just show which remote MCP servers were found, and where
mcp-issuer-check pin             # approve the current login servers (refuses servers with bad metadata)
mcp-issuer-check --url https://mcp.example.com/mcp      # check specific servers
mcp-issuer-check --project path/to/repo                 # include .mcp.json / .cursor / .vscode configs there
mcp-issuer-check -f json         # machine-readable
mcp-issuer-check --fail-on high  # exit 1 only on high (default: medium)

Typical flow: run it once, review the login via lines, run pin, then run it again whenever you like (or on a schedule). A change is reported as PIN-CHANGED: don't sign in until the provider confirms it.

Exit codes: 0 nothing at or above --fail-on, 1 findings (or pin refused a server).

Configs it reads

Client Files
Claude Code ~/.claude.json (user and per-project), ~/.claude/settings.json, .mcp.json
Claude Desktop claude_desktop_config.json (Windows, macOS, Linux paths)
Cursor ~/.cursor/mcp.json, .cursor/mcp.json
VS Code user mcp.json and settings.json (JSONC), .vscode/mcp.json
Windsurf ~/.codeium/windsurf/mcp_config.json
Gemini CLI ~/.gemini/settings.json, .gemini/settings.json
Codex ~/.codex/config.toml

Local (stdio) servers are skipped because they don't use OAuth discovery.

Findings

Code Severity Meaning
ISSUER-MISMATCH high Authorization server metadata claims a different issuer than its URL (RFC 8414 §3.3). This is the impersonation shape.
PIN-CHANGED / ISSUER-CHANGED high Login server differs from the one you pinned.
INSECURE-TRANSPORT high Server, metadata or endpoint over plain HTTP (allowed only on loopback).
AS-PRIVATE-ADDRESS high Authorization server on a private/internal address; not fetched.
RESOURCE-MISMATCH medium Metadata describes a different resource than the configured URL (RFC 9728 §3.3).
PRM-CROSS-ORIGIN medium The 401 points to resource metadata on another origin.
NO-METADATA medium Requires auth but publishes no RFC 9728 metadata, so clients fall back to legacy discovery.
ENDPOINT-GONE medium Configured URL returns 404/410.
AS-NO-METADATA medium No RFC 8414/OIDC metadata for a listed authorization server.
ENDPOINT-OTHER-HOST low Token/authorization/registration endpoint on a different host than the issuer. Usually fine; confirm it.
NOT-PINNED, PIN-UNVERIFIED, UNREACHABLE low Review or retry.
AS-OTHER-HOST, NO-OAUTH info Login is hosted elsewhere (common: GitHub, Stripe), or the server is public.

GitHub Action: alert when a provider changes its login server

name: mcp-issuer-check
on:
  schedule: [{cron: "23 7 * * *"}]
  workflow_dispatch:
jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: garag0l/mcp-issuer-check@v0.1.1
        with:
          urls: |
            https://mcp.notion.com/mcp
            https://api.githubcopilot.com/mcp/
          pins: .github/mcp-pins.json   # create with: mcp-issuer-check pin --url ... --pins .github/mcp-pins.json
          fail-on: high

TLS errors

If a server works in your browser but shows TLS verification failed, your Python CA store is probably missing a root. Some Windows setups lack the newer Let's Encrypt roots, for example. Use --ca-bundle /path/to/cacert.pem (e.g. from certifi) or set SSL_CERT_FILE. Verification is never turned off.

How it discovers (same order as the MCP spec)

  1. Unauthenticated initialize POST, read WWW-Authenticate: Bearer resource_metadata="…".
  2. RFC 9728 metadata: the URL from step 1, then /.well-known/oauth-protected-resource/<path>, then the root.
  3. For each authorization_servers entry: RFC 8414 /.well-known/oauth-authorization-server/<path>, then the OpenID Connect variants.

Redirects are not followed. Responses are capped at 512 KB.

Tested against 20 public MCP server endpoints from 19 providers (Notion, Linear, Sentry, GitHub, Atlassian, Stripe, Asana, Cloudflare, PayPal, Square, Intercom, Vercel, Supabase, Hugging Face, Context7, DeepWiki, monday.com, HubSpot, Webflow) and a mock server covering every finding.

Scope and responsible use

This is a defensive tool for checking the MCP servers you use or are authorized to assess. It only fetches public discovery metadata, the same requests any MCP client makes before you sign in.

Contributing

Issues and PRs are welcome, especially config locations for more clients, and real-world metadata quirks (with the server URL).

python -m venv .venv && . .venv/bin/activate
pip install -e ".[dev]"
pytest && ruff check . && ruff format --check .

License

MIT

Metadata

Release files for mcp-issuer-check 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-issuer-check 0.1.1
File Size Uploaded Provenance Actions
mcp_issuer_check-0.1.1.tar.gz 22.3 kB With provenance Details for mcp_issuer_check-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcp-issuer-check 0.1.1
File Interpreter ABI Platform Actions
mcp_issuer_check-0.1.1-py3-none-any.whl Python 3 none any Details for mcp_issuer_check-0.1.1-py3-none-any.whl

Total release size: 38.4 kB

Release files / mcp_issuer_check-0.1.1.tar.gz

Download URL mcp_issuer_check-0.1.1.tar.gz
Size 22.3 kB
Tags Source
SHA-256 checksum
How to use checksums
88cc9a14bfd714889638001537b3fb24beebee77e37dea6fd7fd77f72ce70ed7
BLAKE2b-256 checksum
How to use checksums
bdaadb9583d81816cf3ae153e844f0984d5db59e3463d9b88a509bc19655f406
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

Release files / mcp_issuer_check-0.1.1-py3-none-any.whl

Download URL mcp_issuer_check-0.1.1-py3-none-any.whl
Size 16.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
92b75c33047d53346f2825ca58d01b0483a450576b30078fd57a9476b908e9f4
BLAKE2b-256 checksum
How to use checksums
02854ec32d6afe2279df92bfdfcd166dcc37de9e860d603cc778cc6878c85c19
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

Security for mcp-issuer-check 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mcp_issuer_check-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page