OwnerRez MCP Server (buildwithmanag/ownerrez-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 18 tools. The publisher has confirmed an email address for this listing, which proves an inbox rather than ownership (Claimed).

Back to MCP Trust IndexM8ven
C
Emerging
74/100
5 days ago

OwnerRez MCP Server

MCP server that connects OwnerRez to Claude and other MCP clients, enabling natural language management of bookings, guest communication, property info, expenses, and webhooks.

→ buildwithmanag/ownerrez-mcp· listed on glama

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 VerifiedSandbox 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

buildwithmanag · Claimed

Source: Glama

⚡ Upgrade to Live Monitored

Connect your repo and M8ven re-verifies it on the push itself. Without it we re-check verified listings about once a day, so a fix can sit unseen. Read-only, one click, 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
✅
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 4 credentials: OWNERREZ_ACCESS_TOKEN, OWNERREZ_TOKEN, OWNERREZ_WEBHOOK_SECRET, OWNERREZ_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
Are you the publisher? Confirm or correct these findings.
// 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.
configOWNERREZ_BASE_URLAPI base URL
🔐 secretOWNERREZ_ACCESS_TOKENOAuth access token (preferred)
configOWNERREZ_USERNAME→ Personal Access Tokens. Set + OWNERREZ_TOKEN.
🔐 secretOWNERREZ_TOKEN→ Personal Access Tokens. Set OWNERREZ_USERNAME + .
configOWNERREZ_READ_ONLYSet =1 to hard-block every write tool (messaging, expenses,
configOWNERREZ_MAX_RETRIESRetries on 429/5xx
configOWNERREZ_TIMEOUTRequest timeout (seconds)
configOWNERREZ_STOREConfig: (db path, default ~/.ownerrez-mcp/messages.db),
configOWNERREZ_WEBHOOK_HOST/ OWNERREZ_WEBHOOK_PORT, and an optional
configOWNERREZ_WEBHOOK_PORTOWNERREZ_WEBHOOK_HOST / , and an optional
🔐 secretOWNERREZ_WEBHOOK_SECRET(sent as X-Webhook-Secret or ?secret=) to reject
configOWNERREZ_CLIENT_IDset + OWNERREZ_CLIENT_SECRET, then run the built-in helper:
🔐 secretOWNERREZ_CLIENT_SECRETset OWNERREZ_CLIENT_ID + , then run the built-in helper:
configOWNERREZ_REDIRECT_URI
configOWNERREZ_AUTHORIZE_URL
configOWNERREZ_TOKEN_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

18/18 tools missing one or more hints — list_bookings (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_booking (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); who_is_staying (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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 3/18 tools referenced in tests (17%)

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/buildwithmanag/ownerrez-mcp)](https://m8ven.ai/mcp/buildwithmanag/ownerrez-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 0f25cf93b9628cb496d457f4f34c0a43ac817b60
code hash: 60bb4c69e74659a6b3625b8eb76cd691bef679c2c801ca3827318e8e28358d31
verified: 9/5/2026, 10:46:53 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