Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | PagerDuty MCPWatchlist candidate | MCP Server for Splunk platformMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP PagerDuty · Publisher source ↗ | First-party MCP ecosystem:splunk-platform · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Jul 15, 2026 Package: Not documented | Repo: Not documented Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 75 GitHub stars · checked 2026-08-14T18:46:26.000Z | Not documented |
| External adoption evidence |
| Not documented |
| Client coverage | ||
| Client coverage details | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Follow only the publisher source; credential storage, scopes, and revocation remain under review. | Splunk documents encrypted token handling and platform authentication for its managed MCP server. |
| Cost | Publisher plans, API usage, infrastructure, or per-action charges may apply; MCP100 has not published a cost conclusion. | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. |
| Permissions | Exact permissions and read/write boundaries have not completed MCP100 review. | Splunk roles, capabilities, and tool-level configuration constrain searches and platform access. |
| Data handling | Candidate-specific retention, subprocess, telemetry, and model-data behavior remain review items. | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive monitoring & observability information. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Use a test account, least privilege, read-only controls where available, and explicit approval for mutations. | Search results may expose sensitive security and operational events; broad search roles should not be used. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-07-30 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-07-30T19:00:00.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →