Sato Hub
MCP

Tenderly MCP

Official Tenderly MCP: gasless EVM transaction simulation, tracing, and contract inspection across 100+ networks.

  • Sato Score25
  • ChainsMultichain
ActiveSelf-Reported

Tenderly MCP is a MCP server by Tenderly, with no code activity tracked. Sato Score 25/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Tenderly MCP →

No code activity tracked

Listed from tenderly.co on 2026-07-13. Install: not attempted. Evidence →

Next step

Watch Tenderly MCP

One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on https://mcp.tenderly.co/mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Tenderly's MCP server exposes 59 tools covering virtual test environments, transaction simulation, tracing, contract inspection, and network discovery across 100+ EVM networks, including decoded call traces, events, state changes, and balance diffs. Requires a Tenderly account with at least one project; access is via OAuth 2.0 (WorkOS). An agent builder plugs it in to let an agent simulate and debug on-chain transactions without spending gas before execution.

Sato Score

25/100· Low

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
8/35
Code transparency
0/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
11/15
Independent verification
0/10

Evidence — listed vs checked · what the words mean

Listed from tenderly.co on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reporteddocs.tenderly.coas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedtenderly.coas of 2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reporteddocs.tenderly.coas of 2026-07-20
MCP endpoint answersanswered, but declined an anonymous probeobservedmcp.tenderly.co2026-10-15
Daily check record0 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Deploys asHosted API (OAuth 2.0 via Claude Connectors)confidence 0.80self-reporteddocs.tenderly.coas of 2026-07-14
Works withClaude Code, Claude.ai, Claude Desktop, Cursor, VS Codeconfidence 0.90self-reporteddocs.tenderly.coas of 2026-07-14
Sato Score25/100 (Low)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: Hosted MCP endpoint (no local install)

claude mcp add tenderly --transport http https://mcp.tenderly.co/mcp
{"mcpServers": {"tenderly": {"type": "streamable-http", "url": "https://mcp.tenderly.co/mcp"}}}

You supply: Tenderly account with at least one project; OAuth 2.0 login on connection (no API keys in config)

Add to CursorAdd to VS Code
claude mcp add --transport http satohub-tenderly-mcp https://mcp.tenderly.co/mcp

A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-07-20. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-17

0%of 45 checks since 2026-09-01 succeeded
Currently unreachable from our probe for 23 days
Succeeded
0
Failed
91
Their error
22
Unattributed
69

State changed on 2026-09-01 (unclear → failing), 2026-09-23 (failing → unreachable from our probe).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
0%
7-day rolling; unattributable days are gaps · 13/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
25
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Skills that target this — 1, with disclosures

Onchain Verify TransactionClawHub · dougalcantara

816 installs

Verify an EVM transaction's calldata via Tenderly before signing. Confirms which tokens move, in what amounts, and to which addresses. Designed to be called...

no disclosure flags from the static scan

Disclosures describe what a skill declares and does; they are not safety verdicts. All skills →

Details

Chains
Multichain
Agent types
MCP Server, Infrastructure
Open source
Unknown
Deploys as
Hosted API (OAuth 2.0 via Claude Connectors)
Works with
Claude Code, Claude.ai, Claude Desktop, Cursor, VS Code
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#evm#simulation#tracing#debugging#mcp
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Tenderly MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 20, 2026
    Edited: mcp endpoint url
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 18, 2026
    Sato Hub began tracking this listing
  5. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  6. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Tenderly MCP

Is Tenderly MCP open source?
Unknown. Sato Hub has not found a public repository or a license statement for Tenderly MCP as of 2026-10-15.
Which chains does Tenderly MCP support?
Tenderly MCP lists support for Multichain as of 2026-10-15.
Is Tenderly MCP still maintained?
Sato Hub tracks no commit or release for Tenderly MCP; it cannot say whether it is maintained.
How do I install or run Tenderly MCP?
Hosted MCP endpoint (no local install). Install: claude mcp add tenderly --transport http https://mcp.tenderly.co/mcp. Entry: {"mcpServers": {"tenderly": {"type": "streamable-http", "url": "https://mcp.tenderly.co/mcp"}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.tenderly.co/mcp (Streamable HTTP, OAuth)).
Is Tenderly MCP verified on Sato Hub?
No independent verification is on record for Tenderly MCP; its verification status is "Self-Reported" and its Sato Score is 25 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Tenderly MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/tenderly-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.