SparkForge MCP Server

The SparkForge MCP Server is SparkForge's MCP interface. Its durable product source is the official website at https://sparkforge.sh/ with documentation at https://sparkforge.sh/docs. The website explicitly links https://github.com/henry-ships/sparkforge-mcp-server as the MCP source; that repository identifies SparkForge as the product, names sparkforge.sh as its homepage, and publishes the server under the MIT licence. The Smithery entry henry-ships/sparkforge is therefore not the only product evidence. It is a registry lead that resolves to an independent website and publicly inspectable source repository.

Product and operator identity

According to the provider, SparkForge bundles utility APIs for AI agents. The operator identity is represented in the reviewed primary sources as SparkForge and is technically traceable through the henry-ships GitHub organisation. The website, documentation, and repository agree on the product name, domain, and MCP project name. The reviewed sources do not establish a fuller legal company name or a personal operator identity, so none is added here. This boundary matters: the technical product identity is durable and independently verifiable, while the legal identity remains undisclosed.

Data and feature scope

The official documentation describes tools for creative media, documents, web research, and developer work. It names image generation, image resizing, meme generation, text to speech, PDF to Markdown, URL to Markdown, text summarisation, screenshots, scraping, URL metadata, domain and SSL checks, web search, QR codes, JSON validation, text differences, language detection, code review, and email verification. The provider also describes crypto prices, signals, token research, wallet analysis, and news summaries. The number of tools differs between older README wording and the current website documentation, so this entry deliberately avoids storing a fixed count as a quality promise.

Authorisation, roles, and access restrictions

The documented remote connection uses https://sparkforge.sh/api/mcp. The website presents MCP access as free to use, while individual API functions may be protected by x402 payment requirements. For the local open-source server, the repository describes wallet-based authorisation for paid calls. That requires a local signing secret, which is not stored in this catalogue. The reviewed sources do not describe organisational roles or an account-based permission model. Restrictions instead come from the MCP client, server configuration, tool input limits, and x402 settlement. A local start without a wallet may be possible according to the README, but paid calls remain unavailable or limited without the required payment setup.

Privacy, data sharing, and write access

Tool calls send inputs to the SparkForge service and may pass them to downstream providers such as model, media, search, or analysis services. The reviewed sources do not provide a complete per-tool privacy matrix. Users should therefore avoid confidential, personal, or restricted information until the relevant processing is separately checked. Results return to the MCP client and may then be forwarded by that client to an AI model. Some operations can have effects outside the client, including media generation, external API calls, and wallet analysis. Use minimal inputs, an isolated wallet, and an explicit confirmation step before actions with external consequences. This catalogue entry does not claim a complete third-party security audit.

Source quality and FAQ

The identity rests on the official product website, its documentation, and the repository linked from that website. Smithery confirms registry presence and remote deployment but is not the sole source. Smithery's verified=false value is treated as the absence of a registry badge, not as proof of a different operator. The remote endpoint is attributable through the official documentation and returned HTTP 405 during review for an unsuitable GET request, which demonstrates an active route rather than relying on an unauthenticated 401 or 403 response.

Can SparkForge run locally? The repository documents local Node operation in addition to the remote MCP access. This catalogue uses the verified remote service as the primary connection path.

What data is suitable? Non-confidential text, public webpages, and deliberately selected test data are appropriate starting points. Personal data, private documents, wallet secrets, and credentials should not be placed in tool arguments or public prompts.

Can the server write? External API calls and media or analysis operations can create effects outside the MCP client. Before such actions, the user and client should review the exact tool description, destination, and possible payment or data-sharing consequences.

MCP-compatible client for remote access. Local paid calls may require separately managed wallet authorisation according to the provider.

Add the remote MCP endpoint https://sparkforge.sh/api/mcp to the client configuration. For local operation, use the public repository and its documented Node installation. Do not store private keys in project files or catalogue fields.

npx -y mcp-remote https://sparkforge.sh/api/mcp

According to the provider, remote access is provided through the MCP endpoint. Paid local calls may require x402 wallet signatures; secret keys are not stored.

No documented role model. Access depends on client configuration, tool limits, the target API, and any required x402 payment authorisation.

Inputs are sent to SparkForge and, depending on the tool, to downstream media, model, search, or analysis providers. Results return to the MCP client and may be forwarded to its model provider.

Data sharing with external services, incomplete public privacy details, possible paid x402 calls, and external effects from API, media, or wallet functions. Avoid sensitive data and keys.