Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.rharper105/reportcraft

NPM · @REPORTCRAFT/MCP-SERVER

Generate Splunk dashboards, reports, and alerts from natural language. No API key required.

0 this week 70 Trust /100

Last scanned (18 hours ago)

Scores higher than 41% of npm servers

Category Monitoring and Observability

Trust breakdown (7 categories)

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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 40 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 0
    • Stability: pass → 0.97 functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 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.

  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 106 packages
Packages resolved 106
Stale 40
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~632 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
blueprintobjectyesA ReportBlueprint object (ideally with SPL generated via generate_spl)
optionsobject–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.

NameTypeReqDescription
clarificationsarray–Answered clarification questions
confirmedMappingsobject–User-confirmed field mappings (fieldId → role assignments)
dataSourceobjectyesSplunk data source configuration
fieldCatalogarrayyesArray of field definitions with id, sourceName, type, and semanticRole
intentobjectyesStructured intent from parse_intent
rawPromptstringyesThe 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.

NameTypeReqDescription
blueprintobjectyesA 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.

NameTypeReqDescription
rawPromptstringyesNatural 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.

NameTypeReqDescription
baseUrlstringyesSplunk management URL (e.g., 'https://localhost:8089' or 'https://splunk.corp.local:8089')
tokenstringyesSplunk 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.

NameTypeReqDescription
appNamestring–Splunk app to deploy into (default: 'search')
blueprintobjectyesA ReportBlueprint with SPL generated (from generate_spl)
dashboardNamestring–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.

NameTypeReqDescription
indexstring–Specific index to discover fields from. If omitted, returns all indexes with event counts.
sourcetypestring–Filter field discovery to a specific sourcetype within the index.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add rharper105-reportcraft -- npx -y @reportcraft/mcp-server
Common questions

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 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.rharper105/reportcraft MCP server?

VerifyMCP ran 15 checks on io.github.rharper105/reportcraft, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.rharper105/reportcraft: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.