F
Warning
36/100
4 days ago

aistatusdashboard

Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.

Warning. Serious findings were identified. Review the full report before connecting. 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

aistatusdashboard

Source: modelscope · also listed on PulseMCP

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
🚨
Secret credentials may flow to a network call
5 flows detected: MAILTM_TOKEN, APP_CRON_SECRET, NEXT_PUBLIC_TELEMETRY_PUBLIC_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: FIREBASE_PRIVATE_KEY, FIREBASE_SERVICE_ACCOUNT_KEY, MCP_ORG_TOKEN, SYNTHETIC_INGEST_SECRET, TELEMETRY_INGEST_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies16 high10 medium11 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highnext@16.1.1GHSA-267c-6grr-h53f

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

highnext@16.1.1GHSA-26hh-7cqf-hhc6

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

highnext@16.1.1GHSA-36qx-fr4f-26g5

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

highnext@16.1.1GHSA-492v-c6pp-mqqv

Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

highnext@16.1.1GHSA-6gpp-xcg3-4w24

Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configALERT_SIGNUP_NOTIFY_EMAIL
configAPP_BUILD_ID
configAPP_ENABLE_EMAIL
configAPP_ENABLE_REAL_MONITORING
configAWS_DEFAULT_REGION
configAWS_REGION
configCOMMIT_SHA
configCONTACT_EMAIL
configFIREBASE_CLIENT_EMAIL
🔐 secretFIREBASE_PRIVATE_KEY
configFIREBASE_PROJECT_ID
🔐 secretFIREBASE_SERVICE_ACCOUNT_KEY
configGITHUB_SHA
configGOOGLE_SITE_VERIFICATION
configGOOGLE_SITE_VERIFICATION_ALT
🔐 secretMCP_ORG_TOKEN
configPROBE_ENABLED
🔐 secretSYNTHETIC_INGEST_SECRET
configTELEMETRY_ENABLED
🔐 secretTELEMETRY_INGEST_SECRET
configTELEMETRY_SALT
configTEST_FRONTEND_URL
configTEST_TYPE
configWEBHOOK_MAX_FAILURES
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_CONTACT_EMAIL
deployNEXT_PUBLIC_ENABLE_SW_ON_LOCALHOST
deployNEXT_PUBLIC_EXPORT_DEBUG
deployNEXT_PUBLIC_FIREBASE_PROJECT_ID
deployNEXT_PUBLIC_GA_MEASUREMENT_ID
deployNEXT_PUBLIC_MCP_ANNOUNCEMENT_URL
deployNEXT_PUBLIC_SITE_URL
deployNEXT_PUBLIC_TELEMETRY_PUBLIC_KEY
deploySMTP_FROM
deploySMTP_HOST
deploySMTP_IGNORE_TLS
deploySMTP_PASSWORD
deploySMTP_PORT
deploySMTP_SECURE
deploySMTP_USER
// quality suggestions

Dependencies

36 dependencies, 1 flagged: @playwright/test

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

7/7 tools missing one or more hints — status.get_summary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); status.get_health_matrix (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); incidents.search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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 0/7 tools referenced in tests (0%)

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

Secrets stay with their owner

4 secret/sensitive values flow into network calls (MAILTM_TOKEN → dynamic, MAILTM_TOKEN → dynamic) (1 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not written to files

2 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 13 high severity in production deps — next@16.1.1 (high), next@16.1.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

3 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

1/10 production deps stale: web-push@2024-01-16 (2.6y)

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 8 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 Verified](https://m8ven.ai/badge/mcp/aistatusdashboard-aistatusdashboard-h68eoj?variant=verified)](https://m8ven.ai/mcp/aistatusdashboard-aistatusdashboard-h68eoj)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: a1a2c5065be952f60b76fe8af651e012a720839f
code hash: 85f8389b8923366f46726d76a7716f34099720435241b287a0c1a702dff0a31f
verified: 8/15/2026, 9:30:49 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