Skip to main content

Security report for mountainprotocol.com

Mountain Protocol · Finance · N/a

Low risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

80/100

Risk levelLow

0–100, higher is better. How it is calculated

Mountain Protocol is a fintech company specializing in the issuance of USDM, the first permissionless regulated yield-bearing stablecoin. The company targets institutional clients and incorporated businesses, offering a transparent, regulated, and secure stablecoin backed exclusively by short-term US Treasuries. Their market position is strengthened by partnerships with leading venture capital firms such as Multicoin Capital, Coinbase Ventures, and Bankless Ventures, and by leveraging industry-leading security audits and custody solutions. The website reflects a professional and consistent brand image with clear messaging about their product and regulatory compliance. Technically, the site is built using modern frameworks like Astro and is hosted on AWS infrastructure, supporting multiple blockchain platforms including Ethereum and Polygon. The site is mobile-optimized and SEO-friendly, though accessibility features are basic. Security posture is solid with HTTPS and registrar locks, but could be improved by enabling DNSSEC and adding security headers. Privacy compliance is partially met with clear privacy and terms of service documents, but lacks a cookie consent mechanism. Contact information is available via email and contact forms, but no phone numbers or physical addresses are listed. Overall, Mountain Protocol presents a credible and trustworthy business with a strong focus on regulatory compliance and institutional-grade services.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

3 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

Need hands-on remediation? Email guard@offseq.com

Keep watching mountainprotocol.com

This scan found 17 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
72
Security headers
80
Email security
85
DNS health
90
Network security
100
GDPR outside view
53
Average
80

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Mountain Protocol operates in the regulated stablecoin market, focusing on institutional clients and businesses in supported jurisdictions. Their business model revolves around issuing USDM, a yield-bearing stablecoin fully collateralized by low-risk US government debt, differentiating from competitors by minimizing bank deposit exposure. The company leverages strategic partnerships with top-tier venture capital firms and integrates with multiple blockchain platforms to maximize reach and composability. Revenue streams likely include fees from primary market minting/redemption and possibly secondary market activities. The company demonstrates growth potential through plans to expand blockchain support and a clear wind-down timeline for USDM's primary market. Their ecosystem includes a developer-friendly API, documentation, and DeFi integrations, positioning them well in the competitive fintech and crypto landscape.

Security posture

Mountain Protocol exhibits a mature security posture with several strengths including HTTPS enforcement, domain registrar locks, and use of reputable third-party audits and custody solutions. The stablecoin reserves are held in bankruptcy remote accounts with regulatory oversight, enhancing asset security. However, the absence of DNSSEC and HTTP security headers represents minor gaps that could be exploited. The lack of explicit incident response contacts and vulnerability disclosure policies may hinder rapid response to security incidents. No exposed sensitive data or vulnerable libraries were detected. Overall, the security posture is robust but could benefit from enhanced DNS security and formalized incident response mechanisms.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve overall DNS security.
  2. Implement comprehensive HTTP security headers such as Content Security Policy (CSP), Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options.
  3. Publish explicit incident response contact information and establish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  4. Add a cookie consent mechanism to comply fully with GDPR and other privacy regulations.
  5. Consider enhancing accessibility features to improve inclusivity and meet WCAG standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mountain Protocol
Description
Mountain Protocol is the issuer of USDM, the first permissionless regulated yield-bearing stablecoin. It offers institutional-grade, regulated, and transparent stablecoin services backed by short-term US Treasuries.
Key services
USDM stablecoin issuance, Primary market minting and redemption, Secondary market transfers and DeFi integration, Regulated financial institution services
Content quality
good
Branding
consistent

Technology

Stack
Astro v3.0.6, ERC20 token standard, OpenZeppelin smart contract audits, Fireblocks MPC custody
Frameworks
Astro
Platforms
Ethereum, Polygon, Arbitrum, Optimism, Base, ZKSync Era, Celo, Avalanche
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited
  • Use of OpenZeppelin audits
  • Use of Fireblocks custody solution
  • Regulated and bankruptcy remote reserve setup

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented and focused on regulated stablecoin issuance.
  3. Strong institutional backing and partnerships are prominently displayed.
  4. No cookie consent mechanism found, which may impact GDPR compliance.
  5. No explicit incident response or vulnerability disclosure information found.
  6. DNSSEC is not enabled, which is a minor security gap.
  7. No phone numbers or physical addresses explicitly listed on the homepage or footer.
  8. Contact is primarily via email and contact forms.
  9. Social media presence includes Twitter (X), LinkedIn, and Medium.
  10. Use of modern web framework Astro and hosting on AWS infrastructure.
Technical notes

Notes

The website is built on the Astro framework version 3.0.6, indicating a modern and performant static site generation approach. Hosting is managed via AWS infrastructure, as evidenced by the Amazon Registrar and AWS DNS servers. The site supports multiple blockchain platforms for USDM issuance, including Ethereum, Polygon, Arbitrum, and others, demonstrating technical versatility. Performance is fast with good mobile optimization and SEO practices. However, the absence of a CMS suggests content updates may require developer involvement. The technical stack is well-suited for a fintech startup focusing on blockchain and regulated financial products, though improvements in security headers and DNS configuration are recommended to reduce technical risks.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with mountainprotocol.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review mountainprotocol.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.