Skip to main content
Glama
itsanishjain

code-mode-alchemy-mcp

by itsanishjain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ALCHEMY_API_KEYYesYour Alchemy API key
ALCHEMY_NETWORKYesThe target blockchain network (e.g., eth-mainnet)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Search Alchemy's API endpoints by keyword. Returns matching endpoints with their paths, methods, parameters, and server URLs. Use this before execute() to discover the right endpoint.

executeA

Execute JavaScript code against Alchemy's APIs. The sandbox provides:

  • request(url, params?, options?) — GET/REST endpoint; {apiKey} and {network} in URLs are auto-replaced

  • fetch — raw fetch for custom requests (use for JSON-RPC POST calls)

  • ALCHEMY_API_KEY — the configured API key string

  • ALCHEMY_NETWORK — current network (default: eth-mainnet)

  • console.log() — captured and returned in logs

REST example:

const data = await request(
  "https://{network}.g.alchemy.com/nft/v3/{apiKey}/getNFTsForOwner",
  { owner: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", withMetadata: false }
);
return data;

JSON-RPC example:

const res = await fetch(
  `https://{network}.g.alchemy.com/v2/${ALCHEMY_API_KEY}`.replace("{network}", ALCHEMY_NETWORK),
  {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "alchemy_getTokenBalances", params: ["0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"] })
  }
);
return await res.json();

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation5/5

Search and execute have clearly distinct roles: search discovers API endpoints, while execute runs arbitrary JavaScript against them. There is no overlap in purpose, and the descriptions explicitly guide sequential use.

Naming Consistency5/5

Both tool names are concise, lowercase imperative verbs following the same bare-verb convention. No inconsistent casing or mixed noun/verb patterns.

Tool Count4/5

Two tools is slightly below the typical 3-15 range, but both are essential and earn their place: one for discovery and one for universal execution. The set is minimal rather than redundant.

Completeness4/5

Search plus execute covers endpoint discovery and arbitrary REST/JSON-RPC calls, which is nearly complete for a code-mode API gateway. Minor gaps remain, such as no structured endpoint-schema lookup or built-in pagination helpers, but agents can work around these.

Resources