ec-pulse
v0.1.0EC Pulse tools for Japanese e-commerce product data, price monitoring, research, consumer insights, and opportunity discovery.
By EC Pulse API0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 4 skill or MCP entries
- Source updated
- Oct 10, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install ec-pulse for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install ec-pulse@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/shunai394-hash/ec-pulse-apiClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/ec-pulse/.
Plugin files
├── .claude-plugin/plugin.json├── skills/ec-api-usage/SKILL.md├── skills/ec-market-research/SKILL.md├── skills/ec-price-monitoring/SKILL.md└── .mcp.json
Included Skills3
Inspect EC Pulse API account usage, credits, and plan limits. Use when the user asks about EC Pulse API usage, remaining credits, or account status.
Research Japanese e-commerce products, competitors, customer pain points, pricing, and product opportunities using EC Pulse. Use when the user asks for product research, competitor analysis, market signals, or opportunity discovery.
Create and analyze EC Pulse price monitors for Japanese e-commerce products. Use when the user wants price tracking, price history, alerts, or opportunity signals.
MCP servers1
- command
- python3
- args
- ${CLAUDE_PLUGIN_ROOT}/server.py
- env.EC_PULSE_API_KEY
- ${EC_PULSE_API_KEY}
- env.EC_PULSE_API_BASE_URL
- ${EC_PULSE_API_BASE_URL:-https://ec-pulse-api.vercel.app}
- env.EC_PULSE_REQUIRE_REQUEST_SIGNATURE
- ${EC_PULSE_REQUIRE_REQUEST_SIGNATURE:-false}
MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.
Plugin manifests1
{
"name": "ec-pulse",
"description": "EC Pulse tools for Japanese e-commerce product data, price monitoring, research, consumer insights, and opportunity discovery.",
"version": "0.1.0",
"author": {
"name": "EC Pulse API"
},
"homepage": "https://ec-pulse-api.vercel.app",
"repository": "https://github.com/shunai394-hash/ec-pulse-api",
"keywords": [
"ecommerce",
"japan",
"product-research",
"price-monitoring",
"market-research",
"commerce"
],
"mcpServers": "./.mcp.json"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[ec-pulse on Agent Plugins Marketplace](https://pluginsmp.com/plugins/ec-pulse)