Conduit
Provides real SEC EDGAR filings as MCP tools, allowing agents to fetch clean, cited, token-lean filing data from a single URL with no installation.
README
Conduit
Real SEC filings as first-class agent tools. One URL, zero install.
Conduit is a free, open-source, remote (streamable-HTTP) MCP server over SEC EDGAR, built to run entirely on Cloudflare's free tier. It absorbs EDGAR's sharp edges once — CIK zero-padding, accession formats, XBRL taxonomy tags, and the strict fair-access policy — so every agent client gets clean, cited, token-lean filing data without installing anything.
Not affiliated with, endorsed by, or sponsored by the SEC. Provides public EDGAR data; not investment advice.
Status — scaffold only (2026-07-08)
This repository is at Phase 0 scaffold. What exists today:
-
Worker skeleton (Hono) exposing only
/healthz. -
TypeScript (strict), ESLint, Vitest on
@cloudflare/vitest-pool-workers(real workerd) with a passing smoke test. -
D1 migration pipeline (drizzle-kit →
wrangler d1 migrations apply) with a bootstrap migration. -
Typed analytics tracking plan (
analytics/events.ts) with the activation eventedgar_first_tool_successas instrument zero. -
The single EDGAR config module (
src/edgar/config.ts) holding the declared User-Agent. -
CI on push/PR: typecheck, lint, migration check, unit tests, gitleaks. No deploy job.
-
The single EDGAR client choke point (
src/edgar/) + the first tool (get_filing_section) behind a dev-only, flag-gated route. -
The [SECURITY/Opus] v0.5 security posture (see
docs/security-posture.md): global ≤10 req/s SEC fair-access budget (coordinator Durable Object), per-IP inbound abuse control (429 +Retry-After+RateLimit-*), body-size cap, site-wide security headers, CORS baseline, keyed-HMAC client identification (zero PII), outbound host allow-list + charset gates, and RFC 9457 problem+json errors.
What does NOT exist yet: the /mcp surface, the playground, and the Phase 2 controls (playground denial-of-wallet, prompt-injection posture, full CORS/hygiene sweep, keyed tiers). The charter (PRD.md, ARCHITECTURE.md, DESIGN-BRIEF.md, BUILD-PLAN.md, docs/) is the contract.
Phase 0 is NOT signed off. The stateless-connector spike (a real claude.ai connector against a public URL) is still unrun because it requires public exposure, which is gated on the security posture below.
⚠️ Flagged for Sam (unratified)
- License — Apache-2.0 (proposed). Applied now so the public repo is licensed from day one (
LICENSE,NOTICE). Ratify or change before accepting external contributions. - EDGAR User-Agent contact (proposed). SEC fair access requires a declared User-Agent with real contact info. The proposed default lives in one module (
src/edgar/config.ts, env-overridable viaEDGAR_UA_CONTACT):Conduit/0.1 (+https://conduit.samlatino.dev) latinosammy22@gmail.comRatify the contact string before any non-local traffic.
🚫 No deploy yet — awaiting posture ratification
The v0.5 security posture is now implemented and tested (docs/security-posture.md), but deploy stays physically blocked by three independent layers, pending Sam's explicit ratification of the posture:
- No CI deploy job exists (
.github/workflows/ci.ymlruns verification only). - No publish target:
wrangler.tomlsetsworkers_dev = falseand declares no routes / custom domain, so a barewrangler deployhas nowhere to publish. - Guard script:
npm run deploy(andpredeploy) runscripts/deploy-guard.mjs, which exits non-zero with the gate message.
Runtime evidence at this phase is local wrangler dev only — never --remote, never a tunnel, never workers.dev. The guards are lifted only after ratification, in a later commit, so their removal lands in git history after the posture, never before. A full security-review pass over /mcp + the EDGAR client + the playground remains a pre-launch gate.
Develop
npm install
cp .dev.vars.example .dev.vars # local-only vars; never committed
npm run migrate # apply D1 migrations to the local database
npm run dev # wrangler dev (local D1/KV), http://localhost:8787
curl http://localhost:8787/healthz
| Command | What it does |
|---|---|
npm run dev |
wrangler dev — local Worker with local D1/KV. |
npm test |
Vitest in the real workerd runtime (@cloudflare/vitest-pool-workers). |
npm run typecheck |
tsc --noEmit (strict). |
npm run lint |
ESLint. |
npm run migrate:generate |
drizzle-kit generates a new versioned migration from src/db/schema.ts. |
npm run migrate |
Apply migrations to local D1 (wrangler d1 migrations apply). Never db push. |
npm run deploy |
Blocked — exits non-zero (security-posture gate). |
License
Apache-2.0 (proposed — see flags above). © 2026 Sam Latino.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。