io.github.treymerica1982/lead-stampede

MCPcommunitylive
v0.2.0io.github.treymerica1982UnknownUpdated 4mo agoGitHub

Find SMBs by name, city, and business type in the Lead Stampede directory via public MCP tools.

The live backend that powers Lead Stampede Agent Cards. Exposes SMB business data as tools that AI agents can call over HTTP. An Express server that implements four MCP tools: Tool | What it returns | | Name, description, industry, service area, contact info | | List of services + pricing summary | | Hours + booking URL (or phone/email fallback) | | Review count, average rating, summary | Each…

Endpoint healthlive
checked 7 days ago · 385ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.treymerica1982
LicenseUnknown
Version0.2.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface16 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

16 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

search_clientsNo description published

This tool published no description. Forge does not invent one.

get_clientNo description published

This tool published no description. Forge does not invent one.

list_business_typesNo description published

This tool published no description. Forge does not invent one.

list_citiesNo description published

This tool published no description. Forge does not invent one.

get_business_profileNo description published

This tool published no description. Forge does not invent one.

get_servicesNo description published

This tool published no description. Forge does not invent one.

get_availabilityNo description published

This tool published no description. Forge does not invent one.

get_reviewsNo description published

This tool published no description. Forge does not invent one.

search_productsNo description published

This tool published no description. Forge does not invent one.

get_product_detailsNo description published

This tool published no description. Forge does not invent one.

get_collectionNo description published

This tool published no description. Forge does not invent one.

search_inventoryNo description published

This tool published no description. Forge does not invent one.

get_vehicle_detailsNo description published

This tool published no description. Forge does not invent one.

get_specialsNo description published

This tool published no description. Forge does not invent one.

schedule_service_appointmentNo description published

This tool published no description. Forge does not invent one.

contact_salesNo description published

This tool published no description. Forge does not invent one.

0 of 16 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

The live backend that powers Lead Stampede Agent Cards. Exposes SMB business data as tools that AI agents can call over HTTP. An Express server that implements four MCP tools: Tool | What it returns | | Name, description, industry, service area, contact info | | List of services + pricing summary | | Hours + booking URL (or phone/email fallback) | | Review count, average rating, summary | Each request is authenticated via an header that maps to a row in the table in Supabase. Clients are scoped…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.