Repliers MCP Server (Repliers-io/mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Repliers MCP Server

Provides AI assistants access to real-time MLS data via the Repliers API, enabling natural language property search, market statistics, and listing details.

→ Repliers-io/mcp-server· 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

⚡ 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

Repliers-io

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

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
46 flows detected: OAUTH_USERINFO_ENDPOINT, OAUTH_BASE_URL, REPLIERS_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 5 credentials: OAUTH_CLIENT_SECRET, PROPELAUTH_API_KEY, REPLIERS_API_KEY, TRELLO_API_KEY, TRELLO_API_TOKEN
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.
configFEEDBACK_DRY_RUN
configFEEDBACK_DRY_RUN_LOG
configFEEDBACK_PROMPT_LEVELoff — no nudges; low — nudges only on detected problems (zero results, missing location filter, API errors, oversized responses); high — also a verify/offer note on every search response.
configOAUTH_AUTHORIZATION_ENDPOINT
configOAUTH_BASE_URL
configOAUTH_CLIENT_ID
🔐 secretOAUTH_CLIENT_SECRET
configOAUTH_TOKEN_ENDPOINT
configOAUTH_USERINFO_ENDPOINT
🔐 secretPROPELAUTH_API_KEY
configREPLIERS_API_BASE_URLTo run against a deployment other than production, add (default
🔐 secretREPLIERS_API_KEY
🔐 secretTRELLO_API_KEYFeedback sink. All three set → the send-feedback tool is registered and _feedback nudges are emitted. Any missing → the tool is hidden and nudges are suppressed.
🔐 secretTRELLO_API_TOKENFeedback sink. All three set → the send-feedback tool is registered and _feedback nudges are emitted. Any missing → the tool is hidden and nudges are suppressed.
configTRELLO_LIST_IDFeedback sink. All three set → the send-feedback tool is registered and _feedback nudges are emitted. Any missing → the tool is hidden and nudges are suppressed.
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Secrets stay with their owner

2 secrets sent to a request target we could not resolve (OAUTH_USERINFO_ENDPOINT → dynamic, OAUTH_BASE_URL → dynamic) — often a configured endpoint, not necessarily third-party

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

Secrets not logged

8 secret values sent to error

Redact or omit secret values from log output.

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 2 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/repliers-io/mcp-server)](https://m8ven.ai/mcp/repliers-io/mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 032083ff05841b5535a326a6c14c488403cec560
code hash: c324b930136a06b1cf990c48782d99ba20ce9a8a27781a78e5b046d620fade56
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