Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/ballpark

OCI · GHCR.IO/CLOUDCORPRECORDS/BALLPARK · 2 COMPONENTS

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

41 Trust /100

Last scanned (4 hours ago)

Scores higher than 47% of OCI servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 379 tokens (~75/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 41

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/ballpark@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 5 exposed · ~379 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
company_facts ~57

Structured facts about Dribba: positioning, offices, team, distinctions, clients.

NameTypeReqDescription
fieldsarray–Subset of fact keys to return (e.g. ["offices","distinctions"]). Omit for every fact.

No output schema declared.

No examples provided.

estimate_project ~69

Ballpark budget and range for an app/product, mirroring dribba.com's public calculator. Minimum project budget is €30,000.

NameTypeReqDescription
complexitystring––
designstring––
platformsarrayyesAt least one target platform.
timelinestring––

No output schema declared.

No examples provided.

list_projects ~64

List Dribba's case studies (slug, title, industry).

NameTypeReqDescription
industrystring–Case-insensitive substring match on the industry, e.g. "fintech". Omit for all industries.
limitinteger–Maximum number of case studies to return.

No output schema declared.

No examples provided.

list_services ~42

List Dribba's services with a one-line summary and URL.

NameTypeReqDescription
limitinteger–Maximum number of services to return. Omit for all of them.

No output schema declared.

No examples provided.

submit_contact_request ~147

Submit 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.

NameTypeReqDescription
budgetstring–Approximate budget range, e.g. "30-60k EUR" (optional).
companystring–Company name (optional).
emailstringyesEmail address Dribba should reply to.
messagestringyesThe inquiry, confirmed by the user.
namestringyesFull name of the person making the inquiry.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/ballpark MCP server?

io.github.CloudCorpRecords/ballpark runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/ballpark:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cloudcorprecords/ballpark

# add to Claude Code
claude mcp add cloudcorprecords-ballpark -- docker run --rm -i ghcr.io/cloudcorprecords/ballpark:0.1.0
Common questions

What is the io.github.CloudCorpRecords/ballpark MCP server?

io.github.CloudCorpRecords/ballpark is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/ballpark. Forwarding client for Dribba studio data: services, case studies, budget estimates, contact. This page covers its container image (ghcr.io/cloudcorprecords/ballpark).

Is the io.github.CloudCorpRecords/ballpark MCP server safe to use?

io.github.CloudCorpRecords/ballpark scores 41 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.CloudCorpRecords/ballpark MCP server expose?

io.github.CloudCorpRecords/ballpark exposes 5 tools: list_services, estimate_project, list_projects, company_facts, submit_contact_request. Their descriptions and schemas cost roughly 379 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/ballpark MCP server still maintained?

io.github.CloudCorpRecords/ballpark is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/ballpark MCP server under?

io.github.CloudCorpRecords/ballpark declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.