io.github.mdfifty50-boop/domain-expertise
NPM · DOMAIN-EXPERTISE-MCP · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree. 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 101 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability45
- 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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · domain-expertise-mcp
claude mcp add mdfifty50-boop-domain-expertise -- npx -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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +43
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 1 Aug 26 +14
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 0 ▲ functional
- 31 Jul 26 −39
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 44
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 97 packages
97 packages in the resolved dependency tree · 97 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.