goldenmatch (benseverndev-oss/goldenmatch) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 230 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
23 days ago

goldenmatch

Zero-config entity resolution feeding a durable identity layer: messy records from any source become stable golden entities, a Customer 360 with provenance, merge/split and audit. Fellegi-Sunter beats hand-tuned Splink. Arrow-native/Rust, 250M rows in 11.2 min. Python + edge TypeScript (WASM), SQL-native in Postgres & DuckDB, 97 MCP tools + REST.

→ benseverndev-oss/goldenmatch· listed on pulsemcp

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

benseverndev-oss

Source: PulseMCP · also listed on github_topic

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

PulseMCPGitHub

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

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 9 credentials: GOLDENCHECK_AGENT_TOKEN, GOLDENMATCH_MCP_TOKEN, GOLDENMATCH_AGENT_TOKEN, GOLDENMATCH_API_TOKEN, GOLDENMATCH_WEB_TOKEN, GOLDENMATCH_BENCH_JOB_TOKEN, OPENAI_API_KEY, GITHUB_TOKEN, GH_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.
🔐 secretGOLDENCHECK_AGENT_TOKEN
configGOLDENCHECK_TYPES_TEST_DIR
configVITE_API_TARGET
🔐 secretGOLDENMATCH_MCP_TOKEN
configGOLDENMATCH_MCP_ALLOW_PUBLIC
configGOLDENPIPE_ALLOWED_ROOT
configGOLDENSUITE_MCP_TOOLS
🔐 secretGOLDENMATCH_AGENT_TOKEN
🔐 secretGOLDENMATCH_API_TOKEN
configGOLDENMATCH_API_CORS_ORIGINS
configGOLDENMATCH_NATIVE
configGOLDENCHECK_FORCE_TUI
configGOLDENFLOW_LLM
🔐 secretGOLDENMATCH_WEB_TOKEN
configGOLDENSUITE_MANIFEST_PATH
configGOLDENMATCH_BENCH_DATA_DIR
🔐 secretGOLDENMATCH_BENCH_JOB_TOKEN
configSQLSERVER_CONNECTION
configGITHUB_OUTPUT
configGOLDENMATCH_GPU_MODE
configGOLDENMATCH_FS_NATIVE
configGOLDENMATCH_FS_CALIBRATED
configGOLDENMATCH_AUTOCONFIG_MEMORY
configGOLDENMATCH_FS_BLOCK_SOURCE
configGOLDENMATCH_FS_SEQUENTIAL_BOUNDED_SCORING
configGOLDENMATCH_FS_SPILL_FORCE_SHARD
configGOLDENMATCH_FS_OOC_DEBUG
configGOLDENMATCH_FS_OUT_OF_CORE
configGOLDENMATCH_FS_BLOCKING_SN_BOUND
configGOLDENMATCH_FS_COLUMNAR_CLUSTER
configGOLDENMATCH_NATIVE_RAYON_MIN_PAIRS
configGOLDENMATCH_SPARK_REMOTE
configGOLDENMATCH_SPARK_PYENV
configGITHUB_STEP_SUMMARY
configPOLARS_SKIP_CPU_CHECK
configGOLDENMATCH_ENABLE_DISTRIBUTED_RAY
🔐 secretOPENAI_API_KEY
configGOLDENMATCH_DISTRIBUTED_PIPELINE
configGOLDENMATCH_DISTRIBUTED_BLOCK_SHUFFLE
configGOLDENMATCH_DISTRIBUTED_WCC_SCRATCH
configEMB_DATA_DIR
configGCP_SA_KEY_B64
configGOOGLE_APPLICATION_CREDENTIALS
configVERTEX_GCP_PROJECT
configGOOGLE_CLOUD_PROJECT
configEMB_PROVIDERS
configEMB_DATASETS
configEMB_EPOCHS
configEMB_SYNTH_ROWS
configQIS_ROWS
configQIS_SHAPE
configQIS_SEED
configQIS_BACKEND
configQIS_CORRUPTION
configQIS_FROZEN
configGOLDENMATCH_NCVR_SAMPLE_URL
🔐 secretGITHUB_TOKEN
🔐 secretGH_TOKEN
configSPLINK_DRIVER_HOST
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

230/230 tools missing one or more hints — list_analyzers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); analyze_frame (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_trend (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +227 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

125/230 tools referenced in tests (54%)

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

Secrets not written to files

1 secret value written to files

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

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 4 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/benseverndev-oss/goldenmatch)](https://m8ven.ai/mcp/benseverndev-oss/goldenmatch)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c0c7aefd48ce7216403aef658f525b56ef9a72c1
code hash: 013d4b4eae6b35c5a6e289a24eafadedab9b6f3cfe0b3f0a739a474a47e2efec
verified: 8/18/2026, 9:44:31 PM
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