MCP OAuth client-interop conformance

MCP server · source repo · graded 2026-10-28Source linked

Prove real MCP clients can connect: 5-client x 3-IdP OAuth matrix with shim fixes.

Outside reports could not be checked just now

MCP OAuth client-interop conformance requires API keys or tokens and links no public GitHub repository; restrict its folder reach, network access, and credentials before installing.

Based on public adoption and transparency signals as of Oct 28, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for MCP OAuth client-interop conformance helpful?

What it can access

Local filesNo local folder access notedLOW
Command executionNo shell command runner notedLOW
Network reachLocal or standard API callsLOW
CredentialsRequires API key or tokenREVIEW
Package sourceSource repository onlyPUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

We hold no install steps for this listing. Follow the project’s own instructions.

All setup options ↓

Compare README badge View project

Everything known

We could not reach our research just now, so this list may be incomplete. Try again later.

0 incidents · 0 advisories · 0 news articles · 0 community threads

Popularity grade: F (from public signals such as stars and downloads, not a code review). Graded 2026-10-28.

Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library.

About MCP OAuth client-interop conformance

MCP OAuth client-interop conformance is an MCP server focused on Developer tools: Prove real MCP clients can connect: 5-client x 3-IdP OAuth matrix with shim fixes.

No standalone npm or PyPI registry package is linked on file; review the project links before installing. Based on its public metadata, its operational scope includes: requires api key or token.

Setup

We hold no install steps for MCP OAuth client-interop conformance. Follow the project’s own instructions.

Why this grade

FF — Many risk signals

Signal-based grade (0/7 points): no public source code found. This reflects adoption and transparency, not a code review.

Popularity and upkeep

4/100

Listing last refreshed: 2026-10-28

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Risks to watch for

Credential & token exposure: Requires API keys or secrets in configuration. Store credentials in environment variables with read-only or minimum required scopes and rotate them regularly.
Unlinked source code repository: No public GitHub repository or registry package is linked on file. Verify the publisher identity and inspect the code before running it locally.

How to lower the risk

Least-privilege permissions

Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

Check its activity history or logs weekly at first, and look at what it changed or sent.
Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

It asks for more access than its job requires, or prompts you to paste passwords.
It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

How do I install MCP OAuth client-interop conformance?

No standalone npm or PyPI package is listed for MCP OAuth client-interop conformance. Use the project links in the Key facts section on this page for installation steps.

Are there security reports about MCP OAuth client-interop conformance?

No reports found for this package in our research. MCP OAuth client-interop conformance currently holds Grade F (Many risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.

Is MCP OAuth client-interop conformance actively maintained?

We do not have star or download counts on file for MCP OAuth client-interop conformance yet (listing refreshed 2026-10-28). Check the commit history and open issues before relying on it.

What are alternatives to MCP OAuth client-interop conformance?

Compare MCP OAuth client-interop conformance side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.

Maintain or use MCP OAuth client-interop conformance? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade F for MCP OAuth client-interop conformance

GitHub README Markdown:

markdown

[![AgentArmorHQ Risk Grade for MCP OAuth client-interop conformance](https://agentarmorhq.com/api/badge/mcp-oauth-client-interop-conformance)](https://agentarmorhq.com/skills/mcp-oauth-client-interop-conformance)

HTML embed:

html

<a href="https://agentarmorhq.com/skills/mcp-oauth-client-interop-conformance"><img src="https://agentarmorhq.com/api/badge/mcp-oauth-client-interop-conformance" alt="AgentArmorHQ Risk Grade for MCP OAuth client-interop conformance" height="20" /></a>

Terminal check:

terminal

curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "mcp-oauth-client-interop-conformance"

Share with your security lead

Need sign-off to use MCP OAuth client-interop conformance? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: MCP OAuth client-interop conformance
- **Listing URL:** https://agentarmorhq.com/skills/mcp-oauth-client-interop-conformance
- **Type:** App connector
- **Risk Grade:** Grade F (Many risk signals)
- **Outside Security Advisories on File:** 0

#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Local or standard API calls
- **Credentials:** Requires API key or token
- **Package source:** Source repository only

#### Recommended Hardened Setup
- Follow repository setup instructions.
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 28, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type: App connector
Est. context load: ~850 tokens / turn (~5 tool schemas, 0.43% of 200k context)
Last updated: 2026-10-28
Last graded: 2026-10-28

Community

Discussions for MCP OAuth client-interop conformance

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for MCP OAuth client-interop conformance helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude