Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
SEC EDGAR insider trades (Form 4/5), 8-K events and 13F holdings as clean JSON.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http algoum https://api.algoum.de/v1/mcp --header 'Authorization: Bearer {api_key}'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"algoum": {
"url": "https://api.algoum.de/v1/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"algoum": {
"type": "http",
"url": "https://api.algoum.de/v1/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 fi4all 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于27天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drain unblocking, leak detection & plumbing in Varna, Bulgaria: services, prices, areas, contact
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Let your AI assistant query US financial regulatory data from SEC EDGAR – insider trades (Form 4/5), material events (8-K) and institutional holdings (13F) – through the Model Context Protocol. Ask in plain language, the assistant looks up the data for you.
Ask for what you want to know – the assistant picks the right tools for you.
Buys and sells reported by officers, directors and 10% owners – for one company or across the whole market – plus the signals derived from them: clusters of buyers and the buy/sell ratio of a company's officers.
The events a company has to disclose – leadership changes, mergers, bankruptcies, cyber incidents, earnings releases and more – as a searchable history or as the latest filings across all companies.
The quarterly portfolios of institutional investors and the aggregated picture per stock: how many funds hold it, and how many opened, increased or reduced their position.
Ticker and company lookup, the original SEC filing behind every record, and how current each data source is.
The assistant can also look up the API description itself whenever it needs more detail.
Got a question, or an idea for data you would like to see? Talk to us – we are happy to hear from you.
The API is free to use. If it is useful to you, a donation helps us keep the service running.
Create a key in the dashboard of the algoum portal – the same key you use for the REST API. Create one key per app or machine, so each one stays under your control, and add or revoke keys at any time.
Keep the key in an environment variable, or let your app prompt for it:
export ALGOUM_API_KEY='<your key>'
curl -s https://api.algoum.de/v1/mcp \
-H "Authorization: Bearer $ALGOUM_API_KEY" \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Some assistants can install the server for you – look for algoum in the MCP Registry. With APM two commands set it up for your assistants. Otherwise use the values below.
| URL | https://api.algoum.de/v1/mcp |
| Transport | Streamable HTTP |
| Authentication | Your API key as Authorization: Bearer |
Create .vscode/mcp.json in your project (or run MCP: Open User Configuration to use it in all projects). VS Code asks for the key on first start and does not store it in the file:
{
"inputs": [ { "type": "promptString", "id": "algoum-key", "description": "algoum API key", "password": true } ], "servers": { "algoum-mcp": { "type": "http", "url": "https://api.algoum.de/v1/mcp", "headers": { "Authorization": "Bearer ${input:algoum-key}" } } } }
Switch the chat to agent mode and check in the tools list that the algoum-mcp tools are enabled.
Both options work in every JetBrains IDE. Use the one for the assistant you have installed.
GitHub Copilot plugin
mcp.json. {
"servers": { "algoum-mcp": { "type": "http", "url": "https://api.algoum.de/v1/mcp", "headers": { "Authorization": "Bearer " } } } }
algoum-mcp tools are listed.JetBrains AI Assistant
{
"mcpServers": { "algoum-mcp": { "url": "https://api.algoum.de/v1/mcp", "headers": { "Authorization": "Bearer " } } } }
The key stays in the IDE's own configuration on your machine.
claude mcp add --transport http algoum-mcp https://api.algoum.de/v1/mcp \
--header "Authorization: Bearer $ALGOUM_API_KEY"
Verify with claude mcp list.
Create .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects). The key is read from the environment variable you exported in step 1, so it does not end up in the file:
{
"mcpServers": { "algoum-mcp": { "url": "https://api.algoum.de/v1/mcp", "headers": { "Authorization": "Bearer ${env:ALGOUM_API_KEY}" } } } }
Start Cursor from a shell in which ALGOUM_API_KEY is set, then check Settings → MCP that the algoum-mcp server is connected.
Add the server to ~/.copilot/mcp-config.json:
{
"mcpServers": { "algoum-mcp": { "type": "http", "url": "https://api.algoum.de/v1/mcp", "headers": { "Authorization": "Bearer " }, "tools": ["*"] } } }
Run /mcp in the CLI to see algoum-mcp connected. The file stays on your machine.
APM installs the server for the assistant you choose. Run it in your project. It reads the key from the environment variable you exported in step 1, so the key does not end up in any file:
apm marketplace add fi4all/algoum-mcp
apm install algoum-mcp@algoum-marketplace --target vscode
Replace vscode with your assistant, for example copilot, claude or cursor. apm targets lists all supported ones. Without --target, APM needs an existing assistant folder in the project.