Overview
MCP Servers
A focused catalog of MCP surfaces I’m building and exploring. Emphasis on small, inspectable tools, versioned datasets, and audit-friendly prompts for durable AI-assisted workflows.
Active Servers
Production-ready MCP servers with verified tool surfaces and documented integration patterns.
| Server |
|---|
|
🌏
Thailand Relocation MCP
thailand-relocation
|
|
🏢
Real Estate MCP
real-estate
|
|
⚖️
Legal Research & Paralegal MCP
legal-mcp-server
|
Gathering & Building Datasets for MCP Servers
Example data assembly workflow (Real Estate domain). Emphasis: small, versioned JSON artifacts; explicit provenance; incremental enrichment. Each dataset is narrow - supports selective retrieval and keeps tool responses bounded.
Principles
- ▹Schema-first
- ▹Small artifacts
- ▹Source-backed
Integrity
- ▹Version tags (ISO)
- ▹Provenance notes
- ▹Separation raw/derived
Refresh
- ▹Event triggers
- ▹Rolling diff pass
- ▹Semantic scan
Dataset Inventory
See example research trace (parallel Exa searches & pending entries) in methodology page.
Research Steps
- Define scope & boundary (avoid over-broad composite)
- Enumerate atomic fields & normalization candidates
- Parallel authoritative source capture (official + regulatory)
- Secondary synthesis (industry reports / analyst notes)
- Annotate provenance arrays & confidence levels
- Derive helper artifacts (lookup maps, param templates)
- Version snapshot & changelog delta commit
Primary Sourcing Targets
- ▹Official regulatory portals & gazettes
- ▹Ministry / agency primary publications
- ▹Accredited education directories
- ▹Statistical bureau / macro data releases
- ▹Licensing & ownership registries
- ▹Industry body whitepapers (corroborative)
Working Notes
- ▹Keep each JSON artifact constrained: one concept cluster per file.
- ▹Record every ambiguous regulatory interpretation with rationale + date.
- ▹Separate raw fact arrays from derived scoring / ranking layers.
- ▹Prefer additive extension (append fields) over in-place mutation.
- ▹Create parameter template early to avoid hard-coded query shapes.
- ▹Automate lightweight diff lint before publishing new version hashes.
Map Your MCP Server Initiative
Send over your current constraints, target use-cases and environment. I'll respond with an initial architecture outline and sequencing approach.
