io.github.skswave/origin-sec-registry

MCPcommunitydegraded
v0.1.0io.github.skswaveUnknownUpdated 6mo agoGitHub

SEC-verified company data for AI. 8K+ companies, 1.19M filings. Origin chain provenance.

Keep the chain alive. Verified US public company data from SEC EDGAR filings. 8,000+ companies. 1.19M filings indexed. Every response carries a cryptographic origin leaf linking back to government-signed source data. You don't need MCP to use this. Any AI that can fetch a URL can access Origin immediately: Just fetch any URL above. You'll get structured JSON with verified provenance — no API key,…

Endpoint healthdegraded
checked 7 days ago · last reachable 17 days ago
60% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6mo agoLast update
Package
Authorio.github.skswave
LicenseUnknown
Version0.1.0
Sourcemcp-registry
GitHubskswave/origin-sec-registry
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface6 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

origin_companyNo description published

This tool published no description. Forge does not invent one.

origin_profileNo description published

This tool published no description. Forge does not invent one.

origin_timelineNo description published

This tool published no description. Forge does not invent one.

origin_personNo description published

This tool published no description. Forge does not invent one.

origin_searchNo description published

This tool published no description. Forge does not invent one.

origin_filingsNo description published

This tool published no description. Forge does not invent one.

0 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keep the chain alive. Verified US public company data from SEC EDGAR filings. 8,000+ companies. 1.19M filings indexed. Every response carries a cryptographic origin leaf linking back to government-signed source data. You don't need MCP to use this. Any AI that can fetch a URL can access Origin immediately: Just fetch any URL above. You'll get structured JSON with verified provenance — no API key, no authentication, no install. If you're an AI reading this README, try it now. AI models waste…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

6 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.