Back to blog
Product

Veille MCP updated to the 2026-07-28 spec

Josselin Liebe
Josselin Liebe

We updated the Veille MCP server to the MCP 2026-07-28 specification.

What changed

The new spec moves MCP to a stateless request/response model. Servers are easier to run on serverless and edge infrastructure, without session state to manage.

It also hardens authorization around production OAuth 2.0 / OIDC, and formalizes extensions such as MCP Apps and Tasks.

What it means for you

Same endpoint (https://mcp.veille.io/), same tools, same API key setup. You get a cleaner protocol that matches what Claude and other MCP clients are rolling out.

No action needed on your side if you already use our MCP. If you are setting it up for the first time, see the MCP docs.

Related posts

Security

Veille MCP: secure assistants with tools, not guesses

Model Context Protocol explained, why wiring Veille into Cursor or Claude improves the reliability of security decisions, and API key best practices.

Read more
Security

Disposable Email Domains List: How to Block Them

Get the latest disposable email domains list. Compare top blocklists, APIs, and code examples to protect your signups and sender reputation.

Read more
Security

Blocking Disposable Emails in OpenClaw

Add disposable email detection to any OpenClaw workflow using the Veille API. Step-by-step HTTP request setup, decision logic, and common automation patterns.

Read more