Sites/tempo.com

Meteored Brasil

Sign in to claim

tempo.com

Meteored Brasil provides weather forecasts and news for Brazil and other parts of the world.

mediaweather-forecastingnewsmeteorologyclimate-reporting
32
AI-Readiness / 100
Level 2 · Basic Presence
91/91
Pages analyzed
0/15
Questions answered
Live
For AI agents
Visit site →

Content

AI-judged Q&A · 70% of score

22

0 of 15 buyer questions answered cleanly

Your site doesn't cover:

technicalpricingintegration
See all 15 gaps

Protocol

Technical hygiene · 30% of score

55

6 of 11 items installed

Missing:

llms.txt +3MCP card +3WebMCP +3
Install with Lattis · +9 pts

Protocol fix list

5 to ship · 6 passing

Start here

install llms.txt

Machine-readable index that routes AI agents to the pages you want them to read. We generate one for you — install at your root.

+3 pts

One-click installs

We host the heavy lifting — you ship one file or one line.

MCP server card

One JSON file at /.well-known/mcp/server-card.json tells agents you have an MCP server. Ours points at mcp.lattis.dev so Lattis handles queries for you.

+3 pts
Download server-card.json

Host at tempo.com/.well-known/mcp/server-card.json — points agents at Lattis as your MCP server.

WebMCP

Paste the widget script — that is the W3C WebMCP draft (navigator.modelContext) and the actual integration. Then also host the discovery manifest so crawlers can find your tool surface without rendering JS. Do both; the script is the spec, the manifest is just discoverability.

+3 pts

1. Runtime — paste in <head>

<script async src="https://lattis.dev/widget.js"></script>

Calls navigator.modelContext.provideContext() — the W3C WebMCP draft. Agents on the page see your tools live, scoped to tempo.com.

2. Discovery — host the manifest

Download webmcp.json

Host at tempo.com/.well-known/webmcp.json. The WebMCP spec defines no discovery mechanism, so crawlers can't see runtime registrations — this manifest closes that gap.

Paste into robots.txt

Static snippets that tell agents your policy.

Content-Signal policy

Cloudflare-launched (Sep 2025) signal in robots.txt. Declare your stance on search, ai-input, and ai-train.

+3 pts
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /

Add to tempo.com/robots.txt. Adjust values: search, ai-input, ai-train each accept yes or no.

Platform-level

Requires config or code on your side. Docs linked where useful.

Markdown content negotiation

Respond to Accept: text/markdown with plain markdown — agents pay ~80% fewer tokens. If you're on Cloudflare, it's a zone toggle.

+3 pts

Zone-level toggle if you're on Cloudflare. Non-CF: implement server-side content negotiation on Accept: text/markdown.

Cloudflare: Markdown for Agents

Already passing

robots.txtsitemap.xmlAllow major AI crawlersClean crawl rateServer-rendered contentOpenAPI spec

Content gaps

15 gaps

MCP Server

AI agents can query this site directly via MCP. Add this endpoint to Claude Code, Cursor, or any MCP client.

Endpoint

https://mcp.lattis.dev/s/tempo-com/mcp

Claude Code

claude mcp add tempo --transport http https://mcp.lattis.dev/s/tempo-com/mcp

Cursor

{
  "mcpServers": {
    "tempo": {
      "url": "https://mcp.lattis.dev/s/tempo-com/mcp"
    }
  }
}

WebMCP — runtime + discovery

1. Widget script — drop in <head>. WebMCP-capable browsers (Chrome 146+ Origin Trial) call navigator.modelContext.provideContext() via this script — that's the W3C draft and the actual integration agents care about.

<script async src="https://lattis.dev/widget.js"></script>

Renders a small "AI-indexed by Lattis" badge bottom-right. Hide with [data-lattis] { display: none !important; }.

2. Discovery manifest — host alongside the script. The WebMCP spec defines no discovery mechanism, so crawlers can't see the runtime registration. This static JSON closes the gap.

Download webmcp.json

Host at tempo.com/.well-known/webmcp.json.