Back to MCP Trust Indexm8ven
F
Warning
28/100
3 days ago

AR LABS Admin MCP Server

Full-access MCP server for managing AR LABS (Viral AI Prompts & Guides), enabling post creation, editing, deletion, image uploads, push notifications, comment moderation, and site stats via AI assistants.

→ abdulrehmanfatehali1-ui/ar-labs-mcp-server· listed on glama

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

abdulrehmanfatehali1-ui

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glama

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

// key findings
🚨
Secret credentials may flow to a network call
6 flows detected: IMGBB_API_KEY, ONESIGNAL_REST_KEY, FIREBASE_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Hardcoded credentials detected
1 live-looking API key in source: 1 Google API key
🔐
You'll be asked for 4 credentials: FIREBASE_ADMIN_PASSWORD, FIREBASE_API_KEY, IMGBB_API_KEY, ONESIGNAL_REST_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.
configFIREBASE_ADMIN_EMAIL
🔐 secretFIREBASE_ADMIN_PASSWORD
🔐 secretFIREBASE_API_KEY
configFIREBASE_DB_URL
🔐 secretIMGBB_API_KEY
configONESIGNAL_APP_ID
🔐 secretONESIGNAL_REST_KEY
configSITE_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

20/20 tools missing one or more hints — list_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

No hardcoded API keys

1 live-looking API key in source: 1 Google API key

Move secrets to environment variables (process.env.X) or your secret manager.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (FIREBASE_API_KEY → dynamic) (5 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.

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 6 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/abdulrehmanfatehali1-ui-ar-labs-mcp-server-1kmogc?variant=verified)](https://m8ven.ai/mcp/abdulrehmanfatehali1-ui-ar-labs-mcp-server-1kmogc)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f85be63799dafef5c23e18d4653ce95af692096d
code hash: 5098100acec0435f16666ef7794ed5cb5e01bad0467f3aafa259479519a1c4e3
verified: 8/16/2026, 9:15:56 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