io.github.mdfifty50-boop/domain-expertise
NPM · DOMAIN-EXPERTISE-MCP · SCANNED SEP 25
Inject deep domain knowledge into any AI agent
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 154 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability47
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 622 tokens (~69/item across 9 items; 8 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.mdfifty50-boop/domain-expertise MCP server?
io.github.mdfifty50-boop/domain-expertise runs locally as an npm package, launched with npx -y domain-expertise-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · domain-expertise-mcp
claude mcp add mdfifty50-boop-domain-expertise -- npx -y domain-expertise-mcp
{
"mcpServers": {
"mdfifty50-boop-domain-expertise": {
"command": "npx",
"args": [
"-y",
"domain-expertise-mcp"
]
}
}
} {
"servers": {
"mdfifty50-boop-domain-expertise": {
"command": "npx",
"args": [
"-y",
"domain-expertise-mcp"
]
}
}
} codex mcp add mdfifty50-boop-domain-expertise -- npx -y domain-expertise-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mdfifty50-boop-domain-expertise": {
"type": "local",
"command": [
"npx",
"-y",
"domain-expertise-mcp"
],
"enabled": true
}
}
} openclaw mcp add mdfifty50-boop-domain-expertise --command npx --arg -y --arg domain-expertise-mcp
mcp_servers:
mdfifty50-boop-domain-expertise:
command: "npx"
args: ["-y", "domain-expertise-mcp"] {
"McpServers": {
"mdfifty50-boop-domain-expertise": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"domain-expertise-mcp"
]
}
}
} assistant mcp add mdfifty50-boop-domain-expertise -t stdio -c npx -a -y domain-expertise-mcp
{
"mcpServers": {
"mdfifty50-boop-domain-expertise": {
"command": "npx",
"args": [
"-y",
"domain-expertise-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.77 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/domain-expertise-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_complexity ~80
Assess the complexity of a professional task and recommend whether it needs a generalist or specialist agent. Returns complexity score, required expertise level, and risk factors.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Professional domain |
| stakes | string | – | What is at stake if the task is done incorrectly |
| task_description | string | yes | Description of the task to assess |
No output schema declared.
No examples provided.
get_decision_tree ~98
Get a structured decision tree for a specific professional scenario. Returns step-by-step decision logic that an expert would follow.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Professional domain |
| jurisdiction | string | – | Jurisdiction for regulatory decisions |
| scenario | string | yes | The specific scenario or question to get a decision tree for (e.g., "Should I register for VAT?", "Is this transaction Sharia-compliant?", "How to classify this lease?") |
No output schema declared.
No examples provided.
get_domain_expertise ~133
Get structured professional expertise for a specific domain. Returns decision frameworks, key principles, common pitfalls, and expert-level reasoning patterns that transform a generalist AI agent into a domain specialist.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | Depth of expertise: overview (5min briefing), practitioner (working knowledge), expert (deep specialist) |
| domain | string | yes | Professional domain to get expertise for |
| focus_area | string | – | Specific sub-area to focus on (e.g., "transfer pricing" within tax, "sharia compliance" within islamic_finance) |
| region | string | – | Regional context for jurisdiction-specific knowledge |
No output schema declared.
No examples provided.
get_professional_workflow ~93
Get the standard professional workflow for a task. Returns the steps an experienced professional would follow, including quality checkpoints and common shortcuts that cause problems.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Professional domain |
| experience_level | string | – | Experience level to calibrate the workflow for |
| task | string | yes | The professional task (e.g., "financial audit", "contract review", "clinical diagnosis", "property valuation") |
No output schema declared.
No examples provided.
get_regulatory_context ~96
Get regulatory context for a domain in a specific jurisdiction. Returns applicable laws, regulatory bodies, compliance requirements, and recent changes.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Professional domain |
| jurisdiction | string | yes | Country or region code (e.g., SA, AE, KW, US, UK, EU) |
| topic | string | – | Specific regulatory topic (e.g., "anti-money laundering", "data protection", "employment contracts") |
No output schema declared.
No examples provided.
get_terminology ~76
Get professional terminology and definitions for a domain. Returns terms with definitions, usage context, and common misunderstandings.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Professional domain |
| language | string | – | Language for definitions |
| terms | array | – | Specific terms to define. If empty, returns the top 20 essential terms for the domain. |
No output schema declared.
No examples provided.
health_check ~20
Returns server health, uptime, version, and usage stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_available_domains ~20
List all available professional domains with descriptions and coverage depth.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.mdfifty50-boop/domain-expertise MCP server?
io.github.mdfifty50-boop/domain-expertise is an MCP server listed in the public MCP registry as io.github.mdfifty50-boop/domain-expertise. Inject deep domain knowledge into any AI agent. This page covers its npm package (domain-expertise-mcp).
Is the io.github.mdfifty50-boop/domain-expertise MCP server safe to use?
io.github.mdfifty50-boop/domain-expertise scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mdfifty50-boop/domain-expertise MCP server expose?
io.github.mdfifty50-boop/domain-expertise exposes 8 tools: health_check, get_domain_expertise, list_available_domains, get_decision_tree, get_terminology, and 3 more. Their descriptions and schemas cost roughly 616 tokens of context every time the server is loaded.
Is the io.github.mdfifty50-boop/domain-expertise MCP server still maintained?
io.github.mdfifty50-boop/domain-expertise is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mdfifty50-boop/domain-expertise MCP server under?
io.github.mdfifty50-boop/domain-expertise declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.