MCP.Market

🐴 Gulltoppr MCP server

online · 82% uptime
by portdeveloper·io.github.portdeveloper/gulltoppr·v0.1.2

Resolve any EVM contract ABI (even unverified, via decompilation), read, simulate, prepare txs.

B76/100grade B
What users say
No reviews yet
Be the first
Safety scan
B76/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed 🐴 Gulltoppr yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

🐴 Gulltoppr tools (12)

write = sends, deletes, buys or posts
  • decode_txFree

    Decode what a transaction did: delegated heimdall decode plus `decoded_call` from the resolved target ABI when available. Prefer `decoded_call` for typed function/arg names, and read its provenance.

  • encode_callFree

    Encode a function call to calldata (0x…) without sending anything.

  • export_registryFree

    Return the CC0 selector commons as NDJSON. This can be large; prefer lookup_selector for normal agent workflows.

  • list_chainsFree

    List viem-backed chain aliases and ids. Use filters to find testnets, default-RPC chains, or a named chain before resolving contracts.

  • lookup_selectorFree

    Lookup gulltoppr-proven signatures for a 4-byte function/error selector or 32-byte event topic0. Prefer these over public 4byte guesses.

  • prepare_txFree

    Prepare a contract WRITE for the user to sign. Returns an UNSIGNED transaction, its simulation, a human-readable summary, safety metadata, warnings, a configured signing deeplink, and an EIP-1193 wallet request when signing is recommended. IMPORTANT: this tool NEVER signs or broadcasts. Present the summary + simulation + warnings to the user. Only hand them the `deeplink` or `wallet_request` when `safety.signing_recommended` is true. If `safety.risk_level` is high or blocked, make that explicit; blocked means do not send.

  • read_contractFree

    Call a view/pure function and get the decoded result. No wallet, no cost. Rejects state-mutating functions.

  • registry_statsFree

    Read selector commons counts by proof grade and bytecode-match index size.

  • resolve_abiFree

    Resolve a contract's interface from chain + address via a fallback ladder (Etherscan → Sourcify → proxy → heimdall decompile → 4byte). Returns a compact capability manifest (read vs write functions, the 'buttons'), proxy chain, token metadata, and PROVENANCE. ALWAYS read `provenance`: a `decompiled` ABI has synthetic function names — treat it with care and confirm intent before writing. Partial, proxy, and bytecode-match results lead with a WARNING before the JSON. The compact manifest/provenance is also returned as structuredContent. Use method_q/method_kind/method_limit for large ABIs. Raw ABI is omitted from MCP output to save tokens; use REST/SDK resolve_abi with include_abi=true if needed.

  • resolve_nameFree

    Resolve an ENS/Basename to an address, or an address to its primary ENS/Basename. Pass chain=base for Basenames.

  • runtime_metricsFree

    Read process-local resolver/rung/RPC counters for smoke checks and reliability dashboards.

  • simulateFree

    Simulate a call and return success, gas, decoded return, and best-effort state diff / asset changes / logs. Provide a high-level call (address + function + args) or raw (to + data), never both.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 10076ms12/20
  • Tool poisoning12 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 57 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 76/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How 🐴 Gulltoppr compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
76/100
higher than 48% of 48,255 servers
Tools
12
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
82%
of our recent checks; the typical remote server answers 100%
Response time
205 ms
faster than 63% of 30,031 servers

What its tools let an agent do: 11 read · 1 run or deploy

Install 🐴 Gulltoppr in Claude Code, Cursor or VS Code

claude mcp add --transport http gulltoppr https://mcp.gulltoppr.dev/mcp
Add to Cursor

What the publisher says

From the 🐴 Gulltoppr repository's README, as published. We do not edit it. Read it on GitHub

🐴 gulltoppr

A real session: an unverified MEV bot that traded seconds earlier (no source, no ABI anywhere) resolved to a full interface in two MCP tool calls.

The REST engine for gulltoppr: the resolution ladder + verb surface that lets an AI agent go from (chain, address) to a correct, simulated, safe contract interaction. This is "the engine" of the four faces (REST → MCP → SDK → Skill); see ../SPEC.md for the full contract and ../IDEATION.md for the strategy.

TypeScript + viem + Hono. The heimdall decompile rung is delegated over HTTP to gulltoppr (kept out-of-process by design).

Run

npm install
npm run dev            # REST engine: tsx watch on http://localhost:8787
npm run mcp            # MCP server: stdio tools for agent clients
npm run mcp:http       # MCP server: Streamable HTTP (remote agents)
npm run typecheck      # tsc --noEmit
npm test               # vitest unit tests (cache, chains, ladder helpers, args, errors)
npm run verify         # root typecheck/test/audit + SDK build/test/audit
npm run docker:build   # build the REST engine deployment image
npm run docker:build:mcp # build the Streamable HTTP MCP deployment image
npm run docker:smoke   # start both deployment images and check health/discovery/registry metadata
npm run test:live      # opt-in live contract smoke tests (RPC/decompiler/network)

Set LIVEENGINEBASE_URL=https://api.gulltoppr.dev with npm run test:live to smoke a deployed engine instead of the local in-process server. The scheduled live GitHub Action runs the local path; manual dispatch can set the same deployed URL.

Env

Endpoints (SPEC §4)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

🐴 Gulltoppr: common questions

Is 🐴 Gulltoppr MCP server safe?
Mostly: it is graded B (76/100). Read the 🐴 Gulltoppr safety report
How do I install 🐴 Gulltoppr?
It runs remotely at mcp.gulltoppr.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does 🐴 Gulltoppr need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is 🐴 Gulltoppr maintained?
The last commit was 95 days ago (2026-08-01). The latest release is v0.1.2.
Is 🐴 Gulltoppr up?
82% of our last 28 checks got an answer. We check remote servers about four times a day.
How does 🐴 Gulltoppr compare with other MCP servers?
safety score 76/100 (higher than 48% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.