Nomas Research

io.github.carterchenccPublished by GitHub account carterchenccv1.3.2Updated Oct 24, 2026

Parsed SEC events by CIK/CUSIP: 8-K items, Form 144, Form D, FTD. Not EDGAR HTML.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Hosted MCP server giving assistants parsed SEC event data by CIK and CUSIP: 8-K items, Form 144, Form D, FTD and more.

What you can do
  • Resolve issuers from tickers to CIK and live CUSIPs
  • Read parsed 8-K items, Form 144 proposed sales, Form D, 13D, periodic, proxy and offering filings
  • Pull FTD series by CUSIP without collapsing CUSIPs
  • Query XBRL company facts, Form 4 insider trades and 13F-by-manager data
  • All tools are read-only
When to use it
Useful when an assistant needs structured SEC filing events tied to a specific issuer or security rather than raw EDGAR HTML or ticker quotes, for example researching insider sales, late filings or failures to deliver.
Requirements
Remote Streamable HTTP endpoint at mcp.nomas.fyi; no local install. Authentication is required: either OAuth Connect or a named API key from nomas.fyi sent in the X-API-Key header. Free, Pro and API plan limits apply.
Before you install
The API key is a secret; keep it out of repositories and config files that are shared. Usage is subject to the provider's plan limits, and requests and account data go to the Nomas service.

Installation

In SourceWeft

  1. Open Nomas Research in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.carterchencc%2Fnomas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nomas-research": {
      "type": "http",
      "url": "https://mcp.nomas.fyi/mcp"
    }
  }
}

README

Nomas Research MCP

Hosted Model Context Protocol server for Nomas: parsed SEC events keyed by CIK and CUSIP — 8-K items, Form 144, Form D, FTD. Not ticker quotes. Not EDGAR HTML.

This public repo is the registry + Cursor plugin package (manifest, MCP URL, logo). It is not the Nomas product source.

What it does

Read-only tools. Tickers are reused; start with lookup_issuer (CIK + live CUSIPs). Then:

  • Mixed issuer tape: parsed 8-K items, Form 144 proposed sales, Form D, 13D, periodic, proxy, offerings
  • FTD series by CUSIP (do not collapse CUSIPs)
  • XBRL company facts, Form 4 insider trades, 13F-by-manager when those datasets are the question

Install

  1. Install Nomas Research from the Cursor Marketplace, or clone this repo and load it from ~/.cursor/plugins/local while testing.
  2. Create a named API key at nomas.fyi/AccountManagement.
  3. In Cursor, open Plugins → Configure and set Nomas API key. Do not put the key in this repo.

Manual MCP (without the plugin):

json
{  "mcpServers": {    "nomas": {      "url": "https://mcp.nomas.fyi/mcp",      "headers": { "X-API-Key": "YOUR_API_KEY" }    }  }}

Docs: nomas.fyi/research/mcp
Privacy: nomas.fyi/privacy

Free, Pro, and API plan limits on nomas.fyi still apply.

Layout

server.json                  Official MCP Registry metadata.cursor-plugin/plugin.json   Cursor marketplace manifestmcp.json                     Streamable HTTP MCP endpointassets/logo.png              Marketplace logotypeskills/nomas-sec-research    When to call which tools

Official MCP Registry

Metadata is in server.json (io.github.carterchencc/nomas). Publish with:

bash
mcp-publisher login githubmcp-publisher publish

License

MIT for this plugin package. Nomas data and the hosted server remain a Nomas service.

Source: README.md at commit 7efd7e3

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.3.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts