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

Back to MCP Trust IndexM8ven
C
Caution
74/100

ReAI MCP Server

MCP server for FSM report migration analysis, providing fuzzy search of report mappings, pattern registry, and columnar report generation.

→ van0219/reai-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

van0219

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
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

reai_search_v10v11

Search the V10-V11 mapping database for S3/Lawson to FSM report migration paths. Returns report codes, names, modules, statuses, and FSM navigation paths. Use this to find how legacy S3/Lawson reports map to FSM (CloudSuite Financials). The database contains 967+ mappings across 20+ modules.

reai_v10v11_modules

List all FSM modules in the V10-V11 mapping database with report counts. Useful for understanding what modules are covered and how many reports each has.

reai_v10v11_stats

Get V10-V11 mapping database statistics: total reports, total navigation paths, module breakdown. Good for getting an overview of the migration knowledge base.

reai_search_bre100

Search the BRE-100 pattern registry for report migration patterns. Each pattern includes: business process, FSM classification, navigation path, future state recommendation, tool selection, timeline estimate, complexity rating, and client project history. The registry contains 617+ patterns from 11 …

reai_bre100_high_value

Get high-value BRE-100 patterns (used by multiple clients). These represent standardization opportunities — reports that appear across many implementations and should use consistent FSM solutions.

reai_bre100_stats

Get BRE-100 pattern registry statistics: total patterns, breakdown by business process and complexity.

reai_generate_columnar

Generate Columnar LPL code package for FSM. Produces 4 files: .form (filter form), .list (columnar list with charts), .field (custom derived fields), and .csv (replication set import). Provide the report name, business class, and field definitions.

// known CVEs in dependencies1 high

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

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

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.
configREAI_BRE100_DBFull path to bre100_registry.db $REAI_DATA_DIR/bre100_registry.db
configREAI_DATA_DIR"": "/path/to/reai_web/data"
configREAI_V10V11_DBFull path to v10v11_mapping.db $REAI_DATA_DIR/v10v11_mapping.db
// 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

7/7 tools missing one or more hints — reai_search_v10v11 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); reai_v10v11_modules (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); reai_v10v11_stats (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.

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high)

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

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 5 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/van0219/reai-mcp?variant=verified)](https://m8ven.ai/mcp/van0219/reai-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 9acd93fdba82aece008052057f2ff9b13b7e306a
code hash: dd532f349b3993c936b4ac56c2c6bb04a4bf6382e03492c1e4b7d08786b19190
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