Is Mcp Remote Oauth Client Provider Safe?

Mcp Remote Oauth Client Provider — Nerq Trust Score 48.2/100 (D grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-25

Mcp Remote Oauth Client Provider is a npm package with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Last analyzed: 2026-03-25 Security: 90/100. Popularity: 0/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-25. Machine-readable data (JSON).

Is Mcp Remote Oauth Client Provider safe?

Trust Score Breakdown — Mcp Remote Oauth Client Provider has a Nerq Trust Score of 48.2/100 (D). Measured across 2 independent trust signals (as of 2026-03-25).

Security Analysis → Mcp Remote Oauth Client Provider Privacy Report →

What is Mcp Remote Oauth Client Provider's trust score?

Mcp Remote Oauth Client Provider has a Nerq Trust Score of 48.2/100, earning a D grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
0

What are the key security findings for Mcp Remote Oauth Client Provider?

Mcp Remote Oauth Client Provider's strongest signal is security at 90/100. No known vulnerabilities have been detected.

Security score: 90/100 (strong)
Popularity: 0/100 — community adoption

What is Mcp Remote Oauth Client Provider and who maintains it?

Authorztxtxwd
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

react-library-boilerplate-for-npm (58)bindler (58)@yassidev/nuxt-directus (58)spectro-kubernetes-client (58)pocketto-svelte (58)
See all safest Npm →

Compare

Mcp Remote Oauth Client Provider vs react-library-boilerplate-for-npmMcp Remote Oauth Client Provider vs bindlerMcp Remote Oauth Client Provider vs @yassidev/nuxt-directus

Safety Guide: Mcp Remote Oauth Client Provider

What is Mcp Remote Oauth Client Provider?

Mcp Remote Oauth Client Provider is a Node.js package — OAuth client provider for MultiServerMCPClient.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=mcp-remote-oauth-client-provider

Key Safety Concerns for Node.js package

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Measured Signals

Mcp Remote Oauth Client Provider has a Nerq Trust Score of 48/100 (D). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Mcp Remote Oauth Client Provider Safe?
mcp-remote-oauth-client-provider with a Nerq Trust Score of 48.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Mcp Remote Oauth Client Provider's trust score?
mcp-remote-oauth-client-provider: 48.2/100 (D). Score based on Security (90/100), Popularity (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=mcp-remote-oauth-client-provider
What are safer alternatives to Mcp Remote Oauth Client Provider?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. mcp-remote-oauth-client-provider scores 48.2/100.
Does Mcp Remote Oauth Client Provider have known vulnerabilities?
Nerq checks Mcp Remote Oauth Client Provider against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Mcp Remote Oauth Client Provider actively maintained?
Mcp Remote Oauth Client Provider maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy