io.github.rharper105/reportcraft
NPM · @REPORTCRAFT/MCP-SERVER · SCANNED SEP 25
Generate Splunk dashboards, reports, and alerts from natural language. No API key required.
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
- 40 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 163 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 632 tokens (~90/item across 7 items; 7 tools + 0 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "splunk_deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 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.rharper105/reportcraft MCP server?
io.github.rharper105/reportcraft runs locally as an npm package, launched with npx -y @reportcraft/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reportcraft/mcp-server
claude mcp add rharper105-reportcraft -- npx -y @reportcraft/mcp-server
{
"mcpServers": {
"rharper105-reportcraft": {
"command": "npx",
"args": [
"-y",
"@reportcraft/mcp-server"
]
}
}
} {
"servers": {
"rharper105-reportcraft": {
"command": "npx",
"args": [
"-y",
"@reportcraft/mcp-server"
]
}
}
} codex mcp add rharper105-reportcraft -- npx -y @reportcraft/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rharper105-reportcraft": {
"type": "local",
"command": [
"npx",
"-y",
"@reportcraft/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add rharper105-reportcraft --command npx --arg -y --arg @reportcraft/mcp-server
mcp_servers:
rharper105-reportcraft:
command: "npx"
args: ["-y", "@reportcraft/mcp-server"] {
"McpServers": {
"rharper105-reportcraft": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@reportcraft/mcp-server"
]
}
}
} assistant mcp add rharper105-reportcraft -t stdio -c npx -a -y @reportcraft/mcp-server
{
"mcpServers": {
"rharper105-reportcraft": {
"command": "npx",
"args": [
"-y",
"@reportcraft/mcp-server"
]
}
}
} 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 −2
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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/@reportcraft/mcp-server@0.1.1
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 109 packages
| Packages resolved | 109 |
|---|---|
| Stale | 40 |
| 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 →
export_package ~82
Generate a complete Splunk export package from a blueprint. Returns a ZIP containing Classic XML dashboard, Studio JSON, savedsearches.conf, SPL queries, field mapping, and import guide.
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint | object | yes | A ReportBlueprint object (ideally with SPL generated via generate_spl) |
| options | object | – | Export options (all default to true if omitted) |
No output schema declared.
No examples provided.
generate_blueprint ~142
Generate a complete ReportBlueprint from a structured intent, field catalog, and data source. The blueprint defines panels, layout, datasets, and field mappings for a Splunk dashboard, report, or alert.
| Name | Type | Req | Description |
|---|---|---|---|
| clarifications | array | – | Answered clarification questions |
| confirmedMappings | object | – | User-confirmed field mappings (fieldId → role assignments) |
| dataSource | object | yes | Splunk data source configuration |
| fieldCatalog | array | yes | Array of field definitions with id, sourceName, type, and semanticRole |
| intent | object | yes | Structured intent from parse_intent |
| rawPrompt | string | yes | The original natural language prompt |
No output schema declared.
No examples provided.
generate_spl ~49
Generate SPL queries for each panel in a ReportBlueprint. Takes a blueprint and returns it with generatedSpl populated on each panel.
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint | object | yes | A ReportBlueprint object from generate_blueprint |
No output schema declared.
No examples provided.
parse_intent ~75
Parse a natural language description of a Splunk dashboard, report, or alert into a structured intent. Returns audience, use case, layout preference, and time range.
| Name | Type | Req | Description |
|---|---|---|---|
| rawPrompt | string | yes | Natural language description of what the user needs (e.g., 'Failed auth monitoring with trends by hour and top risky IPs') |
No output schema declared.
No examples provided.
splunk_connect ~92
Connect to a Splunk instance via REST API. Tests the connection and returns server info. Credentials stay in-memory for this session only — never persisted.
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | yes | Splunk management URL (e.g., 'https://localhost:8089' or 'https://splunk.corp.local:8089') |
| token | string | yes | Splunk password or auth token for the admin user |
No output schema declared.
No examples provided.
splunk_deploy ~102
Deploy a generated blueprint to the connected Splunk instance. Creates the dashboard and any saved searches/alerts. Requires splunk_connect first.
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | – | Splunk app to deploy into (default: 'search') |
| blueprint | object | yes | A ReportBlueprint with SPL generated (from generate_spl) |
| dashboardName | string | – | Name for the dashboard in Splunk (lowercase, underscores). Auto-generated from blueprint title if omitted. |
No output schema declared.
No examples provided.
splunk_discover ~90
Discover the schema of a connected Splunk instance — indexes, sourcetypes, and fields. Returns structured data that feeds directly into generate_blueprint. Requires splunk_connect first.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | – | Specific index to discover fields from. If omitted, returns all indexes with event counts. |
| sourcetype | string | – | Filter field discovery to a specific sourcetype within the index. |
No output schema declared.
No examples provided.
What is the io.github.rharper105/reportcraft MCP server?
io.github.rharper105/reportcraft is an MCP server listed in the public MCP registry as io.github.rharper105/reportcraft. Generate Splunk dashboards, reports, and alerts from natural language. No API key required. This page covers its npm package (@reportcraft/mcp-server).
Is the io.github.rharper105/reportcraft MCP server safe to use?
io.github.rharper105/reportcraft scores 74 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.rharper105/reportcraft MCP server expose?
io.github.rharper105/reportcraft exposes 7 tools: parse_intent, generate_blueprint, generate_spl, export_package, splunk_connect, and 2 more. Their descriptions and schemas cost roughly 632 tokens of context every time the server is loaded.
Is the io.github.rharper105/reportcraft MCP server still maintained?
io.github.rharper105/reportcraft 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.