Provenancewhere it came from, and what was verified
Published to the official MCP registry by github.com/benseverndev-oss, which proved it owns this namespace.
🛡 Permissions & trustwhat this server can touch before you run it
About
Find duplicate records in 30 seconds. Zero-config entity resolution, 97.2% F1 out of the box.
Packages & transports
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
▸analyze_data83B
▸auto_configure92A
▸controller_telemetry100A
▸agent_deduplicate81B
▸agent_match_sources76B
▸agent_explain_pair65C
▸agent_explain_cluster65C
▸agent_review_queue65C
▸agent_approve_reject65C
▸agent_compare_strategies79B
▸suggest_pprl83B
▸scan_quality100A
▸fix_quality100A
▸run_transforms100A
▸sensitivity100A
▸incremental95A
▸certify_recall100A
▸retrieve_similar100A
▸upload_dataset100A
▸list_corrections93A
▸add_correction93A
▸list_plugins68C
▸learn_thresholds93A
▸memory_stats93A
▸memory_export81B
▸memory_import100A
▸identity_resolve100A
▸identity_list58C
▸identity_history65C
▸identity_conflicts58C
▸identity_merge83B
▸identity_split83B
▸identity_claim92A
▸identity_resolve_conflict83B
▸identity_audit68C
▸identity_audit_seal85A
▸identity_audit_verify81B
▸identity_show83B
▸identity_profile88A
▸identity_stats81B
▸identity_worklist75B
▸plan_routing75B
▸explain_routing75B
▸lint_routing75B
▸get_stats100A
▸find_duplicates100A
▸explain_match100A
▸list_clusters93A
▸get_cluster100A
▸get_golden_record90A
▸match_record100A
▸unmerge_record100A
▸shatter_cluster100A
▸suggest_config100A
▸review_config100A
▸profile_data100A
▸export_results90A
▸list_domains100A
▸create_domain100A
▸test_domain100A
▸pprl_auto_config93A
▸pprl_link93A
▸evaluate83B
▸analyze_blocking77B
▸compare_clusters93A
▸schema_match85A
▸lineage77B
▸list_runs68C
▸rollback75B
▸config_weaknesses93A
▸dedupe100A
▸match100A
▸explain_pair100A
▸profile100A
▸explain_cluster75B
▸documents_suggest_schema75B
▸documents_ingest83B
Structural, not an LLM's opinion: each check is a fact about the tool's schema, so it's reproducible. One weak tool drags the score (60% average, 40% worst). How it's scored →
Raise this grade
up to +9 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
- Description is short (55 chars). Expand past 60 for full credit.
- 5 of 5 params have no description: `path`, `limit`, `offset`, `status`, +1 more. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- Description is short (44 chars). Expand past 60 for full credit.
- 2 of 2 params have no description: `path`, `dataset`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- Description is short (46 chars). Expand past 60 for full credit.
- 4 of 4 params have no description: `exact`, `fuzzy`, `record_a`, `record_b`. Describe each one.
- Description is short (43 chars). Expand past 60 for full credit.
- 1 of 1 params have no description: `cluster_id`. Describe each one.
Already earned (5) ▾Already earned (5) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.github.benseverndev-oss/goldenmatch)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"goldenmatch": {
"command": "uvx",
"args": [
"goldenmatch"
]
}
}
}▶ Try itlive against goldenmatch-mcp-production.up.railway.app
This server has a hosted endpoint, so we can connect and list its actual tools right here. Nothing runs on your machine.