Jigwell

site.jigwellPublished by jigwell.siteOfficial publisherv0.11.1Updated Oct 31, 2026

Pay-per-call tools for AI assistants: code, data, finance, spreadsheets, media, web, time.

VerifiedStreamable HTTPWeb executableFinanceDeveloper ToolsData & Analytics

Overview

AI-generated overview

Remote MCP endpoint offering pay-per-call tools for AI assistants across code, data, finance, spreadsheets, media, web and time.

What you can do
  • The registry lists no individual tools, so capabilities are known only at a high level.
  • Per the description, the server provides pay-per-call tools grouped around code, data, finance, spreadsheets, media, web and time.
  • Each tool is billed per call rather than through a subscription, according to the provider's description.
When to use it
Consider it when an assistant needs occasional access to a mix of coding, data, finance, spreadsheet, media or web utilities and you would rather pay per use than install several separate servers.
Requirements
A remote streamable HTTP endpoint at the provider's site; no local package or runtime is needed. OAuth authentication is required, so an account with the provider is needed. No environment variables or headers are declared.
Before you install
Tools are described as pay-per-call, so usage may incur charges; check pricing and any spending limits before connecting. OAuth grants the server access tied to your account, and the specific tools, their data handling and third-party recipients are not documented in the available listing.

Installation

In SourceWeft

  1. Open Jigwell in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/site.jigwell%2Fjigwell/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "jigwell": {
      "type": "http",
      "url": "https://jigwell.site/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.11.1LatestOct 31, 2026

Score

56% 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
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.