API Tool Calls

io.github.cowerxdevPublished by GitHub account cowerxdevv0.2.5Updated Oct 24, 2026

94 tools, one small door: home costs, fitness, QR, barcodes, Markdown, SEO, recalls.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP endpoint offering 94 small everyday utility tools, from home costs and fitness to QR codes, barcodes, Markdown, SEO and product recalls.

What you can do
  • Run assorted everyday calculations and lookups, such as home cost and fitness estimates
  • Generate QR codes and barcodes
  • Convert or format Markdown and handle SEO-related tasks
  • Check product recall information
  • Pick from a catalog of 94 small single-purpose tools exposed through one endpoint
When to use it
Useful when you want a single remote connection that covers many small, unrelated everyday tasks instead of installing several narrow servers. Best for occasional utility work rather than deep, specialized workflows.
Requirements
Remote streamable HTTP endpoint at apitoolcalls.com; nothing to install locally. No account is required for the free tier of 20 calls per IP per day. An optional Authorization header with a Bearer key raises the limit for existing API Tool Calls keys.
Before you install
The Authorization header carries a secret API key; keep it out of shared logs and transcripts. The free tier is capped at 20 calls per IP per day, and requests go to a third-party service, so avoid sending sensitive content in tool inputs.

Installation

In SourceWeft

  1. Open API Tool Calls in the dashboard and add it to a workspace.
  2. 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/io.github.cowerxdev%2Fapitoolcalls/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.

{
  "mcpServers": {
    "api-tool-calls": {
      "type": "http",
      "url": "https://apitoolcalls.com/mcp?tools=all"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

7
  1. v0.2.5LatestOct 15, 2026
  2. v0.2.4Oct 7, 2026
  3. v0.2.3Oct 6, 2026
  4. v0.2.2Oct 5, 2026
  5. v0.2.1Oct 4, 2026
  6. v0.2.0Oct 3, 2026
  7. v0.1.0Sep 30, 2026

Score

67% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.