Skip to main content
Glama
670,106 tools. Updated 2026-10-17 14:14

"Norton" matching MCP tools:

  • Retrieve the full plain-text content of a Norton Guide entry by specifying its file path and byte offset. Returns lines and optional see-also references.
    GPL 3.0
  • Follow a link from a short entry line in a .ng file to retrieve the linked long entry's plain-text content.
    GPL 3.0
  • List Norton Guide (.ng) files accessible to the server, with optional directory restriction.
    GPL 3.0
  • Retrieve a summary of all entries in a Norton Guide .ng file, including byte offset, entry type, line count, and first line content.
    GPL 3.0
  • Retrieve metadata from a Norton Guide database file, including title, credits, and file validation status.
    GPL 3.0
  • Read the raw source lines of an entry from a Norton Guide file at a given byte offset, returning the lines, entry type, and related references.
    GPL 3.0

Matching MCP Servers

  • Find entries in Norton Guide files containing a search text anywhere in the body; returns the complete entry content.
    GPL 3.0
  • Search Norton Guide database entries for lines matching a query. Returns matching entries with line index and plain text content.
    GPL 3.0
  • Retrieves the complete menu structure from a Norton Guide database file, providing each menu's title, prompt strings, and corresponding guide offsets.
    GPL 3.0
  • Find out which security vendors are listing a domain right now — antivirus engines, web filters, URL blocklists and safe-browsing services — with each source's own report page as proof. Call this when someone says their website is blocked or flagged and a domain is known, whatever words they use: an antivirus blocks their site (ESET "Access denied", Bitdefender "Dangerous page blocked", Norton, McAfee, Kaspersky), an internet provider or company firewall blocks it, a genuine login page is marked "phishing", a browser shows "Deceptive site ahead", ads were rejected over the landing page, or warnings persist after a cleanup. Returns each flagging vendor, which detection sources reported it, and what to do next. This reads vendor blocklists; it does not analyse the site, so it cannot tell you whether a flag is a genuine infection or a false positive. Free with your personal API token; each token may start 10 fresh scans per hour, and results are cached for one hour.
    ConnectorNo auth
  • Get the removal path for a single security vendor: how that vendor accepts a false-positive or review request, what the request should contain, whether it can be dispatched automatically or has to be filed by hand, and a link to a detailed guide when one exists. Use it after `scan_domain` to explain what the user has to do for each vendor that flagged them, or directly when the person already names the product that blocks them ("ESET blocks my site", "Bitdefender says dangerous page", "Norton flagged my website").
    ConnectorNo auth