I
io.github.tytutueh13-sudo/woo-revenue-incident-graph
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
No known CVEs
No license
Maintenance unknown
No commit data
Works with most clients
Transport: http
0 tools
Grade F
io.github.tytutueh13-sudo/woo-revenue-incident-graph is an MCP server that check WooCommerce checkout-change risk using public evidence and privacy-safe store signals. Its tool list has not been published yet over http, requires no API key, and scores 16/100 on MCPpedia's security, maintenance and efficiency rubric.
Step 1
Install in your client
Config is the same across clients - only the file and path differ.
CD
Supported in Claude Desktophttp · Node 18+
Paste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"io-github-tytutueh13-sudo-woo-revenue-incident-graph": {
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Embed in your READMEAbout badges →
[](https://mcppedia.org/s/io-github-tytutueh13-sudo-woo-revenue-incident-graph)
Read me
What io.github.tytutueh13-sudo/woo-revenue-incident-graph does
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
Test This Server
No automated test available for this server. Check the documentation for setup instructions.
Scored, not listed
Why this score
Five weighted categories - click any category to see the underlying evidence.
Score breakdown
16/100across 5 weighted dimensions
0255075100
10
−84
Security
Maintenance
Efficiency
Documentation
Compatibility
Categoriesclick a row to see evidence
Security
OSV.devNo known CVEs.
No package registry to scan.
Community
Reviews
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
How easy was setup?Did it work reliably?How was the documentation?
Sign in to write a review.
Frequently Asked Questions
- Is io.github.tytutueh13-sudo/woo-revenue-incident-graph safe to use?
- io.github.tytutueh13-sudo/woo-revenue-incident-graph has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment.
- How do I install io.github.tytutueh13-sudo/woo-revenue-incident-graph?
- io.github.tytutueh13-sudo/woo-revenue-incident-graph is a hosted remote MCP server - there is no local package to install. Configure your MCP client to connect to its endpoint (https://revenue-graph.utilityhouse.xyz/mcp/registry) instead of running it locally.
- What AI clients work with io.github.tytutueh13-sudo/woo-revenue-incident-graph?
- io.github.tytutueh13-sudo/woo-revenue-incident-graph is compatible with claude-desktop, cursor, claude-code. It uses http transport.
Related
Similar servers
Others in ecommerce / finance
Agent Trade Kit94OKX trading MCP server — connect AI agents to spot, swap, futures, options & grid bots via the Model Context Protocol.
457 3
I
io.github.WYRE-AI/alternative-payments-mcp92MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.
6
I
io.github.wyattpalm2-eng/x402-seller92Rug-check & launch radar for trading agents: composite honeypot score, EVM+Solana, keyless x402.
2 1
E
Edgartools MCP Server91Open-source SEC EDGAR toolkit — 11 tools, 7 prompts, every filing type. No API key required.
2.8k 4
MCP Security Weekly
Get CVE alerts and security updates for io.github.tytutueh13-sudo/woo-revenue-incident-graph and similar servers.
Community
Discussion
Start a conversation
Ask a question, share a tip, or report an issue.
Has anyone used this with Cursor?How do you handle auth?Any alternatives?
Sign in to join the discussion.