Conduit

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.

Category
Visit Server

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 event edgar_first_tool_success as 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)

  1. 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.
  2. 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 via EDGAR_UA_CONTACT): Conduit/0.1 (+https://conduit.samlatino.dev) latinosammy22@gmail.com Ratify 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:

  1. No CI deploy job exists (.github/workflows/ci.yml runs verification only).
  2. No publish target: wrangler.toml sets workers_dev = false and declares no routes / custom domain, so a bare wrangler deploy has nowhere to publish.
  3. Guard script: npm run deploy (and predeploy) run scripts/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.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured