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.

BillboardBug

MCPB · BILLBOARDBUG.MCPB

BillboardBug MCP: create and verify GPS-anchored AR billboards and deals for real businesses.

Available components

+3 this week 52 Trust /100

Last scanned (11 hours ago)

Scores higher than 84% of MCPB servers

Category Marketing and SEO

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 Security23
  • 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 were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 1308 tokens (~118/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 53% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityNo 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.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +6
    • Stability: unverified → 0.40 ▲ functional
  • 17 Oct 26 43

    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 mcpb/https://github.com/bgaut007/billboardbug-mcp/releases/download/v1.0.1/billboardbug.mcpb@1.0.1

Provenance No attestation

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

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,190 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
create_chirp ~108

Post a chirp (social post) on BillboardBug, e.g. announcing a new billboard. Returns the chirp id.

NameTypeReqDescription
imageIdstring–Blob id from upload_media (post-image)
isActiveboolean––
isMatureboolean––
parentPostIdstring–Set to comment on an existing chirp
textstring––
videoIdstring–Blob id from upload_media (post-video)

No output schema declared.

No examples provided.

create_deal ~280

Create a live billboard deal at a real location. Requires an uploaded image or video. Returns storefrontId and billboardId. Never sets featured (paid) placement.

NameTypeReqDescription
addressstringyesStreet address shown as locationDescription
altitudeMetersnumber––
businessNamestringyesExact business name (confirm with your human)
categoryIdstring–Storefront category UUID from list_categories; default ce8f8f8f-8f8f-8f8f-8f8f-8f8f8f8f8f8f (Miscellaneous)
descriptionstringyesUse only claims, prices, and hours the business provided
hours–yes"24/7" or per-day: {monday: "closed" | "24h" | {open:"09:00",close:"17:00"}, ...}
imageIdstring–Blob id from upload_media (category billboard-image). The live API requires imageId or videoId.
isEnabledboolean––
latnumberyesLatitude of the business
lngnumberyesLongitude of the business
titlestringyesDeal title, max 18 characters
videoIdstring–Blob id from upload_media (category billboard-video)

No output schema declared.

No examples provided.

generate_image ~91

Generate billboard artwork from a prompt (recommended 640x373). Returns base64 data URIs you can pass to upload_media. Prefer realistic photos.

NameTypeReqDescription
aiProviderinteger–Provider type from GET /global-config/all: 5 = Grok (default, recommended), 1 = OpenAI
heightinteger––
promptstringyes–
widthinteger––

No output schema declared.

No examples provided.

get_chirp ~28

Read a chirp back by id to verify it posted.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_deal ~47

Read a deal back by storefrontId and billboardId to verify it is live. Works without an API key.

NameTypeReqDescription
billboardIdstringyes–
storefrontIdstringyes–

No output schema declared.

No examples provided.

list_categories ~57

List storefront categories for categoryId (about 7,000). Pass nameContains to filter. Requires an API key. Default used by create_deal is Miscellaneous.

NameTypeReqDescription
maxinteger––
nameContainsstring––

No output schema declared.

No examples provided.

list_my_deals ~34

List deals owned by the API key's account.

NameTypeReqDescription
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

search_deals ~47

Search BillboardBug deals by text (min 3 characters). Requires an API key.

NameTypeReqDescription
limitinteger––
offsetinteger––
searchstringyes–

No output schema declared.

No examples provided.

update_chirp ~97

Edit an existing chirp you own.

NameTypeReqDescription
idstringyes–
imageIdstring–Blob id from upload_media (post-image)
isActiveboolean––
isMatureboolean––
parentPostIdstring–Set to comment on an existing chirp
textstring––
videoIdstring–Blob id from upload_media (post-video)

No output schema declared.

No examples provided.

update_deal ~290

Replace an existing deal (same fields as create_deal). Use isEnabled:false to take a deal down when the promotion ends.

NameTypeReqDescription
addressstringyesStreet address shown as locationDescription
altitudeMetersnumber––
billboardIdstringyes–
businessNamestringyesExact business name (confirm with your human)
categoryIdstring–Storefront category UUID from list_categories; default ce8f8f8f-8f8f-8f8f-8f8f-8f8f8f8f8f8f (Miscellaneous)
descriptionstringyesUse only claims, prices, and hours the business provided
hours–yes"24/7" or per-day: {monday: "closed" | "24h" | {open:"09:00",close:"17:00"}, ...}
imageIdstring–Blob id from upload_media (category billboard-image). The live API requires imageId or videoId.
isEnabledboolean––
latnumberyesLatitude of the business
lngnumberyesLongitude of the business
storefrontIdstringyes–
titlestringyesDeal title, max 18 characters
videoIdstring–Blob id from upload_media (category billboard-video)

No output schema declared.

No examples provided.

upload_media ~111

Upload a local image/video file (or base64 data) to BillboardBug. Use billboard-image/billboard-video for deals, post-image/post-video for chirps. Returns the blob id.

NameTypeReqDescription
base64Datastring–Base64 or data: URI content (alternative to filePath)
categorystringyes–
fileNamestring–File name to use with base64Data, e.g. billboard.jpg
filePathstring–Absolute path to a local file

No output schema declared.

No examples provided.

Install

How do I install the BillboardBug MCP server?

BillboardBug ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 983959451d426c6ded8871d07951fe64057231ea974772360792ea8d051fa42a; the commands to do that are on this page. If it does not match, do not open it.

mcpb · billboardbug.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

983959451d426c6ded8871d07951fe64057231ea974772360792ea8d051fa42a

macOS / Linux

echo "983959451d426c6ded8871d07951fe64057231ea974772360792ea8d051fa42a  billboardbug.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\billboardbug.mcpb).Hash -eq "983959451d426c6ded8871d07951fe64057231ea974772360792ea8d051fa42a"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the BillboardBug MCP server?

BillboardBug is an MCP server listed in the public MCP registry as io.github.bgaut007/billboardbug. BillboardBug MCP: create and verify GPS-anchored AR billboards and deals for real businesses. This page covers its MCPB bundle (https://github.com/bgaut007/billboardbug-mcp/releases/download/v1.0.1/billboardbug.mcpb).

Is the BillboardBug MCP server safe to use?

BillboardBug scores 52 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 BillboardBug MCP server expose?

BillboardBug exposes 11 tools: create_deal, update_deal, get_deal, list_my_deals, list_categories, and 6 more. Their descriptions and schemas cost roughly 1,190 tokens of context every time the server is loaded.

What licence is the BillboardBug MCP server under?

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

What did VerifyMCP test on the BillboardBug MCP server?

VerifyMCP ran 15 checks on BillboardBug, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about BillboardBug: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.