Hosted MCP server/Finance

Sparks RE API MCP server

Hosted at sparks-re-api.sparksdigital-re.workers.dev·Streamable HTTP

Sparks RE API exposes real estate and compliance tools: normalize_property extracts structured property data from listing text, check_fha_compliance scans for Fair Housing Act issues across the 7 federal protected classes, calculate_investor_metrics returns cap rate, DSCR, cash-on-cash, GRM and monthly cash flow, and additional tools extract web Markdown, audit WCAG and ADA structure, fetch SEC EDGAR data, and inspect Base contracts, gas, agentic readiness and TCPA voice compliance. Paid calls use x402 micropayments on Base. The cited GitHub repository and owner account now return 404, so the live endpoint is the only current evidence for the tool list.

sparks-re-api.sparksdigital-re.workers.dev Streamable HTTP No API key; x402 micropayments on Base for paid tools Server not checked yet Reviewed 2026-11-16
About

Where it fits

Real estate investors and compliance reviewers who need property metrics, FHA scans, and related web or chain checks.

  • Extract structured facts from a messy listing.
  • Scan listing text for Fair Housing Act issues.
  • Calculate cap rate, DSCR, cash-on-cash, and GRM.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Sparks RE API as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http sparks-re-api https://sparks-re-api.sparksdigital-re.workers.dev/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://sparks-re-api.sparksdigital-re.workers.dev/mcp
Host
sparks-re-api.sparksdigital-re.workers.dev · /mcp
Transport
Streamable HTTP
Authentication
No API key; x402 micropayments on Base for paid tools
Server name
sparks-re-api
Listing type
Community or directory listing

The installer uses the server name sparks-re-api. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that sparks-re-api appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Extract structured facts from a messy listing. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Sparks RE API repositoryhttps://github.com/intellectuallyneutral/Real-estate-analysis-API-with-x402-micropayments-on-Base-L2