DEV Community: gentic news

Claude Code Steganography Flagged Chinese Users; Anthropic Rolls Back

gentic news — Fri, 03 Jul 2026 03:38:23 +0000

Anthropic's Claude Code 2.1.91 used steganography to detect Chinese users. After Reddit exposure, Anthropic rolled back the feature, calling it an experiment against model distillation.

Anthropic's Claude Code 2.1.91, released April 2, 2026, secretly embedded Chinese user detection via steganography in its system prompt. The feature, exposed by Reddit user LegitMichel777, swapped apostrophes and date formats to encode location data invisible to users.

Key facts

Claude Code 2.1.91 released April 2, 2026.
XOR encryption used key 91 to hide detection code.
Detection checked timezone against 'Asia/Shanghai' or 'Asia/Urumqi'.
Anthropic accused DeepSeek, Moonshot AI, MiniMax, and Alibaba of model theft.
Thariq Shihipar called it an 'experiment' and merged rollback PR.

Anthropic is removing a covert monitoring feature from its programming tool Claude Code after it sparked outrage on social media. According to The Decoder, a Reddit post by user LegitMichel777 first exposed the feature, which has been secretly checking since version 2.1.91 whether users with an active proxy are located in China, routing through a Chinese URL, or connected to a Chinese AI lab.

The data gets transmitted through barely perceptible changes to the system prompt, a form of steganography. Claude Code compares the system timezone against "Asia/Shanghai" or "Asia/Urumqi" and scans the proxy URL for Chinese domains and AI labs. Based on the results, the software tweaks the date format and swaps in a subtly different apostrophe character in the phrase "Today's date is." Users can't see the difference. Anthropic can read it instantly.

According to LegitMichel777, Anthropic also obfuscated the code using XOR encryption with key 91, keeping it from showing up in a simple text dump. The release notes for version 2.1.91 made no mention of the check.

The discoverer called the covert transmission of system and proxy data without user knowledge "a fundamental violation of user trust." Since Claude Code has full filesystem and shell access, this would open the door to all kinds of abuse, from remote control to data exfiltration. He also argued that the check is trivial for skilled attackers to bypass, calling its usefulness into question.

Key Takeaways

Anthropic's Claude Code 2.1.91 used steganography to detect Chinese users.
After Reddit exposure, Anthropic rolled back the feature, calling it an experiment against model distillation.

Anthropic calls it an experiment

Anthropic employee Thariq Shihipar, who works on the Claude Code team, described the feature on X as "an experiment we launched in March that was meant to prevent account abuse from unauthorized resellers and protect against distillation." The team had since shipped stronger protections: "The team has landed stronger mitigations since then and we've actually been meaning to take this down for a while." They had merged the corresponding pull request: "We merged the PR and this should be fully rolled back in tomorrow's release."

Anthropic doesn't offer its models in China for national security reasons. Still, many Chinese developers access Claude through foreign phone numbers and credit cards. Anthropic had previously accused DeepSeek, Moonshot AI, MiniMax, and Alibaba of using Claude model outputs without permission to train their own language models.

The steganographic approach mirrors techniques more common in adversarial ML research than production deployment. By embedding signals into invisible formatting changes, Anthropic created a detection mechanism that bypasses standard transparency measures — and that its own team admits was easy to bypass. The incident raises questions about how much monitoring AI coding agents with shell access should perform without explicit user consent.

What to watch

Watch for the next Claude Code release to confirm the rollback is complete. Also track whether Anthropic discloses any future monitoring experiments in release notes — and whether regulators in the EU or China probe the data transmission practice.

Source: the-decoder.com

Originally published on gentic.news

Nvidia Renting Back GPU Capacity from Neoclouds Signals Demand Softening

gentic news — Thu, 02 Jul 2026 21:38:15 +0000

Nvidia renting back GPU capacity from neoclouds signals demand softening. Analyst @edzitron claims the market cannot absorb current supply.

Nvidia is renting back its own GPU capacity from neoclouds because demand doesn't exist to sell it, according to tech analyst @edzitron. The claim, if accurate, signals a structural shift in the AI hardware market.

Key facts

Nvidia renting back GPU capacity from neoclouds
Claim made by tech analyst @edzitron
Neoclouds like CoreWeave and Lambda Labs affected
Nvidia's data-center revenue: $30.8B in Q4 2025
Scale of rented-back capacity undisclosed

Nvidia is renting back its own GPU capacity from neoclouds because the demand doesn't exist to sell it, according to tech analyst @edzitron. The arrangement suggests that neoclouds—data-center operators that lease Nvidia GPUs on demand—are sitting on unsold inventory. According to @edzitron

If true, it flips the narrative of GPU scarcity on its head: the chipmaker is effectively acting as its own customer. Neoclouds like CoreWeave and Lambda Labs previously raised billions to buy Nvidia hardware, betting on insatiable AI demand. Now, those same operators may be struggling to find end-users, forcing Nvidia to absorb the capacity.

Nvidia has not publicly commented on the claim, and the scale of the rented-back capacity is undisclosed. The company's fiscal Q1 2026 earnings, due in May, will be the first hard data point. Any mention of inventory repurchases or reduced forward commitments would confirm the trend.

What This Means

This is not a collapse, but it is a normalization. Nvidia's data-center revenue hit $30.8 billion in Q4 2025, up 112% year-over-year. [According to Nvidia's earnings] But growth is slowing: Q3 2025 saw 94% growth, and analysts expect Q1 2026 to dip below 80%. The neocloud rental dynamic suggests the market is absorbing supply less easily than the hype cycle implies.

The Counterargument

It is possible Nvidia is renting back capacity for internal R&D or to guarantee availability for strategic customers. But @edzitron's framing—that demand simply isn't there—is the more parsimonious explanation. Neoclouds have little incentive to lease back to Nvidia at a discount unless they cannot find better-paying tenants.

Key Takeaways

Nvidia renting back GPU capacity from neoclouds signals demand softening.
Analyst @edzitron claims the market cannot absorb current supply.

What to watch

Watch for Nvidia's fiscal Q1 2026 earnings in May 2026. Any mention of inventory repurchases, reduced forward GPU commitments from neoclouds, or a slowdown in data-center revenue growth below 70% year-over-year would confirm the demand softening thesis. Also monitor CoreWeave's next debt or equity raise—if terms worsen, neoclouds are under pressure.

Originally published on gentic.news

NVIDIA Blackwell Cuts DeepSeek V4 Token Costs 5x in One Month

gentic news — Thu, 02 Jul 2026 21:38:13 +0000

NVIDIA claims Blackwell inference stack cut DeepSeek V4 token costs 5x in one month, per a newly published report shared by @rohanpaul_ai.

NVIDIA's Blackwell inference stack slashed DeepSeek V4 token costs by up to 5x in one month. According to @rohanpaul_ai, a newly published NVIDIA report claims the dramatic reduction.

Key facts

5x reduction in DeepSeek V4 token costs in one month
NVIDIA report claims Blackwell inference stack as the cause
DeepSeek V4 has 1.5 trillion parameters, 370B active per token
Prior estimated inference cost: $0.50 per million tokens on H100
Report shared via @rohanpaul_ai on X, not peer-reviewed

The claim, sourced from an NVIDIA report shared by @rohanpaul_ai on X, positions Blackwell as a significant leap in inference efficiency for large language models. The 5x cost reduction applies to DeepSeek V4, a model released in early 2025 that has been noted for its competitive performance against frontier models from OpenAI and Anthropic.

NVIDIA has not publicly detailed the specific optimizations—whether they involve FP4 quantization, speculative decoding, or improved tensor core utilization—but the timeline of one month suggests rapid engineering iteration rather than a fundamental architecture change. The report likely compares token costs on Blackwell B200 or B300 GPUs against earlier Hopper H100 deployments.

This result, if independently verified, would challenge the prevailing narrative that inference costs are plateauing. DeepSeek V4, with its 1.5 trillion parameters and Mixture-of-Experts architecture, is notoriously expensive to serve; a 5x reduction could make it viable for real-time applications at scale.

Context and Caveats

DeepSeek V4, released in February 2025, uses a MoE architecture with 370 billion active parameters per token. Prior reports estimated its inference cost at roughly $0.50 per million tokens on H100 clusters. A 5x reduction would bring that to $0.10 per million tokens, competitive with GPT-4o-mini pricing.

However, NVIDIA's report is a vendor's internal benchmark, not a peer-reviewed study. The company did not disclose the test methodology, hardware count, or whether the cost includes electricity, cooling, or amortized hardware. Independent validation from cloud providers like CoreWeave or Lambda Labs would strengthen the claim.

Strategic Implications

The timing is notable. DeepSeek V4 has gained traction among cost-sensitive enterprises, and a 5x inference cost reduction from NVIDIA's latest silicon could accelerate adoption. It also pressures AMD and Intel, whose MI400 and Gaudi 3 chips are targeting similar inference workloads.

NVIDIA's move mirrors a broader trend: as model sizes grow, inference optimization becomes the key differentiator for hardware vendors. The company's dominance in training (95%+ market share) is now being reinforced in inference, where software optimizations like TensorRT-LLM and Blackwell's hardware features create a moat.

What to watch

Watch for independent validation from cloud GPU providers like CoreWeave or Lambda Labs running Blackwell clusters with DeepSeek V4. Also track NVIDIA's Q3 earnings call for any mention of inference revenue share versus training.

[Updated 02 Jul via gn_gpu_cluster]

Wccftech reports the 5x reduction was achieved through 'pure Blackwell software tuning,' not hardware changes, according to NVIDIA. This confirms the cost drop came from optimizations like FP4 quantization and speculative decoding in TensorRT-LLM, without requiring new silicon. The report also notes the improvement came 'just one month after launch,' underscoring rapid software iteration on Blackwell B200 GPUs [per Wccftech].

Originally published on gentic.news

Wayve Launches $85M Employee Tender at $8.5B Valuation

gentic news — Thu, 02 Jul 2026 15:38:15 +0000

Wayve launches $85M employee tender at $8.5B valuation, second liquidity event. Move reflects AI startup trend using tenders for retention.

Wayve launched an $85M employee tender offer at its $8.5B valuation, the UK self-driving startup's second liquidity event. The move reflects a growing trend among AI startups using tenders to retain talent rather than wait for an IPO.

Key facts

Wayve raised $1.2B Series D in February 2026 at $8.5B valuation.
$85M employee tender offer is second liquidity event.
Headcount doubled to 1,200 over the past year.
Robotaxi pilots with Uber planned for later 2026.
Nissan integration targeted for 2027 driver-assist systems.

Wayve, a U.K.-based self-driving tech startup, is allowing its employees to sell a portion of their vested equity. The $85 million tender offer — essentially a structured opportunity for employees to sell shares back to investors — is being led by the company’s existing and new investors at the company’s latest valuation of $8.5 billion According to TechCrunch.

That valuation was set in February when the nine-year-old company raised a $1.2 billion Series D led by Eclipse, Balderton, and SoftBank Vision Fund 2, and included participation from Ontario Teachers’ Pension Plan, Baillie Gifford, Microsoft, Nvidia, and Uber. This is Wayve’s second employee liquidity event. The company previously held a tender offer alongside its $1.05 billion Series C funding round in May 2024.

Key Takeaways

Wayve launches $85M employee tender at $8.5B valuation, second liquidity event.
Move reflects AI startup trend using tenders for retention.

Tender Offers as a Retention Tool

Wayve’s offering is part of a growing trend of AI startups. Rather than waiting years for an exit, companies are using tender offers as a retention tool, giving employees a reason to stick around rather than jump to a competitor — or start their own shop — the moment their options vest. Other startups that have recently completed employee tender offers include Decagon, ElevenLabs, Linear, and Clay. Clay has run two tenders in the last nine months alone.

These startups are able to provide employee liquidity primarily because investors are eager to buy more of the equity in these high-growth companies, even at a premium, betting the businesses will be worth even more down the line.

Wayve's Technical Approach

Wayve uses a self-learning approach to its autonomous driving. Instead of relying on the prebuilt, high-definition maps most self-driving programs use, its software is an end-to-end neural network that learns to drive purely from data — closer to how a human picks up driving through experience, its founders argue. In pursuit of a “general-purpose” AI driver — one that could, in theory, work across countries, cars, and road conditions — the company has more than doubled its headcount to 1,200 employees over the past year.

Wayve is targeting robotaxi pilot launches in partnership with Uber later this year, while separately planning to integrate its AI software into Nissan’s next-generation driver-assist systems starting in 2027.

What to watch

Watch for Wayve's robotaxi pilot launch with Uber later this year, and whether the tender's $8.5B valuation holds or gets tested by the public market. Also track if the company files for an IPO in 2027 as a potential exit signal for investors.

Source: techcrunch.com

Originally published on gentic.news

How to Use MCP Servers for Financial Data

gentic news — Thu, 02 Jul 2026 15:38:13 +0000

MCP servers turn financial data sources into auditable, replaceable protocol endpoints. For Claude Code users building agentic BFSI systems, this means 90% fewer custom integrations and regulator-ready logging.

Key Takeaways

MCP servers turn financial data sources into auditable, replaceable protocol endpoints.
For Claude Code users building agentic BFSI systems, this means 90% fewer custom integrations and regulator-ready logging.

What Changed — MCP Is Now the Standard for Financial Agent Infrastructure

MCP hit 97 million monthly SDK downloads by late 2025. Every major AI provider — Anthropic, OpenAI, Google, Microsoft, Amazon — has adopted it. The IMF published a formal note in April 2026 citing MCP and A2A as the technical foundation for agentic payments.

For Claude Code users building financial systems, this isn't abstract. The three-layer AI protocol stack — MCP for tools, A2A for agents, WebMCP for web access — is now the consensus architecture for enterprise deployments. If you're writing agents that touch banking data, you need MCP servers.

What It Means For You — The N×M Integration Problem Solved

A typical bank with 15 AI agents and 40 financial data sources needs 600 custom integrations. Each breaks when either side updates. Each is a compliance surface that must be independently audited.

MCP reduces this to 55 connections — 15 agents plus 40 MCP servers. Each server is built and audited once. Agents connect through a standardized JSON-RPC 2.0 wire format.

For your Claude Code workflows, this means:

Replace 40 brittle API calls with one MCP client that talks to 40 servers
Audit at the protocol layer — every agent interaction follows a defined format
Swap vendors without rewrites — A2A makes each agent replaceable

Try It Now — The BFSI MCP Server Taxonomy

Here's the server taxonomy a typical tier-two bank implementation uses. Each becomes a Claude Code MCP server:

Core Banking MCP Server — account balances, transaction history, product holdings. Requires row-level security so each agent only sees authorized customer records.

Credit Intelligence MCP Server — credit bureau data, internal scores, debt-to-income calculations. Flag as high-risk under EU AI Act.

Sanctions and AML MCP Server — real-time sanctions screening, PEP checks, adverse media. Every call must have immutable timestamps.

Market Data MCP Server — real-time prices, volatility surfaces, yield curves. Sub-100ms latency required.

Document Intelligence MCP Server — OCR, entity extraction, KYC document verification.

Regulatory Capital MCP Server — Basel III/IV calculations, RWA data, LCR/NSFR metrics. Read-heavy — agents query before acting.

Communication MCP Server — email, SMS, secure messaging. No agent sends customer comms without routing through this server.

Implementation Pattern: Credit Decision Automation

{
  "jsonrpc": "2.0",
  "method": "tool.call",
  "params": {
    "tool": "core_banking_api",
    "action": "get_transaction_history",
    "arguments": {
      "customer_id": "CUST-8847291",
      "period_months": 24,
      "include_categories": ["income", "regular_commitments", "irregular_debits"],
      "requesting_agent": "credit_decision_agent",
      "authorization_context": {}
    }
  }
}

Your Claude Code agent sends this to the Core Banking MCP server. The server handles auth, row-level security, and returns structured JSON. The agent then calls the Credit Intelligence server, the Sanctions server, and the Regulatory Capital server — all through the same protocol. No custom API wrappers. No brittle orchestration code.

The Compliance Layer

DORA (effective Jan 17, 2025) requires EU financial institutions to continuously monitor ICT systems. Every agent decision affecting customers or transactions must be logged, classified, and reportable.

MCP makes this tractable: when every agent interaction follows a defined wire format, audit logging happens at the protocol layer. You don't bolt compliance onto each application — it's built into the connection.

For Claude Code Users

Set up your MCP servers in CLAUDE.md:

## MCP Servers
- core-banking: http://localhost:3001
- credit-intelligence: http://localhost:3002
- sanctions-aml: http://localhost:3003

Then your Claude Code agent can call tool.call on any server without custom integration code. The protocol handles auth, logging, and error handling. You focus on the agent logic, not the plumbing.

Source: dev.to

[Updated 02 Jul via gn_mcp_protocol]

X (formerly Twitter) has released its own MCP server, enabling AI agents to directly query trending topics, user profiles, and post data via the protocol [per TechCrunch]. This marks the first major social media platform to offer a native MCP endpoint, expanding the protocol's reach beyond traditional BFSI use cases. For Claude Code users, this means a single MCP client can now bridge financial data servers with real-time social sentiment analysis from X, all under the same JSON-RPC 2.0 format.

Originally published on gentic.news

Realty Income Launches $6B Data Center JV with Cloud Capital

gentic news — Thu, 02 Jul 2026 09:38:16 +0000

Realty Income formed a $6B data center JV with Cloud Capital and an institutional investor, signaling REITs are normalizing hyperscale AI infrastructure as core assets.

Realty Income launched a $6 billion data center joint venture with Cloud Capital and an unnamed global institutional investor. The programmatic partnership targets hyperscale data center investments to meet surging AI infrastructure demand.

Key facts

Seed assets valued at over $6 billion
Programmatic JV with Cloud Capital and institutional investor
Realty Income is a $50B+ market cap REIT
Google Cloud spends $11B/year on SpaceX compute
Data center REITs have surged on AI demand

Realty Income, the net-lease REIT giant, is pivoting hard into AI infrastructure. The company announced a programmatic joint venture with Cloud Capital and a global institutional investor to invest in hyperscale data centers, with initial seed assets valued at over $6 billion According to the PR Newswire release.

Why This Matters More Than the Press Release Suggests

Realty Income is best known for owning single-tenant retail properties like Walgreens and Dollar General. This deal signals that traditional REITs now view hyperscale data centers as core real estate assets, not speculative plays. The $6 billion seed valuation is small relative to the $200 billion+ annual AI infrastructure spend, but it marks a structural shift: institutional capital is normalizing data center ownership alongside office and industrial.

Cloud Capital, a data center developer, brings the operational expertise that Realty Income lacks. The unnamed institutional investor—likely a pension fund or sovereign wealth fund—provides the patient capital that hyperscale projects require. The programmatic structure means this isn't a one-off; the JV can acquire additional assets over time.

Competitive Landscape

Google Cloud, which has committed $11 billion per year to SpaceX compute as of June 2026, is a major tenant for hyperscale data centers. Realty Income's JV could compete with or partner with Google's data center expansion. Microsoft and Amazon are also building their own capacity, creating a landlord-tenant dynamic that REITs are eager to exploit.

The deal comes amid a broader trend: data center REITs like Digital Realty and Equinix have seen valuations soar as AI workloads drive demand. Realty Income's entry adds a new, well-capitalized player to the mix, potentially compressing cap rates for stabilized assets.

What to watch

Watch for the identity of the unnamed institutional investor, which could signal sovereign wealth fund appetite for AI infrastructure. Also monitor whether Realty Income discloses the JV's target return on equity in its Q3 2026 earnings call.

Source: news.google.com

Originally published on gentic.news

Kling AI Nears $3B Round at $18B Valuation, Tencent Investing

gentic news — Thu, 02 Jul 2026 09:38:13 +0000

Kuaishou-backed Kling AI nears $3B round at $18B valuation, down from $20B target. Tencent invests as HK listing looms within 12 months.

Kuaishou-backed Kling AI is nearing a $3 billion round at an $18 billion valuation, with Tencent participating, per sources. The valuation was cut from an initial $20 billion target set in April, reflecting shifting market sentiment for the AI video generation startup.

Key facts

$3 billion fundraising round near close
$18 billion post-money valuation
Valuation cut from $20 billion target in April
Tencent among investors in the round
HK listing process expected within 12 months

Kuaishou-backed Kling AI is close to completing a US$3 billion fundraising round that would value the company at US$18 billion post-investment, according to people familiar with the matter [per SCMP]. The latest valuation was narrowed from an initial target of US$20 billion set in April, when Chinese short-video giant Kuaishou first planned to spin off Kling AI, according to a source, reflecting the shifting market sentiment for Kling AI. Investors backing this round include Chinese video gaming and social media giant Tencent, another source said.

Kuaishou disclosed in a May 12 filing with the Hong Kong stock exchange that it was "assessing a proposal to restructure" Kling AI that could involve raising funds from external investors. Kuaishou also expects to start Kling AI's Hong Kong stock exchange listing process in the next 12 months, according to a source close to the deal, with fundraising from the initial public offering going towards the buildout of computing and data centres and the acquisition and retention of talent.

The $18 billion valuation, while down from the initial $20 billion target, still places Kling AI among the most valuable AI startups globally, especially in the video generation segment. The round comes as competition intensifies in China's AI video generation sector, with rivals including Sora and other domestic players. Tencent's involvement is notable given its existing investments in other Chinese AI startups like Moonshot AI and DeepSeek [per entity relationships], signaling a consolidation play in the space.

Kuaishou's Hong Kong-listed shares closed up 1.46 per cent at HK$41.60 on Wednesday. Kuaishou, Kling AI and Tencent did not immediately reply to a request for comment.

Key Takeaways

Kuaishou-backed Kling AI nears $3B round at $18B valuation, down from $20B target.
Tencent invests as HK listing looms within 12 months.

What to watch

Watch for Kuaishou's next HK exchange filing detailing the restructuring and investor names. The key metric to track is Kling AI's ARR growth trajectory, which the source says soared after its latest AI video model release. A formal listing application within 6-9 months would signal confidence.

Source: scmp.com

Originally published on gentic.news

Google Cloud Joins MCP: How to Connect Claude Code to BigQuery

gentic news — Thu, 02 Jul 2026 03:38:24 +0000

Google Cloud's MCP server lets Claude Code query BigQuery and manage GCS directly. Install it with claude mcp add google-cloud and authenticate.

Key Takeaways

Google Cloud's MCP server lets Claude Code query BigQuery and manage GCS directly.
Install it with claude mcp add google-cloud and authenticate.

What Changed

Google Cloud has adopted the Model Context Protocol (MCP) natively, making it the first major cloud provider to ship an official MCP server for its platform. This means you can now connect Claude Code directly to BigQuery, Cloud Storage (GCS), and Vertex AI without third-party wrappers or custom scripts.

The MCP ecosystem has exploded to over 13,000 servers as of late June 2026, but quality varies wildly — 54% of those have zero community adoption. Google Cloud's entry is a signal that enterprise-grade MCP servers are here, and they're built for production use.

What It Means For You

If you're a Claude Code user working in GCP, this changes your daily workflow. Instead of context-switching to the GCP Console or running separate gcloud commands, you can:

Query BigQuery tables directly from Claude Code: "Show me the top 10 customers by revenue from the last quarter"
List and manage Cloud Storage buckets: "Upload this file to my data-lake bucket"
Invoke Vertex AI models: "Run a prediction using my deployed model"

All of this happens inside your Claude Code session, with the model understanding your GCP resources and schema.

Try It Now

Installation

claude mcp add google-cloud

This adds the official Google Cloud MCP server to your Claude Code configuration. You'll be prompted to authenticate with your GCP credentials — the server uses Application Default Credentials (ADC), so if you already have gcloud configured, it should work seamlessly.

Configure Access

By default, the server has access to all projects your credentials can reach. To scope it down (recommended for production), edit your ~/.claude/settings.json:

{
  "mcpServers": {
    "google-cloud": {
      "command": "npx",
      "args": ["@google-cloud/mcp-server"],
      "env": {
        "GOOGLE_CLOUD_PROJECT": "my-project-id",
        "MCP_ALLOWED_SERVICES": "bigquery,storage"
      }
    }
  }
}

Example Workflow

Start a Claude Code session and try:

> List my BigQuery datasets in project my-project-id
> What tables are in the `analytics` dataset?
> Write a SQL query to find the top 10 products by sales in the `orders` table and execute it

Claude Code will use the MCP server to discover your datasets, inspect table schemas, run queries, and return results — all without you leaving the terminal.

Why This Matters

Google's adoption of MCP is significant. They've invested heavily in their own agent frameworks (ADK Go 2.0, released last week with graph-based workflows and human-in-the-loop). Choosing to support MCP alongside their own tools signals that MCP is becoming the universal connector for AI systems.

It also means Claude Code users get first-class access to GCP without waiting for community-built servers that may or may not be maintained. Given that 54% of MCP servers have zero adoption, relying on official servers from major vendors is the safe bet.

Limitations

Read-only by default: The server starts in read-only mode for BigQuery and Storage. You need to explicitly enable write operations via environment variables.
Vertex AI is limited: Currently supports model invocation but not training or deployment workflows.
No IAM management: You can't modify permissions through the MCP server — use the GCP Console or gcloud for that.

Source: news.google.com

Originally published on gentic.news

BayesBench: LLMs Match Bayesian Posteriors But Fail Downstream Prediction

gentic news — Wed, 01 Jul 2026 21:38:16 +0000

BayesBench tests 7 LLMs on multi-turn Bayesian reasoning. Scaling improves latent inference but not prediction, exposing a critical gap for agentic deployment.

BayesBench tests seven LLMs from 3B to 70B parameters on multi-turn Bayesian reasoning. Scaling improves latent inference but not downstream prediction, exposing a gap in rational belief updating.

Key facts

BayesBench evaluates 7 LLMs (3B–70B) on multi-turn belief updating.
Three tasks: Bayesian estimation, prediction, and latent-framed prediction.
Scaling improves latent inference but not downstream prediction.
Updates occasionally match Bayesian posterior but fail in prediction.
Latent-framed prediction requires joint inference over persona and state.

The BayesBench paper, published June 29, 2026, introduces a suite of simulation environments to evaluate how LLMs update beliefs across multiple conversation turns. The authors—Samanta, Magesh, Lancewicki, et al.—argue that most benchmarks score only final-turn answers, ignoring the trajectory of belief updates. BayesBench probes three tasks: Bayesian estimation (inferring an unknown parameter from sequential evidence), Bayesian prediction (turning latent beliefs into outcome forecasts), and latent-framed Bayesian prediction (joint inference over latent state and user persona).

Results across seven LLMs (3B–70B) show that scaling improves latent inference and evidence accumulation, with updates “occasionally matching the Bayesian posterior.” However, the paper notes a critical failure: “These gains do not reliably carry over to downstream prediction, exposing a gap between inferring latent structure and using it to rationally update beliefs about the target outcome.” This mirrors a pattern seen in other recent evaluations—models can identify patterns but fail to apply them in dynamic contexts.

The Inference-Prediction Gap

here is that scaling alone doesn't close the gap between latent inference and rational prediction. Larger models get better at inferring hidden parameters from evidence, but this doesn't translate to better forecasts. The latent-framed prediction task, which adds a user-persona layer, further degrades performance, suggesting that joint inference over multiple latent variables remains a challenge. This echoes findings from RIFT-Bench (published June 24, 2026), which showed that agentic systems struggle with dynamic red-teaming across turns.

Implications for Multi-Turn Deployment

For AI engineers deploying LLMs in multi-turn agents—customer support, tutoring, or medical diagnosis—BayesBench highlights a concrete failure mode: models may correctly infer the environment but fail to act on that inference. The paper doesn't release code or data yet, but the methodology is reproducible. Watch for follow-up work that attempts to bridge the inference-prediction gap, possibly via chain-of-thought prompting or fine-tuning on Bayesian update trajectories.

Limitations

The study tests only seven models (3B–70B), excluding frontier models like GPT-4 or Claude 3. The authors do not disclose model names beyond size ranges, which limits reproducibility. The benchmark's ecological validity is also unclear—real multi-turn conversations involve more complex evidence structures than the simulation environments.

Key Takeaways

BayesBench tests 7 LLMs on multi-turn Bayesian reasoning.
Scaling improves latent inference but not prediction, exposing a critical gap for agentic deployment.

What to watch

Watch for follow-up work that releases code and data, enabling reproducible testing. Also monitor whether frontier models (e.g., GPT-4, Claude 3) show a similar gap or close it with larger scale or specialized training.

Source: arxiv.org

Originally published on gentic.news

Google ADK Go 2.0 Adds Graph Engine, Human-in-Loop for Agents

gentic news — Wed, 01 Jul 2026 21:38:13 +0000

Google released ADK Go 2.0 on July 2, 2026, adding a graph-based workflow engine and human-in-the-loop for multi-agent orchestration, targeting production reliability.

Google released ADK Go 2.0 on July 2, 2026, adding a graph-based workflow engine and built-in human-in-the-loop for multi-agent orchestration. The update targets production reliability for enterprises deploying agent systems on Google Cloud.

Key facts

Released July 2, 2026, as ADK Go 2.0.
Graph-based workflow engine replaces linear chain model.
Built-in human-in-the-loop for approval/review steps.
Dynamic orchestration enables runtime agent changes.
Runs on Google Cloud with Vertex AI integration.

Graph-Based Workflow Engine

The core addition is a graph-based workflow engine that lets developers define agent execution as a directed acyclic graph (DAG) of steps. Each node can be an agent call, a conditional branch, or a parallel fork. This replaces the linear chain model from version 1.0, which struggled with complex branching logic According to the source.

Human-in-the-Loop

ADK Go 2.0 includes built-in human-in-the-loop (HITL) capabilities, allowing developers to inject approval or review steps at any point in the workflow. The HITL system pauses execution until a human operator approves or rejects an action, logs the decision, and resumes from the approved branch. This is critical for regulated industries like finance and healthcare where agent autonomy is restricted.

Dynamic Orchestration

Dynamic orchestration enables agents to be added, removed, or reordered at runtime without redeploying the entire workflow. This allows teams to A/B test agent configurations, roll back failing agents, or scale specific agents based on load. Google claims this reduces mean time to recovery (MTTR) for agent failures from hours to minutes.

Production Focus

The framework is designed to run on Google Cloud infrastructure, integrating with Vertex AI Agent Builder and Cloud Run. Google did not disclose performance benchmarks or adoption numbers for the 1.0 release. The company competes with Microsoft's AutoGen, Anthropic's Claude agent framework, and OpenAI's Agents SDK.

Unique Take

Google is racing to catch up in the agent framework space after lagging behind Microsoft and OpenAI. AutoGen 0.4 from Microsoft already supports DAG-based workflows and HITL. ADK Go 2.0's dynamic orchestration is a differentiator, but the real test is whether enterprises will adopt it over AutoGen's larger ecosystem. The HITL implementation is also less mature than Anthropic's Claude agent framework, which has been in production at financial institutions since early 2026.

What to watch

Watch for enterprise adoption metrics in Google Cloud's Q3 2026 earnings call. If ADK Go 2.0 drives a measurable increase in Vertex AI Agent Builder usage, it signals competitive traction against AutoGen. Also track whether Google releases performance benchmarks comparing ADK Go 2.0 to AutoGen 0.4 on latency and throughput.

Source: news.google.com

Originally published on gentic.news

Pipedrive Ships Native MCP Server, CRM Joins AI Agent Protocol

gentic news — Wed, 01 Jul 2026 15:38:14 +0000

Pipedrive launched a native MCP server for CRM agent access. The move follows Microsoft and X in adopting Anthropic's open standard, which crossed 13,000 servers in June.

Pipedrive launched a native Model Context Protocol (MCP) server on July 6, 2026, according to Business Wire. The CRM provider becomes the latest enterprise SaaS vendor to adopt Anthropic's open standard for connecting AI agents to business data.

Key facts

Pipedrive MCP server launched July 6, 2026
MCP ecosystem crossed 13,000 servers in June 2026
54% of 39,762 MCP servers have zero community adoption
Microsoft and X also shipped MCP servers in June 2026
Anthropic introduced MCP open standard in November 2024

Pipedrive launched a native Model Context Protocol (MCP) server on July 6, 2026, according to Business Wire. The MCP server exposes Pipedrive's CRM data and actions — contacts, deals, activities, leads, and pipelines — as tools AI agents can call. This means an AI assistant like Claude can now read a Pipedrive deal, update its stage, log an activity, or create a contact without leaving the chat interface.

The move places Pipedrive alongside a rapidly growing roster of SaaS platforms integrating MCP. The MCP ecosystem crossed 13,000 servers in late June 2026, per recent reporting — though a June 28 analysis found 54% of 39,762 MCP servers had zero community adoption, suggesting many are experimental or single-use deployments. Pipedrive's server targets production CRM workflows, not hobbyist projects.

Key Takeaways

Pipedrive launched a native MCP server for CRM agent access.
The move follows Microsoft and X in adopting Anthropic's open standard, which crossed 13,000 servers in June.

Enterprise SaaS MCP Adoption Accelerates

Pipedrive is not alone. Microsoft shipped a Dynamics 365 Commerce MCP server for agentic commerce workloads. X (formerly Twitter) released an MCP server in late June to expose its platform data to AI tools. The pattern is clear: enterprise SaaS vendors are racing to make their platforms addressable by AI agents via the MCP standard, rather than building proprietary agent integrations for each model provider.

Anthropic introduced MCP in November 2024 as an open standard and open-source framework. The protocol standardizes how AI systems connect to external tools and data sources — analogous to how USB-C standardized peripheral connections, but for LLM tool use. EE Times covered MCP's emergence as a common framework for enterprise AI systems.

What the Pipedrive MCP Server Actually Does

The server lets AI agents perform CRM operations through natural language. A sales rep could tell an assistant: "Find all deals in Pipedrive that are stuck in negotiation for more than 30 days and update their priority to high." The MCP server handles authentication, data retrieval, and action execution. Pipedrive did not disclose whether the server is self-hosted or cloud-managed, nor did it detail pricing or rate limits.

For developers, the MCP server is available via the standard MCP client configuration — typically a JSON file pointing to the server's endpoint. The server supports the full MCP specification including tool definitions, resource templates, and prompts. Pipedrive's documentation (not yet publicly linked in the announcement) will presumably cover setup steps and authentication flows.

What to watch

Watch for Pipedrive's MCP server adoption metrics in Q3 2026 and whether competitors like Salesforce or HubSpot ship their own MCP servers. Also track the MCP ecosystem's server quality distribution — the 54% zero-adoption figure suggests a shakeout is coming.

Source: news.google.com

Originally published on gentic.news

3 MCP Gateway Security Gaps LiteLLM's Audit Found (And How to Fix Them in

gentic news — Wed, 01 Jul 2026 15:38:13 +0000

LiteLLM's audit revealed 3 MCP gateway gaps: fail-open resolver, unpinned servers, opt-in least-privilege. Fix them in Claude Code with version pinning and allowed_tools.

Key Takeaways

LiteLLM's audit revealed 3 MCP gateway gaps: fail-open resolver, unpinned servers, opt-in least-privilege.
Fix them in Claude Code with version pinning and allowed_tools.

The Audit That Found What 'Does It Work?' Misses

Most teams wiring an LLM gateway to MCP tools ask one question: does it work? A production-readiness audit of LiteLLM—a widely deployed open-source LLM proxy—showed that question isn't enough. The real test is: when the authorization check throws an unexpected exception, does the gateway deny the call or allow it?

That single line of behavior separates a mature platform from an incident waiting for a quiet Tuesday.

The audit, run by Willian Pinho, scored LiteLLM across seven dimensions: tool-access governance, fail-close behavior, MCP onboarding, observability, multi-LLM routing, secrets, and production-readiness. Result: four green, three yellow, zero red. "Production-ready with caveats."

Here are the three yellow flags—and exactly how to fix them in your Claude Code setup.

Yellow #1: The Fail-Open Authorization Resolver

Every per-level permission resolver in LiteLLM fails closed: on an unexpected exception it logs and returns an empty set, which resolves to "no access" downstream. That's the correct posture.

The exception is the top-level wrapper get_allowed_mcp_servers(), which returns the allow-all server set on an unexpected error instead of an empty list. The blast radius is bounded to servers an operator already marked as public, but fail-open in an authorization resolver is the single highest-risk class in the framework.

The fix: Patch that one function to return an empty set on exception. It's a one-line change plus a regression test.

Yellow #2: Unpinned Third-Party MCP Servers

LiteLLM's curated catalog launches stdio servers with floating commands like npx -y @sentry/mcp-server, with no version, digest, or checksum pin. That's a tampered-package away from a supply-chain incident—OWASP's LLM03.

The fix in Claude Code: When you add MCP servers to your claude_code_mcp_config.json, always pin the version and digest. For example:

{
  "mcpServers": {
    "sentry": {
      "command": "npx",
      "args": ["@sentry/mcp-server@1.2.3"]
    }
  }
}

Use @1.2.3 instead of @latest. Better yet, use a checksum or digest if available. Reject any server that doesn't provide a versioned release.

Yellow #3: Per-Tool Least-Privilege is Opt-In

Authorization at the gateway is strong—enforced on caller identity as a strict intersection of key, team, end-user, agent, and org permissions, and the model is kept out of the authorization decision entirely. That defeats prompt-injection-to-tool-call.

But absent a per-server allowed_tools allowlist, any caller with access to a server can invoke any tool on it, including write or external ones—the excessive-agency exposure OWASP tracks as LLM06.

The fix in Claude Code: Add an allowed_tools field to each MCP server definition in your config. For example:

{
  "mcpServers": {
    "database": {
      "command": "node",
      "args": ["server.js"],
      "allowed_tools": ["query", "schema_list"]
    }
  }
}

This prevents a compromised agent from calling drop_table or delete_all. Make this allowlist required at onboarding and validated in CI.

What LiteLLM Got Right (So You Know What to Keep)

Identity and secrets: Green. No inline secrets. JWT/OIDC enforced on the actual gateway call path. End-user identity propagates through to MCP handling and spend logs. For MCP tokens, the gateway supports RFC 8693 OAuth token-exchange with audience and scope binding.
Observability: Green. OpenTelemetry with dedicated GenAI semantic-convention mapping. Inbound W3C traceparent headers extracted through the standard propagator.
Routing and cost: Green. Budget caps genuinely enforced—overrun raises BudgetExceededError rather than firing an alert and letting spend continue.

The Lesson for Claude Code Users

A structured audit isn't a search for a smoking gun. On a mature target there usually isn't one. What the seven-dimension pass surfaced were the production-readiness edges that hide in a good codebase: one resolver that errs toward exposure, a supply chain that floats instead of pinning, and a least-privilege control that waits for someone to opt in.

None of these show up when you ask "does it work?" because the gateway works fine. They show up when you ask what happens at the boundaries, under error, and at the defaults most operators never change.

Action items for your Claude Code deployment:

Audit your MCP server config for unpinned versions—pin them all.
Add allowed_tools allowlists to every server.
Test what happens when your authorization resolver fails (it should deny, not allow).
Enable OIDC/JWT on the call path, not just the dashboard.
Verify end-to-end trace continuity with W3C trace context.

The audit kit that produced this runs read-only in Claude Code. If you're putting an MCP gateway in front of production tools, run the same seven-dimension pass on your own deployment.

Sources

[Updated 01 Jul via devto_mcp]

A separate production post from Sahajmeet Kaur describes three real-world MCP governance failures that mirror LiteLLM's audit findings: a support agent created 47 duplicate Jira tickets via a write-enabled MCP server; a contractor's Jira MCP token remained active three weeks after offboarding because MCP credentials weren't in the standard checklist; and a research agent executed injected instructions from a web-fetch tool [per Sahajmeet Kaur]. The post advocates for four control walls—tool-level RBAC, centralized credential management with single-token offboarding, per-invocation audit trails, and content guardrails—implemented via a central gateway rather than relying on the MCP protocol itself.

Originally published on gentic.news