Back to Browse

Ballpark MCP Server

Developer ToolsUse Caution4.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

Forwarding client for Dribba studio data: services, case studies, budget estimates, contact.

About

Forwarding client for Dribba studio data: services, case studies, budget estimates, contact.

Security Report

4.7
Use Caution4.7High Risk

ballpark is a small forwarding client for the public Dribba MCP remote. It needs no credentials, its only network access is to the pinned dribba.com endpoint (or a user-set override), and its argument validation matches the captured schemas. The main concern is that submit_contact_request sends an email and creates a lead on the user's behalf, and the code adds no confirmation gate of its own, relying only on the tool description. Upstream results are also passed to the model without sanitization, and the package's publisher does not obviously match the upstream company. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-ballpark": {
      "args": [
        "-y",
        "@reneturcios/ballpark"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

ballpark

A forwarding client for the published Dribba MCP remote. Dribba is a product studio; its remote MCP server exposes public studio data — its services, its case studies, a ballpark budget calculator, structured company facts, and a contact-request tool. There is no installable package for that remote, so ballpark gives it a local stdio MCP server and a small CLI: tools/list is answered locally from the verbatim live capture of the remote, and every tools/call is forwarded to the remote over streamable HTTP.

The upstream result passes through verbatim, including structuredContent and any isError flag. Failures on the way there or back are reported as an error result whose text starts with ballpark error: .

Upstream and the override

  • Upstream: https://dribba.com/mcp (pinned).
  • Override: set DRIBBA_MCP_URL to point the client at a different endpoint. This override is a reconstruction: no override is published for the remote-only original.
  • The client handshake is initialize (protocol version 2025-03-26, client ballpark / 0.1.0), then notifications/initialized, then tools/call. When the upstream issues an Mcp-Session-Id, it is honoured on every later request. Responses may be plain JSON or an SSE stream.
  • Argument validation is local: an unknown tool or malformed arguments fail before anything is forwarded. submit_contact_request is forwarded like the other tools; its captured description — which asks for explicit user confirmation of the exact name, email and message before calling — is served verbatim, and this rebuild adds no gating of its own.

Install and run

npx -y @reneturcios/ballpark mcp          # stdio MCP server
npx -y @reneturcios/ballpark --version    # 0.1.0
npx -y @reneturcios/ballpark list_services '{"limit":3}'
npx -y @reneturcios/ballpark estimate_project '{"platforms":["ios","web"],"complexity":"standard"}'
npx -y @reneturcios/ballpark list_projects '{"industry":"fintech"}'
npx -y @reneturcios/ballpark company_facts '{"fields":["offices","distinctions"]}'

Each tool subcommand takes one JSON argument string and prints the forwarded result. Exit codes: 0 on success, 1 on an error result, 2 on a usage or validation error.

MCP client config

{
  "mcpServers": {
    "ballpark": {
      "command": "npx",
      "args": ["-y", "@reneturcios/ballpark", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/ballpark                    # stdio MCP server
docker run --rm ghcr.io/cloudcorprecords/ballpark --version        # CLI

Tools

ToolWhat it does
list_servicesList Dribba's services with a one-line summary and URL.
estimate_projectBallpark budget and range for an app/product, mirroring dribba.com's public calculator. Minimum project budget is €30,000. Requires platforms.
list_projectsList Dribba's case studies (slug, title, industry).
company_factsStructured facts about Dribba: positioning, offices, team, distinctions, clients.
submit_contact_requestSubmit a real project inquiry to Dribba on behalf of the user. This sends an email and creates a lead — ONLY call it after the user has explicitly confirmed the exact name, email and message to be sent. Dribba replies within 1h. Rate-limited per client.

Development

npm install
npm run build   # tsc -> dist/
npm test        # tsx --test test/*.test.ts (fake fetch only, no network)
npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios.

Reviews

No reviews yet

Be the first to review this server!