Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
SEC EDGAR insider trades (Form 4/5), 8-K events and 13F holdings as clean JSON.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http algoum https://api.algoum.de/v1/mcp --header 'Authorization: Bearer {api_key}'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"algoum": {
"url": "https://api.algoum.de/v1/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"algoum": {
"type": "http",
"url": "https://api.algoum.de/v1/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account fi4all, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 27 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.