@sedis/mcp
OfficialRelated Servers
Alternatives to @sedis/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables natural-language queries over SEC EDGAR filings and live market data, providing hybrid retrieval with reranking for company snapshots, quotes, fundamentals, and macro indicators.MIT

RiseUp MCP Serverofficial
AlicenseAqualityCmaintenanceMCP server for programmatic read-only access to RiseUp cashflow data, allowing AI assistants to retrieve budget information via natural language.2244 npm27MIT- AlicenseAqualityBmaintenanceMCP server that lets an LLM read official SEC financial data, tracing every number back to a specific SEC filing, US-GAAP tag, and filing date.4MIT
- AlicenseCqualityBmaintenanceMCP server for accessing SEC EDGAR filings. Connects AI assistants to company filings, financial statements, and insider trading data with exact numeric precision.21523 PyPI363AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceMCP server for Swedish company data. Enables AI agents to lookup companies, analyze financials, assess health, screen compliance, and get industry stats.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceHosted MCP server that gives AI agents real-time access to SEC EDGAR filings search, 10-K/8-K reading, XBRL financial facts, and insider-trade (Form 4) alerts.14 npm1MIT
TDQS
Scored across 14 tools
Most tools target clearly distinct resources and steps; the two closest pairs (bolagsanalys_get_data vs bolagsanalys_search_data, and list_jamforelseobjekt vs list_reference_zones) are explicitly differentiated in their descriptions. There is still mild overlap in purpose between the two data-fetch tools, so an agent must read carefully to pick the right one.
Strong, predictable verb_noun pattern within each domain prefix (fastighetsbenchmark_* and bolagsanalys_*), and the two session tools (set_session/clear_session) are clean and readable. The only deviation is that session tools don't share a domain prefix, but they're a distinct cross-cutting concern so this is a minor issue.
14 tools split across two coherent domains (real-estate benchmarking and company analysis) plus session handling is well-scoped. Each tool earns its place as a distinct step in the documented flows, with no redundant or trivial tools.
Both domains have complete read paths: reference lookups, parameter discovery, object search, and terminal data fetches, plus session lifecycle management. The main gap is the absence of write operations (e.g. creating/editing Samlingar or zones), which is acknowledged as intentional in the descriptions.