C
Emerging
74/100
6 days ago

ScopeGate

Permission gateway that hands an AI agent a scoped MCP endpoint instead of an OAuth token: connect 27 services (Gmail, Google Calendar/Drive/Ads/Search Console, Slack, Notion, GitHub, Jira, Salesforce, HubSpot, Stripe, LinkedIn, X, Meta Ads and more), grant per-action permissions finer than native OAuth scopes, audit every call and revoke a key in one click. Self-hostable, MIT.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

alifanov

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 8 credentials: ADMIN_PASSWORD, BETTER_AUTH_SECRET, CRON_SECRET, GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_SIGNIN_CLIENT_SECRET, POLAR_ACCESS_TOKEN, POLAR_WEBHOOK_SECRET, RESEND_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configADMIN_EMAILBootstrap admin email
🔐 secretADMIN_PASSWORDBootstrap admin password
🔐 secretBETTER_AUTH_SECRETPostgres and a fresh are provisioned automatically, and the
configBETTER_AUTH_URLApp base URL (e.g. http://localhost:3000)
🔐 secretCRON_SECRET
configEMAIL_FROM
🔐 secretGOOGLE_ADS_DEVELOPER_TOKEN
configGOOGLE_SIGNIN_CLIENT_ID
🔐 secretGOOGLE_SIGNIN_CLIENT_SECRET
configOTEL_EXPORTER_OTLP_ENDPOINT
configOTEL_SERVICE_NAME
🔐 secretPOLAR_ACCESS_TOKEN
🔐 secretPOLAR_WEBHOOK_SECRET
🔐 secretRESEND_API_KEY
configSCOPEGATE_CLOUD
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

386/386 tools missing one or more hints — ahrefs_domain_rating (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ahrefs_backlinks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ahrefs_organic_keywords (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +383 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 6/386 tools referenced in tests (2%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/alifanov-scopegate-1l3w4k)](https://m8ven.ai/mcp/alifanov-scopegate-1l3w4k)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: f9c3b5fa6f5cbb7329cfc352cf7d6453305a611e
code hash: 30d4af95730e19a84250bba6ddd58f5be72d16dcd65deebe31fee64404d187f7
verified: 8/16/2026, 9:07:25 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client