Add community.sapph1re-findata-mcp-http

[sapph1re]

Change Type

• Add a new server definition

Summary

Adds FinData MCP, a remote-hosted financial data server providing real-time and historical market data (stocks, crypto, forex, options, earnings, company fundamentals) via the x402 micropayment protocol ($0.01/call, no subscription required).

Server Details

• Server Name: FinData MCP
• Server ID: community.sapph1re-findata-mcp-http
• Transport: http
• Authentication: none (x402 micropayments handled automatically by compatible clients)
• Categories: search, developer-tools
• Upstream Repository: https://github.com/sapph1re/findata-mcp

Checklist

CI-enforced — your PR will fail without these

• JSON file lives at servers/community.sapph1re-findata-mcp-http.json
• Filename matches the id field exactly
• Required fields present: id, name, transport
• pnpm validate servers/community.sapph1re-findata-mcp-http.json passes
• pnpm check-conflicts passes (no duplicate IDs or aliases)
• pnpm test passes
• Every commit is signed off — git commit -s (DCO)

Reviewer quality bar

• description is one clear sentence — no marketing fluff
• At least one category from categories.json is assigned
• auth.type is consistent with how credentials are actually wired into the transport
• links.repository resolves (public repo)
• capabilities reflect what the server actually implements (tools: true, read_only_mode: true)
• platforms is ["all"] — server-side, no client-side OS dependency

Platform-managed fields — leave unset

• I did not set badges, stats, sponsored, featured
• I did not set publisher.official, publisher.verified, publisher.domain_verified
• I did not add any _platform*-prefixed keys

Trademark & branding

• No "official" / "certified" / "endorsed" wording
• Logo is own GitHub avatar (https://avatars.githubusercontent.com/u/5317413?v=4)

Notes for Reviewers

FinData MCP uses the x402 payment protocol for per-request micropayments. The auth.type: "none" reflects that no pre-configuration is needed from the user — x402-compatible MCP clients handle the payment handshake automatically. The live endpoint is on Railway and has been tested end-to-end.