Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Foundry MCP server 🤝 Heimdall Heimdall is an EVM smart contract toolkit by jon becker specializing in bytecode analysis and extracting information from unverified contracts. Combining the power of foundry tools with heimdall's capabilities you can perform advanced solidity bytecode analysis. Here's an example analysis of Malicious Safe Implementation...

26,119 görüntüleme • 1 yıl önce •via X (Twitter)

10 Yorum

PraneshASP profil fotoğrafı
PraneshASP1 yıl önce

You can try it out here 👇

jon becker profil fotoğrafı
jon becker1 yıl önce

this is sick 🔥

PraneshASP profil fotoğrafı
PraneshASP1 yıl önce

Thanks for building Heimdall 🤝

KOREVERSE🌐🖤 profil fotoğrafı
KOREVERSE🌐🖤1 yıl önce

@beckerrjon Crazy tech!

Antonio Viggiano profil fotoğrafı
Antonio Viggiano1 yıl önce

@beckerrjon Really cool

PraneshASP profil fotoğrafı
PraneshASP1 yıl önce

@beckerrjon Thanks!

Xyz profil fotoğrafı
Xyz1 yıl önce

@beckerrjon this is sick

PETER d/acc profil fotoğrafı
PETER d/acc1 yıl önce

@beckerrjon Thanks 🙏🏻

Edward profil fotoğrafı
Edward1 yıl önce

@beckerrjon Whoa

Andoroid profil fotoğrafı
Andoroid1 yıl önce

@beckerrjon That's sick!

Benzer Videolar

Today, we’re pushing a major update to Edison Analysis, our data analysis agent, which is tuned for scientific research and SOTA across data analysis benchmarks. In contrast to Kosmos, which runs for 6-12 hours and produces tens of thousands of lines of code, Edison Analysis runs for seconds to minutes and is best for specific, well-defined computational tasks. It is available both on our platform under the Analysis tab, and via API, and costs only one credit per run, so it is available to users on both free and paid tiers. Edison Analysis is a modified version of the data analysis agent Kosmos uses in its trajectories. Try it out! One of the most important improvements over our previous data analysis agents has been the addition of a specialized data retrieval tool. Edison Analysis can either use this tool to access data, or can pull data down directly via API. To evaluate this tool, we ranked the most commonly used public data repositories across recent papers from BioRxiv, and created a new benchmark that measures the ability of a language agent system to retrieve raw data from those sources. Edison Analysis gets 71% on this benchmark, and we’ll be working to increase this over time. You can read more about our benchmarks in the our blog post, link below. Some features worth highlighting: 1. Edison Analysis produces a report on the analysis it runs, along with a Jupyter notebook that you can download to reproduce the analysis yourself. Every figure it produces is linked back to the specific lines of code used to produce the figure, to make it easy to reproduce. 2. It works well with both Python and R. 3. One of the best uses for Edison Analysis is to use it to retrieve datasets that you can then analyze with Kosmos. We have a bunch of major improvements to Edison Analysis coming in the next few months that we’re excited to share. In the meantime, congratulations to the team, especially Ludovico Mitchener, Jon Laurent, Conor Igoe , Alex Andonian, and many more.

Sam Rodriques

61,886 görüntüleme • 8 ay önce

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

Andrew Ng

142,010 görüntüleme • 1 yıl önce

I've built it for you!! It's an automated AI system that analyzes AI case studies (you can change the use case) to identify and document enterprise-level AI implementations. It starts by reading URLs from a CSV file and uses web scraping (either through WebLoader or Firecrawl) to extract the content from each case study. The extracted content is then sent to Claude 3.5 Sonnet, which analyzes whether the case study represents a genuine enterprise AI implementation based on specific criteria like company maturity, implementation scale, and measurable business outcomes. For each URL, the system first saves the raw content and then performs this initial qualification analysis. If Claude determines that a case study qualifies as an enterprise AI implementation, the system proceeds to generate a detailed analysis. It creates three types of reports: - an individual case study report with sections like Executive Summary, AI Strategy Analysis, and Business Impact Assessment - a cross-case analysis that identifies patterns and trends across multiple case studies - and an executive dashboard summarizing key metrics and insights. All of these reports are saved in structured formats (markdown for individual reports, JSON for cross-case analysis and dashboard) in their respective directories. If a case study doesn't qualify as an enterprise AI implementation, the system logs the reason and moves on to the next URL. The entire process is asynchronous and provides detailed terminal feedback about its progress and decisions.

Muratcan Koylan

85,319 görüntüleme • 1 yıl önce