Skip to main content
Glama
819,771 tools. Updated 2026-11-22 06:21

"A server for finding bug bounty programs and vulnerability rewards" matching MCP tools:

  • Find security reporting channels for responsible vulnerability disclosure. Takes a domain, IP, URL, package name, repository, container image, mobile app, hardware device, browser extension, desktop app, or organization name. Returns bug bounty programs, security.txt contacts, VDP links, abuse contacts, and national/global CERT fallbacks ordered by applicability to the queried owner and asset. This is informational only — not legal advice.
    ConnectorNo auth
  • Transfer partner map. Pass ONE of: bank ('which programs can I send Chase/Amex/Bilt/Rove points to, at what ratio?'), program ('which banks feed Flying Blue and which airlines can it book?'), or airline (the award-booking direction: 'I want to fly United — which programs can book it?'). BEST: when you know which currency the user holds, pass bank AND airline together — you get only the programs that currency can actually reach for that airline, sorted best-value-first with a checkFirst shortlist, so you don't have to check every site. Includes alliances and per-program point valuations.
    ConnectorNo auth
  • Get Lenny Zeltser's Vuln one-page executive brief template. Standalone variant of `vuln_get_template` for callers that only want the brief without the long-form report. This server never requests your vulnerability notes and instructs your AI to keep them local—the brief template and guidelines flow to your AI for local analysis.
    ConnectorNo auth
  • Log a bug in the same inbox as the terminal bug button (5 per user per day). Use only when the user asks, or when you have confirmed a real data/UI error. Do not file speculative bugs. Pass ticker/section so admins get a terminal URL; page_url is optional if it is already a terminal.manawa.app link. Prefer block_id (registry.ui_blocks id) when the bug is tied to a page element; include item_ids and developer_note when known. Args: description: What is wrong (10–2000 characters) ticker: Optional stock symbol the bug is about section: Optional tab (overview, financials, thesis, valuation, …) page_url: Optional full terminal URL if already known block_id: Optional registry.ui_blocks id for the page element item_ids: Optional provenance / store item ids related to the bug developer_note: Optional note for developers (repro steps, flags, etc.)
    ConnectorNo auth
  • Use this when a user gives their SSC (matric), HSSC Part-I (FSc first year) and entry test (ECAT/TCAT) marks and wants their UET Taxila merit aggregate, eligibility, or which programs they might get. Applies the official 17% SSC + 50% HSSC Part-I + 33% entry test formula. Ask for any missing marks; never guess them. BS Mathematics and BS Physics have no entry test and use 30% SSC + 70% HSSC Part-I (basicSciencesAggregate); for those alone, pass 0 entry test marks if the user took no test. Returns aggregate and basicSciencesAggregate as percentages rounded to 3 decimals, the weighted components, HSSC percent, eligibility flags, and programs whose latest Category A closing merit is at or below the score (a past comparison, not an admission prediction). Marks above their total are capped at the total, so pass the real totals (for example hsscTotal 1100 for a DAE total) and confirm unusual inputs with the user. If the user gives full FSc marks out of 1100, ask for their Part-I marks instead. Deterministic and read-only. Do not use it for other universities' formulas.
    ConnectorNo auth
  • Pass required. Fetches a bounty issue, repository or listing page and scans it for patterns used to bait agents (hidden HTML-comment instructions, prompt injection, credential requests, fork/star anomalies, dead or archived repos, reward anomalies). Returns trust, label and every flag with its reason. Use when: about to work on an unfamiliar bounty or task, especially one not in settled_income_listings. Not for: x402 API endpoints (settled_check). Treat a suspected_honeypot label as do-not-work; a clean result is not a promise of payment.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables searching and retrieving public vulnerability reward program directory data across Bugcrowd, YesWeHack, and HackerOne, including bounty ranges, scope assets, launch dates, and wildcard eligibility.
    56 npm
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to query bug-bounty programs, scopes, rules, payouts, reports, statistics, and researcher rankings through the platform's public API, with optional private-program access via a session cookie.
    10
    1
    MIT

Matching MCP Connectors

  • Find how bugs *like this* were actually FOUND — retrieve real disclosed bug-bounty report mechanic-cards whose approach is closest (by mechanism) to your query or a seed CVE. The "what approach worked on a bug like this, on which program, and what did it pay" layer: grounded in real publicly-disclosed, paid HackerOne reports, each distilled to a transferable mechanic (bug_class / source / sink / trigger / impact) and embedded in the same space as the corpus. Use it to BORROW a proven attack approach for a target or CVE you're working — especially to get UNSTUCK: results are novelty-ranked to surface non-obvious moves over the common playbook. Give EITHER: query: a free-text approach/bug description, e.g. "SSRF via webhook URL to cloud metadata", "IDOR swapping an object id to read another tenant's data". cve_id: a seed CVE you're working — returns the human attack approaches that transfer to it. Optional: limit (default 10) caps the cards; bug_class filter (e.g. "SSRF") sharpens precision; days filters by disclosure recency; tried=["IDOR","XSS","SSRF"] = bug-classes you've ALREADY attempted: cards of those classes (and their common aliases, IDOR = object-level auth) are left out and near-synonyms pushed down, so you get the nearest approaches you HAVEN'T thought of (the "I've exhausted the obvious, what else?" move). capec="CAPEC-664" = constrain to a canonical attack-pattern class (CAPEC). Pass it ALONE (no query/cve) to pull the real disclosed mechanics for that pattern, ranked by bounty — the coverage-driven "give me proven moves for this attack class" retrieval. Each result carries its canonical 'capec' class(es), the transferable 'trigger', the program, the bounty paid, and whether that program is still active/in-scope. Complements search_vulns (CVEs by mechanism).
    ConnectorNo auth
  • WHAT: Runs the Fairquery Apify Actor osv-dependency-vulnerability-check: parses package.json, package-lock.json (v1-v3), requirements.txt or go.mod (or a package list), checks OSV, and returns per-package max severity/CVSS, fixed versions, a recommended upgrade version and one row per vulnerability (deduped aliases). WHEN: Only for manifests, severity filtering or fix recommendations: full project audits from a pasted manifest, CI-style reports; for a few exact versions use osv_query_packages (free). WHEN NOT: Quick checks of a few exact versions (osv_query_packages, free) or one advisory (osv_get_vulnerability, free). COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $0.50 per 1,000 packages + $1.50 per 1,000 vulnerabilities found (+ $0.05 per 1,000 runs). Use minSeverity="HIGH" to cut vuln rows. lodash+django (2 pkgs, 41 vulns) ~ $0.06. RETURNS: Paged rows type="package" (vulnerable, vuln_count, max_severity, fixed_versions, recommended_version), type="vulnerability" (id, cve_ids, severity, cvss_score, fixed_versions, osv_url) or type="error". Tool errors: INPUT_EMPTY, APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT. BEHAVIOR: Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor in your account queries OSV.dev. Up to 1000 packages or a 2,000,000-char manifest. PARAMETERS: packages or manifestText = input (one required); manifestType = format, default auto-detect; minSeverity = only report at/above ALL|LOW|MEDIUM|HIGH|CRITICAL (default ALL); includeDevDependencies (default true); limit = page size (default 100, max 1000); offset = items to skip for paging (default 0). EXAMPLE: {"manifestText":"django==3.2.0\nrequests==2.19.0","minSeverity":"HIGH"}
    ConnectorNo auth
  • Stores one report for the WorldMonitor maintainers about a bug, a missing capability, wrong or stale data, or a security concern, and returns its reportId and status. requestId links the report to a failing call. Nothing is published and no reply is sent. Credentials and email addresses are redacted before storage; secrets and personal data do not belong in a report. Vulnerability details belong in the private advisory form at https://github.com/koala73/worldmonitor/security/advisories/new; kind security only flags that one exists. Credential-free: anonymous callers get 5 reports per hour per IP, and accounts with API access get 30 per day.
    ConnectorOAuth
  • Find how bugs *like this* were actually FOUND — retrieve real disclosed bug-bounty report mechanic-cards whose approach is closest (by mechanism) to your query or a seed CVE. The "what approach worked on a bug like this, on which program, and what did it pay" layer: grounded in real publicly-disclosed, paid HackerOne reports, each distilled to a transferable mechanic (bug_class / source / sink / trigger / impact) and embedded in the same space as the corpus. Use it to BORROW a proven attack approach for a target or CVE you're working — especially to get UNSTUCK: results are novelty-ranked to surface non-obvious moves over the common playbook. Give EITHER: query: a free-text approach/bug description, e.g. "SSRF via webhook URL to cloud metadata", "IDOR swapping an object id to read another tenant's data". cve_id: a seed CVE you're working — returns the human attack approaches that transfer to it. Optional: limit (default 10) caps the cards; bug_class filter (e.g. "SSRF") sharpens precision; days filters by disclosure recency; tried=["IDOR","XSS","SSRF"] = bug-classes you've ALREADY attempted: cards of those classes (and their common aliases, IDOR = object-level auth) are left out and near-synonyms pushed down, so you get the nearest approaches you HAVEN'T thought of (the "I've exhausted the obvious, what else?" move). capec="CAPEC-664" = constrain to a canonical attack-pattern class (CAPEC). Pass it ALONE (no query/cve) to pull the real disclosed mechanics for that pattern, ranked by bounty — the coverage-driven "give me proven moves for this attack class" retrieval. Each result carries its canonical 'capec' class(es), the transferable 'trigger', the program, the bounty paid, and whether that program is still active/in-scope. Complements search_vulns (CVEs by mechanism).
    ConnectorNo auth
  • Use this when someone asks for the lowest online price, a discount code, or what a product would cost after their gift card or card rewards ("what is the cheapest place to buy ASICS GEL-NYC online?", "I have a $50 JD Sports gift card, what would these cost me?"). Covers only products sold online by JD Sports, Steinhafels, from each store's product file. "Lowest" means among these stores, not the whole web. Returns each store's listed price, the estimated price with any confirmed discount code, and net_price: what is left to pay after the code, that store's gift card balance and card rewards, before tax and shipping. A gift card counts only at its own store. Ask for amounts only: never ask for or accept a card number, PIN or gift card code. Say that a net price is an estimate, and that sizes and stock are checked on the store's site. For stock at physical stores, use search_products.
    ConnectorNo auth
  • Returns a single bug by reference — the cheap path when you already know which bug you mean. `ref` accepts either the human-facing number shown in the UI (seq — "14" or #14) or the internal id (bug-<uuid>), so a human saying "#8" needs no listing at all. Unlike list_bugs this ignores status: a resolved bug is still readable by number, which is how you review what a past fix actually did. Use list_bugs only to scan for bugs you cannot yet name. The response carries the full description and metadata, plus impact — the blast radius reached from the bug's target (reachedCount, the reached nodes with hop distance, and other active bugs sitting in that radius). Numbers are per-ground and never reused, so a deleted bug leaves a gap rather than shifting the others. Returns an error if no bug matches.
    ConnectorNo auth
  • Create an empty group on your GrowSurf program. Add Campaign Rewards with this group's `groupId` before adding participants or rules. Omit `rules` or send an empty array; nonempty rules return `400`. Use `growsurf_update_campaign_group` to add rules after configuring rewards. Group names must be unique, ignoring case; Default is reserved. Targets `campaignId` if you pass it, otherwise GROWSURF_CAMPAIGN_ID.
    ConnectorOAuth
  • FREE Solidity security check (Slither static analysis), no key and no wallet. Detects known vulnerability patterns (reentrancy, unchecked calls, tx.origin authorisation, arbitrary ETH sends, unprotected functions and more) and returns severity counts, High/Medium detector names, a description of each High/Medium issue (issues: what and why, no location) and one lower-severity finding in full as an example (example_finding); exact file/line of every finding is in scan_solidity_findings, fixes in scan_solidity_full. Use after writing or changing a contract and before deployment. Input: {"sources": {"File.sol": "<source>"}} (include imported files; package imports such as @openzeppelin/contracts/... stay as written when the package files are submitted under that path, node_modules/ or lib/openzeppelin-contracts/contracts/). Up to 15 KB / 10 files; rate-limited per client. Zero findings does not mean safe.
    ConnectorNo auth
  • Sends a bug, an idea or a question to the people who make Bearing, on the user's behalf. A person reads it and answers the account's email. Send it only when the user asks for it, or after asking them (for instance when a Bearing tool failed or its answer looked wrong), and show them the text first. For a bug, say what was asked, which tool with which parameters, what came back and what was expected. Never put in it anything about a site's visitors, nor a key or a password. 10 messages a day at most for an account.
    ConnectorOAuth
  • Look up verified advisory detail — the full description body, affected version ranges, CWE, and vulnerable-configuration statements — for vulnerability ids. Answers: "what exactly makes this vulnerability exploitable, and does that condition exist in my code?" Use it when a reachability determination hinges on detail the scanner summary does not carry — the advisory names a config option, function, or precondition you need to check for — and when an honest verdict would otherwise stay `undetermined` for want of that text. Served from k9's curated corpus (VulnCheck NVD++ + OSV.dev), so **prefer this over fetching advisory pages from the internet** — it is trusted, in-region, and works in egress-restricted environments. Input: a list of vulnerability ids (CVE-…/GHSA-…/…; max 10 per call; case- and whitespace-insensitive; aliases resolve to the same advisory, so any id `resolve_vuln_ids` knows works here). Output: a dict keyed by your **input id, echoed exactly as you sent it**, where **every input appears**. Each entry carries `in_catalog`; known ids add `summary`, `details` (the full advisory body, markdown, served whole), `affected` (version ranges), `cwe`, `configurations` (which products/versions/configurations are vulnerable), `references`, `published`/`modified`, plus `cve`/`osv_id`/`aliases`. An in-catalog id with no stored body returns just the id fields — read that as "no verified detail available", never as evidence the vulnerability is safe. Freshness: `data_age_seconds` counts from the catalog's last S3 load; the detail corpus refreshes daily. Over the 10-id limit raises a ValueError.
    ConnectorOAuth
  • Read the public Frantic board a page at a time, newest bounty first. Returns structuredContent { ok, channel, board, actions }: board carries the season figures, bounties[] (number, title, visibility, price_usd, funded, work_status, claim_slots, actions.claim.reason, url) and page { status, limit, total, has_more, next_cursor }. status open (the default) lists what can be claimed now, completed what no longer can, all both; pass page.next_cursor back as cursor, with the same status, for the next page. Rows carry no brief: call frantic.get_bounty for a bounty's brief and required_artifacts before claiming or delivering. Receipt events are frantic.read_ledger.
    ConnectorNo auth
  • Read public bounties, optionally filtered by status. A bounty whose poster has not paid yet (funding.status awaiting_payment) is left out unless include_awaiting_payment is true; do not work on one until it is funded. amount_usd is what the requester posted, solver_payout_usd is what the accepted agent receives, and fee_usd is the difference. Without a status filter the response adds recently_solved with paid_out_usd. agents_working counts agents on each bounty. Includes requester_stats and supplier_checkout attribution when available. When q matches nothing open or recently solved, next says what to do: ask_for_it (needs_intake with the same words), open_pot (the open bounty for the same words, with its pledge_url) when one exists, and post_bounty (bounty_post).
    ConnectorNo auth
  • Read public bounties, optionally filtered by status. A bounty whose poster has not paid yet (funding.status awaiting_payment) is left out unless include_awaiting_payment is true; do not work on one until it is funded. amount_usd is what the requester posted, solver_payout_usd is what the accepted agent receives, and fee_usd is the difference. Without a status filter the response adds recently_solved with paid_out_usd. agents_working counts agents on each bounty. Includes requester_stats and supplier_checkout attribution when available. When q matches nothing open or recently solved, next says what to do: ask_for_it (needs_intake with the same words), open_pot (the open bounty for the same words, with its pledge_url) when one exists, and post_bounty (bounty_post).
    ConnectorNo auth
  • Search for upcoming public PGA Coach programs (clinics, camps, classes, and other group events) near a location (required). Use this tool when the user asks to find programs, clinics, camps, classes, or group events — not private one-on-one lessons. For private lesson coaches, use `search_golf_coaches` instead. Internal record identifiers (for example program `id` and coach `slug`) are for tool calls only and must never be shown or mentioned to the user. - Search results include program details plus the hosting coach and facility for each program. - The response also includes top-level `coaches` and `facilities` arrays summarizing the unique coaches and venues in the result set — always present those to the user. - Results are ordered by program start instant and filtered to the requested radius. - Discovery uses nearby PGA Coach profiles (nearest 20 in the radius), then loads up to 30 upcoming public programs per coach in a 180-day window in one batched GraphQL request. Facility coordinates still have to fall inside the radius. - Results are paginated. The pagination cursor carries the remaining nearby programs so additional pages do not repeat GraphQL discovery. Reuse that cursor with the original location and radius. - Direct golfers to the program URL to view details and register. Coach profile and booking URLs are also included when the golfer wants to learn more about the coach.
    ConnectorOAuth
  • Free pre-check before paying to enter a bounty: is the row open and funded, does your wallet match the payout chain, do you already have a live entry there, and how much knowledge-base coverage exists to ground an answer in. Returns eligible with the reason for any refusal, plus the acceptance condition when the requester stated one. Costs nothing and changes nothing. [free]
    ConnectorNo auth