Reference & Lookup Data · Integration
Mozilla Observatory
Add Mozilla Observatory to your product for your customers, and give your AI agents governed access to it.
Embed a Mozilla Observatory integration so your product can check the HTTP security posture of a hostname and show the result to the person who can fix it. Observatory grades a site on its response headers and returns the individual tests it passed and failed, which makes it useful inside onboarding checks, security scorecards and posture dashboards. fastn handles the request, retries and result normalisation, and scans are queued and throttled deliberately so a bulk run does not hammer the service or the hostnames being scanned.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let your product scan a hostname on demand and show its grade with the tests that failed.
Re-scan on a schedule so a posture score in your product reflects the current configuration, not last quarter's.
Track score changes over time so a customer can show a header issue was actually fixed.
Queue and throttle bulk scans so checking a whole portfolio does not turn into an abuse pattern.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent scans a hostname and explains which headers are missing and what each one protects against.
An agent compares the current result with the previous scan and reports what changed.
An agent runs a scan as one step of a wider posture review, with each call logged.
Example prompt
Scan this hostname, list the failing header tests and explain the fix for each in priority order.
Set up Mozilla Observatory in 4 steps
- 01Open the Mozilla Observatory connector from your fastn dashboard.
- 02Configure which hostnames your product is allowed to scan, per tenant.
- 03Enable the scan and result-read actions your product needs.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Mozilla Observatory integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Mozilla Observatory integration without building it. Your customers connect their own Mozilla Observatory account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Mozilla Observatory update is not your on-call problem.
- One integration serves your product and your agents. The same governed Mozilla Observatory connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Google Safe Browsing
APIVoid
MxToolboxOften used alongside
Tools the same teams tend to run next to Mozilla Observatory, across other categories.
Salesforce
HubSpot
Notion
SnowflakeMozilla Observatory integration FAQ
How do I add a Mozilla Observatory integration to my product?
Enable the Mozilla Observatory connector in your fastn dashboard, then let each customer authenticate their own Mozilla Observatory account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Mozilla Observatory client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Mozilla Observatory account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Mozilla Observatory account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Mozilla Observatory integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent scans a hostname and explains which headers are missing and what each one protects against.
Who maintains the Mozilla Observatory integration?
fastn does. When Mozilla Observatory changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Mozilla Observatory lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Mozilla Observatory results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Mozilla Observatory is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Mozilla Observatory integration?
A common starting point: let your product scan a hostname on demand and show its grade with the tests that failed. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Mozilla Observatory integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Mozilla Observatory does not change your per-connector cost. You can start free with 3 connected accounts.
Add Mozilla Observatory to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.