Filingpulse vs .prompts
A side-by-side look at the Filingpulse and .prompts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FilingpulseDeveloper ToolsHosted SEC EDGAR filings: Form 4 insider trades, 8-K events, S-1/IPO registrations. Read-only.38FairAuth: not declared.
.promptsDeveloper Tools.prompts, the home to all your AI prompts, everywhere you need them.38FairAuth: not declaredVerdict: choose Filingpulse for developer tools work; choose .prompts for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
FChoose Filingpulse when
- You need dedicated capabilities in the Developer Tools domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Filingpulse | . .prompts |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 38/100 · Fair | 38/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Filingpulse tools
No tool names declared yet. Check the project README from the listing page.
.prompts tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Filingpulse
No confirmed install command for Filingpulse yet — follow the setup steps linked from its listing page rather than a guessed package name.
.prompts
No confirmed install command for .prompts yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Filingpulse is categorized under Developer Tools and uses an install path we have not confirmed yet. .prompts belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Filingpulse for developer tools work and .prompts for developer tools.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Filingpulse has no declared pricing — check the project's own site. .prompts has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add filingpulse and prompts as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Filingpulse has a quality signal of 38/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. .prompts has 38/100 (Fair) with 5 views, 0 installs and 0 GitHub stars.
