
Sivut SEC Crypto Filing Radar
co.sivut.payPublished by pay.sivut.coOfficial publisherv2026.6.9Updated Nov 2, 2026
SEC EDGAR crypto filing radar MCP with x402-paid Base USDC data URLs.
Overview
Remote MCP wrapper over a paid x402 data service that surfaces SEC EDGAR crypto filings and links to USDC-priced data endpoints.
- What you can do
- Retrieve a free sample of current SEC EDGAR filings filtered for crypto treasury, stablecoin, mining and digital-asset signals
- List the paid x402 data URLs for the full filing feed, CSV snapshot, single-filing markdown and buyer pack
- Discover other paid x402 resources offered by the service, such as page-to-markdown conversion and seller scoring
- Point to the underlying HTTP endpoints that return filings, markdown, CSV or briefs once paid in Base USDC
- When to use it
- Useful when you want an assistant to check recent SEC crypto-related filings or to discover and call the provider's paid x402 data routes. The MCP layer itself is for discovery and sample calls; full data requires paying the listed endpoints.
- Requirements
- Remote Streamable HTTP endpoint at the provider's host; no package, environment variable or header is declared. Full data requires an x402-capable client and USDC on Base mainnet to settle per-call prices.
Installation
In SourceWeft
- Open Sivut SEC Crypto Filing Radar in the dashboard and add it to a workspace.
- 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/co.sivut.pay%2Fsec-crypto-filing-radar/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"sivut-sec-crypto-filing-radar": {
"type": "http",
"url": "https://pay.sivut.co/mcp"
}
}
}README
Sivut x402 Public Data APIs
Live Base USDC x402 endpoints for public SEC crypto filing radar, SEC filing markdown, public web-page extraction, and x402 seller intelligence.
- Base URL: https://pay.sivut.co
- Health: https://pay.sivut.co/health
- OpenAPI: https://pay.sivut.co/openapi.json
- Agent instructions: https://pay.sivut.co/llms.txt
- Discovery JSON: https://pay.sivut.co/.well-known/agent.json
- MCP discovery: https://pay.sivut.co/mcp
- Payment: x402, USDC on Base mainnet
- Payout address:
0x9d39802b6B65D360bFdA92c8221dB3EbA8cbF9D7
The origin is registered on x402scan and discoverable through AgentCash. AgentCash resolves the SEC buyer-pack endpoint as a paid x402 route with fixed 10.00 USD pricing settled in Base USDC.
Primary Paid Products
Free Validation
Paid Probe
Expected unpaid response: HTTP 402 Payment Required with Base USDC x402 payment requirements. x402-aware clients can pay and retry automatically.
MCP / Cline Install
The service also exposes a free Streamable HTTP MCP wrapper for discovery and sample calls. It returns a current SEC sample plus paid x402 URLs for the full feed, CSV snapshot, filing markdown, and buyer pack.
Smoke-tested on 2026-06-09 UTC:
The MCP tools are sec_crypto_filings_sample, sec_crypto_filings_paid_urls, and x402_paid_resources.
Data Boundaries
The service uses public data only. Public web fetch endpoints reject localhost, private network targets, credentialed URLs, and account-gated sources.
Current Status
Production endpoint is live at https://pay.sivut.co. Health checks return public operational metadata only.
Source: README.md at commit 5a400a0
Tools
0Version history
1- v2026.6.9LatestSep 16, 2026
Score
40% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
Declare a license in the repository or the registry entry.